Updated FIXMEs

diff --git a/man2/chroot.2 b/man2/chroot.2
index ce8d4b742aee580e27ce522a2d364bedfea11858..22ff3a03c6d3b54068630a8b9022beb9a9ba4be4 100644 (file)
--- a/man2/chroot.2
+++ b/man2/chroot.2
@@ -118,7 +118,7 @@ The root directory is left unchanged by
 FreeBSD has a stronger
 .BR jail ()
 system call.
-.\" FIXME -- eventually say something about containers,
+.\" FIXME . eventually say something about containers,
 .\" virtual servers, etc.?
 .SH "SEE ALSO"
 .BR chdir (2),

diff --git a/man2/fcntl.2 b/man2/fcntl.2
index 56dbb2f52423e0f043b1d2069c8f30fef006e6c8..8d92af53482849a97bf29fb34fe1a0a8dd8473f3 100644 (file)
--- a/man2/fcntl.2
+++ b/man2/fcntl.2
@@ -147,7 +147,7 @@ On Linux this command can only change the
 and
 .BR O_NONBLOCK
 flags.
-.\" FIXME According to POSIX.1-2001, O_SYNC should also be modifiable
+.\" FIXME . According to POSIX.1-2001, O_SYNC should also be modifiable
 .\" via fcntl(2), but currently Linux does not permit this
 .\" See http://bugzilla.kernel.org/show_bug.cgi?id=5994
 .SS "Advisory locking"
@@ -915,11 +915,10 @@ that is, the return value of
 will be \-1, and
 .I errno
 will contain the (positive) process group ID.
-.\" FIXME Dec 04: some limited testing on alpha and ia64 seems to
+.\" mtk, Dec 04: some limited testing on alpha and ia64 seems to
 .\" indicate that ANY negative PGID value will cause F_GETOWN
 .\" to misinterpret the return as an error. Some other architectures
-.\" seem to have the same range check as x86.  Must document
-.\" the reality on other architectures -- MTK
+.\" seem to have the same range check as x86.  
 
 In Linux 2.4 and earlier, there is bug that can occur
 when an unprivileged process uses

diff --git a/man2/get_mempolicy.2 b/man2/get_mempolicy.2
index 4ac24b703b40306d0e6c8b4e8845b4e8bf63b52b..716e704bf72b66a965b217397dda10ca88d1d78c 100644 (file)
--- a/man2/get_mempolicy.2
+++ b/man2/get_mempolicy.2
@@ -30,7 +30,7 @@ get_mempolicy \- Retrieve NUMA memory policy for a process
 .BI "                  unsigned long " maxnode ", unsigned long " addr ,
 .BI "                  unsigned long " flags );
 .fi
-.\" FIXME rewrite this. it is confusing.
+.\" FIXME rewrite this DESCRIPTION. it is confusing.
 .SH DESCRIPTION
 .BR get_mempolicy ()
 retrieves the NUMA policy of the calling process or of a memory address,
@@ -121,7 +121,7 @@ on error, \-1 is returned and
 .I errno
 is set to indicate the error.
 .\" .SH ERRORS
-.\" FIXME writeme -- no errors are listed on this page
+.\" FIXME -- no errors are listed on this page
 .\" .
 .\" .TP
 .\" .B EINVAL

diff --git a/man2/ioperm.2 b/man2/ioperm.2
index 569fab177fa9b8fc63eabed04ed5d7c8c4c4be6a..be04d1f5e4d9870e8dd0e536c131ab9bb103a8e0 100644 (file)
--- a/man2/ioperm.2
+++ b/man2/ioperm.2
@@ -51,7 +51,8 @@ sets the port access permission bits for the calling process for
 If \fIturn_on\fP is non-zero, the calling process must be privileged
 .RB ( CAP_SYS_RAWIO ).
 
-.\" FIXME is the following still true?  Looking at changes in
+.\" FIXME is the following ("Only the first 0x3ff I/O ports can be 
+.\" specified in this manner") still true?  Looking at changes in
 .\" include/asm-i386/processor.h between 2.4 and 2.6 suggests
 .\" that the limit is different in 2.6.
 Only the first 0x3ff I/O ports can be specified in this manner.

diff --git a/man2/modify_ldt.2 b/man2/modify_ldt.2
index 30ba3018b1d3b8560cebfc1a4b9ec0e8b9ec6987..103787e07a1451ba5c595ba722fa1e44339fb85c 100644 (file)
--- a/man2/modify_ldt.2
+++ b/man2/modify_ldt.2
@@ -60,7 +60,7 @@ and
 .I bytecount
 must equal the size of this structure.
 .\"
-.\" FIXME, say something about func == 2 ans func == 0x11?
+.\" FIXME ? say something about func == 2 and func == 0x11?
 .\" In Linux 2.4, func == 2 returned "the default ldt"
 .\" In Linux 2.6, func == 2 is a nop, returning a zeroed out structure.
 .\" Linux 2.4 and 2.6 implement an operation for func == 0x11

