freebsd version typo

diff --git a/BUGS b/BUGS
index 8c45e33e4099955ae3a3d8b5c5bee4d5daee6fbf..3a3ba6b367d42ef52b524e3cb85013b43db4dd2e 100644 (file)
--- a/BUGS
+++ b/BUGS
@@ -284,7 +284,7 @@ the resulting configure script by an order of magnitude, and for no real
 gain.  Configure is big enough as it is, we don't need any more useless
 baggage in it.
 
-(18) NetBSD 2.0.2, FreeBSD 4.6, OpenBSD 3.7, and quite possibly most other
+(18) NetBSD 2.0.2, FreeBSD 5.4, OpenBSD 3.7, and quite possibly most other
      BSDs and other OSs (as of September 2005)
 
 Some BSD kernels don't have a way to turn off the NFS attribute cache.  They

diff --git a/README.attrcache b/README.attrcache
index 04963dbe70f84b7e9b8010c49bf0b1bdb0164859..d290ce9a46ed2b25d56cc67bd63a002068dc1d9e 100644 (file)
--- a/README.attrcache
+++ b/README.attrcache
@@ -50,7 +50,7 @@ resolution of only 1 second, which was not fine enough under heavy load.  We
 fixed this problem and switched to using a microsecond resolution mtime.
 
 After fixing this in Amd, we went on to verify that things work for other
-OSs.  When we got to FreeBSD 4.6 and NetBSD 2.0.2, we found out that they
+OSs.  When we got to FreeBSD 5.4 and NetBSD 2.0.2, we found out that they
 always cache directory entries, and there is no way to turn it off
 completely.  Specifically, if we set the ac{reg,dir}{min,max} fields in
 struct nfs_args all to zero, the kernel seems to cache the entries for a
@@ -99,7 +99,7 @@ Linux: 2.6.11 kernel (2.4.latest probably works fine)
 ** Vulnerable (don't support a proper "noac" flag):
 
 NetBSD 2.0.2 (older versions also probably affected)
-FreeBSD 4.6 (older versions also probably affected)
+FreeBSD 5.4 (older versions also probably affected)
 OpenBSD 3.7 (older versions also probably affected)
 
 Note: NetBSD has promised to support a noac flag hopefully after 2.1.0 is