Updated FIXME

diff --git a/man2/getrlimit.2 b/man2/getrlimit.2
index b6e3e70d881a206e13f90a949c4fad0a064b6ed7..32698b795928ba4f74a6566edce25c0fd2bcca1a 100644 (file)
--- a/man2/getrlimit.2
+++ b/man2/getrlimit.2
@@ -367,11 +367,9 @@ In 2.6.x kernels before 2.6.17, a
 .B RLIMIT_CPU 
 limit of 0 is wrongly treated as "no limit" (like 
 .BR RLIM_INFINITY ).
-.\" FIXME . The following change occurred in 2.6.17-rc1; verify
-.\" that it stays for 2.6.17 final.
-.\" see http://marc.theaimsgroup.com/?l=linux-kernel&m=114008066530167&w=2
 Since kernel 2.6.17, setting a limit of 0 does have an effect, 
 but is actually treated as a limit of 1 second.
+.\" see http://marc.theaimsgroup.com/?l=linux-kernel&m=114008066530167&w=2
 
 A kernel bug means that
 .B RLIMIT_RTPRIO