diff --git a/man2/open.2 b/man2/open.2
index ddeb397cf2a06e7c7c775bd7428b5bd48257114e..d46b6bf7009f27fb1c6d2ecec7870ea6c498a206 100644 (file)
--- a/man2/open.2
+++ b/man2/open.2
@@ -242,7 +242,7 @@ This flag is intended for use by indexing or backup programs,
 where its use can significantly reduce the amount of disk activity.
 This flag may not be effective on all filesystems.
 One example is NFS, where the server maintains the access time.
-.\" FIXME? The O_NOATIME flag also affects the treatment of st_atime
+.\" The O_NOATIME flag also affects the treatment of st_atime
 .\" by mmap() and readdir(2), MTK, Dec 04.
 .TP
 .B O_NOCTTY
@@ -396,7 +396,7 @@ refers to a regular file, too large to be opened; see O_LARGEFILE above.
 (POSIX.1-2001 specifies the error
 .B EOVERFLOW
 for this case.)
-.\" FIXME Maybe this deviation from the standard will get repaired.
+.\" FIXME . Maybe this deviation from the standard will get repaired.
 .\" See http://bugzilla.kernel.org/show_bug.cgi?id=7253
 .\" "Open of a large file on 32-bit fails with EFBIG, should be EOVERFLOW"
 .\" Reported 2006-10-03
@@ -589,7 +589,7 @@ when calling
 use
 .BR fcntl (2)
 to enable this flag.
-.\" FIXME Check bugzilla report on open(O_ASYNC)
+.\" FIXME . Check bugzilla report on open(O_ASYNC)
 .\" See http://bugzilla.kernel.org/show_bug.cgi?id=5993
 .SH "SEE ALSO"
 .BR close (2),

diff --git a/man2/send.2 b/man2/send.2
index 7ca24a6a5e4afed41d5254fbe7d60ddd662c5c46..51bdd7fe9ff62a128f8c67995782bbac709abffc 100644 (file)
--- a/man2/send.2
+++ b/man2/send.2
@@ -150,7 +150,7 @@ The
 .I flags
 parameter is the bitwise OR
 of zero or more of the following flags.
-.\" FIXME? document MSG_PROXY (which went away in 2.3.15)
+.\" FIXME ? document MSG_PROXY (which went away in 2.3.15)
 .TP
 .BR MSG_CONFIRM " (Linux 2.3+ only)"
 Tell the link layer that forward progress happened: you got a successful

diff --git a/man2/set_mempolicy.2 b/man2/set_mempolicy.2
index 24e2a885df65052f653a0971b0e02f986b5a1a0c..0ff5dd1820aa8a6841cf691f57b2cc6ba1190c04 100644 (file)
--- a/man2/set_mempolicy.2
+++ b/man2/set_mempolicy.2
@@ -113,7 +113,7 @@ on error, \-1 is returned and
 .I errno
 is set to indicate the error.
 .\" .SH ERRORS
-.\" FIXME writeme -- no errors are listed on this page
+.\" FIXME no errors are listed on this page
 .\" .
 .\" .TP
 .\" .B EINVAL

diff --git a/man2/vfork.2 b/man2/vfork.2
index 8f067e59ed0fe24aa89fc41116d0345b31266309..4ff18cce5da5438d7593a5d2d2bdc98e94c1c001 100644 (file)
--- a/man2/vfork.2
+++ b/man2/vfork.2
@@ -116,7 +116,7 @@ in the parent process depended on knowing which variables are
 held in a register.
 .SH "CONFORMING TO"
 4.3BSD, POSIX.1-2001.
-.\" FIXME Mar 07: in the draft of the next POSIX revision, the spec for
+.\" FIXME . Mar 07: in the draft of the next POSIX revision, the spec for
 .\" vfork() has been removed.  See if this remains so in final version.
 The requirements put on
 .BR vfork ()

diff --git a/man3/fmemopen.3 b/man3/fmemopen.3
index fd86cf00978e6267ae76e4b6fa2be7345ab64138..c928cfb42dcb19441760daa237dc6fecd483b9a9 100644 (file)
--- a/man3/fmemopen.3
+++ b/man3/fmemopen.3
@@ -121,7 +121,7 @@ This byte is
 included in the size value stored at
 .IR sizeloc .
 .\"
-.\" FIXME The glibc info doc has text like the following, but it appears
+.\" FIXME . The glibc info doc has text like the following, but it appears
 .\" not to be true: http://sourceware.org/bugzilla/show_bug.cgi?id=1996
 .\" The stream's file position can be changed with
 .\" .BR fseek (3)

diff --git a/man3/netlink.3 b/man3/netlink.3
index 75e52c08043b15ece5828ca4b67f3da20fe09a8e..8a6771bf7ef587a18996d2d06a7c763697f1eca1 100644 (file)
--- a/man3/netlink.3
+++ b/man3/netlink.3
@@ -6,7 +6,7 @@
 netlink \- Netlink macros
 .SH SYNOPSIS
 .nf
-.\" FIXME what will glibc 2.1 use here?
+.\" FIXME . what will glibc 2.1 use here?
 .\" May 2007: glibc 2.5, things look to be unchanged -- the header file 
 .\" is still linux/netlink.h -- mtk
 .B #include <asm/types.h>
@@ -54,7 +54,7 @@ NLMSG_DATA
 Return a pointer to the payload associated with the passed
 .IR nlmsghdr .
 .TP
-.\" FIXME this is bizarre, maybe the interface should be fixed.
+.\" this is bizarre, maybe the interface should be fixed.
 NLMSG_NEXT
 Get the next
 .I nlmsghdr

diff --git a/man3/rtnetlink.3 b/man3/rtnetlink.3
index 6870cca21ba45f42d77eb6774e471ca32e2f4ab2..0a2e248b756bda86f6e84095a4c00181c21bb6f8 100644 (file)
--- a/man3/rtnetlink.3
+++ b/man3/rtnetlink.3
@@ -78,7 +78,7 @@ bytes of data.
 .SH BUGS
 This manual page is lacking and incomplete.
 .SH EXAMPLE
-.\" FIXME would be better to use libnetlink in the EXAMPLE code here
+.\" FIXME ? would be better to use libnetlink in the EXAMPLE code here
 
 Creating a rtnetlink message to set a MTU of a device.
 .nf

diff --git a/man3/sigset.3 b/man3/sigset.3
index dd601b5645d718e9a20c8a9da3b2f11010a785fc..ec0ffecfd361defcf40380413a97e644fe8f3fe2 100644 (file)
--- a/man3/sigset.3
+++ b/man3/sigset.3
@@ -121,7 +121,7 @@ On error,
 returns \-1, with
 .I errno
 set to indicate the error.
-.\" FIXME But as at 2.3.5, glibc's sigset() is broken for the
+.\" FIXME . But as at 2.3.5, glibc's sigset() is broken for the
 .\" SIG_HOLD case: it will only return SIG_HOLD if 'disp' is
 .\" SIG_HOLD; if the signal is blocked, then sigset() should return
 .\" SIG_HOLD even if 'disp' is specified as something other than
@@ -236,7 +236,7 @@ the return value of a successful
 should be
 .BR SIG_HOLD .
 Instead, the previous disposition of the signal is returned.
-.\"FIXME This has been reported on 30 Nov 05 -- mtk
+.\" FIXME . This has been reported on 30 Nov 05 -- mtk
 .\" See http://sourceware.org/bugzilla/show_bug.cgi?id=1951
 .\"
 .\" The POSIX.1-2001 disposition of sigset() says:

diff --git a/man3/wcstoimax.3 b/man3/wcstoimax.3
index b8a52d2b7dff50b1721166d124f260f33adc23a8..0a1044f798165e79f0641d91f89973b1ba0083a9 100644 (file)
--- a/man3/wcstoimax.3
+++ b/man3/wcstoimax.3
@@ -50,6 +50,6 @@ C99.
 .BR imaxdiv (3),
 .BR strtoimax (3),
 .BR strtoumax (3),
-.\" FIXME the pages referred to by the following xrefs are not yet written
+.\" FIXME . the pages referred to by the following xrefs are not yet written
 .BR wcstol (3),
 .BR wcstoul (3)

diff --git a/man7/netdevice.7 b/man7/netdevice.7
index 1574cb57735cf6e07c7b78961e8e5c61e485ba61..5fff6948171d91c007c830bf09bbfc92f9f357a1 100644 (file)
--- a/man7/netdevice.7
+++ b/man7/netdevice.7
@@ -215,7 +215,7 @@ and you should retry with a bigger buffer to get all addresses.
 When no error occurs the ioctl returns 0;
 otherwise \-1.
 Overflow is not an error.
-.\" FIXME Slaving isn't supported in 2.2
+.\" Slaving isn't supported in 2.2
 .\" .
 .\" .TP
 .\" .BR SIOCGIFSLAVE ", " SIOCSIFSLAVE

diff --git a/man7/rtnetlink.7 b/man7/rtnetlink.7
index 2b5fa00892a4808a2285fe9c3b782fe7770eab10..35505948ea1c733d0ae3ff89279ae03f608856a3 100644 (file)
--- a/man7/rtnetlink.7
+++ b/man7/rtnetlink.7
@@ -34,7 +34,7 @@ sockets.
 It is based on netlink messages, see
 .BR netlink (7)
 for more information.
-.\" FIXME all these macros could be moved to rtnetlink(3)
+.\" FIXME ? all these macros could be moved to rtnetlink(3)
 .SS "Routing Attributes"
 Some rtnetlink messages have optional attributes after the initial header:
 

diff --git a/man7/socket.7 b/man7/socket.7
index ada7e37fd64d5fae9a666df5b86175bbbd0647f7..4b076dd7466a4922fc420f6ccf054e0ebe420dcf 100644 (file)
--- a/man7/socket.7
+++ b/man7/socket.7
@@ -165,7 +165,7 @@ Urgent data arrived.
 .B SIGURG
 is sent then.
 T}
-.\" FIXME The following is not true currently:
+.\" FIXME . The following is not true currently:
 .\" It is no I/O event when the connection
 .\" is broken from the local end using
 .\" .BR shutdown (2)