LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

adjtimex.2, bind.2, cacheflush.2, clone.2, fallocate.2, fanotify_init.2, fanotify_mark.2, flock.2, futex.2, getdents.2, getpriority.2, getrlimit.2, gettid.2, gettimeofday.2, ioprio_set.2, kexec_load.2, migrate_pages.2, modify_ldt.2, mount.2, move_pages.2, mprotect.2, msgop.2, nfsservctl.2, perf_event_open.2, pread.2, ptrace.2, recvmmsg.2, rename.2, restart_syscall.2, sched_setattr.2, send.2, shmop.2, shutdown.2, sigaction.2, signalfd.2, syscalls.2, timer_create.2, timerfd_create.2, tkill.2, vmsplice.2, wait.2, aio_init.3, confstr.3, exit.3, fmemopen.3, fopen.3, getaddrinfo.3, getauxval.3, getspnam.3, isalpha.3, isatty.3, mallinfo.3, malloc.3, mallopt.3, psignal.3, pthread_attr_setinheritsched.3, qecvt.3, queue.3, rtnetlink.3, strerror.3, strftime.3, toupper.3, towlower.3, towupper.3, initrd.4, locale.5, proc.5, bootparam.7, capabilities.7, ddp.7, fanotify.7, icmp.7, inotify.7, ip.7, ipv6.7, netdevice.7, netlink.7, path_resolution.7, rtld-audit.7, rtnetlink.7, sched.7, signal.7, socket.7, svipc.7, tcp.7, unix.7, ld.so.8: srcfix: Update FIXMEs 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-08-21 16:47:44 -05:00
parent d62018316a
commit bea08fec7e
87 changed files with 190 additions and 186 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
man2/adjtimex.2
View File

@ -25,12 +25,14 @@
.\" Modified 1997-07-30 by Paul Slootman <paul@wurtel.demon.nl>
.\" Modified 2004-05-27 by Michael Kerrisk <mtk.manpages@gmail.com>
.\"
.\" FIXME 2.6.26 added ADJ_TAI
.\" FIXME Document ADJ_TAI (added in Linux 2.6.26)
.\" commit 153b5d054ac2d98ea0d86504884326b6777f683d
.\" FIXME 2.6.26 added ADJ_MICOR and ADJ_NANO
.\"
.\" FIXME Document ADJ_MICRO and ADJ_NANO (added in Linux 2.6.26)
.\" commit eea83d896e318bda54be2d2770d2c5d6668d11db
.\" Author: Roman Zippel <zippel@linux-m68k.org>
.\" FIXME 2.6.39 added ADJ_SETOFFSET
.\"
.\" FIXME Document ADJ_SETOFFSET (added in Linux 2.6.39)
.\" commit 094aa1881fdc1b8889b442eb3511b31f3ec2b762
.\" Author: Richard Cochran <richardcochran@gmail.com>
.\"
@ -61,7 +63,7 @@ struct timex {
int modes; /* mode selector */
long offset; /* time offset (usec) */
long freq; /* frequency offset (scaled ppm) */
.\" FIXME -- what is the scaling unit? 2^16 ?
.\" FIXME What is the scaling unit of timex.freq? 2^16 ?
long maxerror; /* maximum error (usec) */
long esterror; /* estimated error (usec) */
int status; /* clock command/status */

2
man2/bind.2
View File

@ -260,7 +260,7 @@ See also
.BR accept (2).
.SH BUGS
The transparent proxy options are not described.
.\" FIXME What *are* transparent proxy options?
.\" FIXME Document transparent proxy options
.SH EXAMPLE
An example of the use of
.BR bind ()

4
man2/cacheflush.2
View File

@ -74,8 +74,8 @@ or
.BR BCACHE .
.SH CONFORMING TO
This Linux-specific system call is available only on MIPS-based systems.
.\" FIXME This system call was only on MIPS back in 1.2 days, but
.\" by now it is on a number of other architectures (but not i386).
.\" FIXME The cacheflush() system call was only on MIPS back in 1.2 days,
.\" but by now it is on a number of other architectures (but not i386).
.\" Investigate the details and update this page.
It should not be used in programs intended to be portable.
.\" Irix 6.5 appears to have a cacheflush() syscall -- mtk

3
man2/clone.2
View File

@ -318,7 +318,6 @@ This flag can't be specified in conjunction with
.BR CLONE_SYSVSEM .
.TP
.BR CLONE_NEWNET " (since Linux 2.6.24)"
.\" FIXME Check when the implementation was completed
(The implementation of this flag was completed only
by about kernel version 2.6.29.)
@ -341,7 +340,7 @@ directory trees, sockets, etc.).
A physical network device can live in exactly one
network namespace.
A virtual network device ("veth") pair provides a pipe-like abstraction
.\" FIXME Add pointer to veth(4) page when it is eventually completed
.\" FIXME . Add pointer to veth(4) page when it is eventually completed
that can be used to create tunnels between network namespaces,
and can be used to create a bridge to a physical network device
in another namespace.

2
man2/fallocate.2
View File

@ -249,7 +249,7 @@ A signal was caught during execution.
.I offset
was less than 0, or
.I len
.\" FIXME (raise a kernel bug) Probably the len==0 case should be
.\" FIXME . (raise a kernel bug) Probably the len==0 case should be
.\" a no-op, rather than an error. That would be consistent with
.\" similar APIs for the len==0 case.
.\" See "Re: [PATCH] fallocate.2: add FALLOC_FL_PUNCH_HOLE flag definition"

2
man2/fanotify_init.2
View File

@ -240,7 +240,7 @@ This system call is Linux-specific.
As of Linux 3.15,
the following bug exists:
.IP * 3
.\" FIXME: Patch accepted to mm tree.
.\" FIXME . Patch accepted to mm tree.
The
.I event_f_flags
argument is not checked for invalid flags.

6
man2/fanotify_mark.2
View File

@ -306,7 +306,7 @@ This system call is Linux-specific.
As of Linux 3.15,
the following bugs exist:
.IP * 3
.\" FIXME: Patch is in next-20140424.
.\" FIXME . Patch is in next-20140424.
If
.I flags
contains
@ -316,13 +316,13 @@ and
.I pathname
must specify a valid filesystem object, even though this object is not used.
.IP *
.\" FIXME: Patch is in next-20140424.
.\" FIXME . Patch is in next-20140424.
.BR readdir (2)
does not generate a
.B FAN_ACCESS
event.
.IP *
.\" FIXME: Patch proposed.
.\" FIXME . Patch proposed.
If
.BR fanotify_mark (2)
is called with

4
man2/flock.2
View File

@ -29,8 +29,8 @@
.\" Substantial rewrites and additions
.\" 2005-05-10 mtk, noted that lock conversions are not atomic.
.\"
.\" FIXME: Maybe document LOCK_MAND, LOCK_RW, LOCK_READ, LOCK_WRITE
.\" which only have effect for SAMBA.
.\" FIXME Maybe document LOCK_MAND, LOCK_RW, LOCK_READ, LOCK_WRITE
.\" which only have effect for SAMBA.
.\"
.TH FLOCK 2 2014-06-13 "Linux" "Linux Programmer's Manual"
.SH NAME

8
man2/futex.2
View File

@ -10,14 +10,14 @@
.\" Modified 2004-06-17 mtk
.\" Modified 2004-10-07 aeb, added FUTEX_REQUEUE, FUTEX_CMP_REQUEUE
.\"
.\" FIXME
.\" FIXME .
.\" See also https://bugzilla.kernel.org/show_bug.cgi?id=14303
.\" 2.6.14 adds FUTEX_WAKE_OP
.\" commit 4732efbeb997189d9f9b04708dc26bf8613ed721
.\" Author: Jakub Jelinek <jakub@redhat.com>
.\" Date: Tue Sep 6 15:16:25 2005 -0700
.\"
.\" FIXME
.\" FIXME .
.\" 2.6.18 adds (Ingo Molnar) priority inheritance support:
.\" FUTEX_LOCK_PI, FUTEX_UNLOCK_PI, and FUTEX_TRYLOCK_PI. These need
.\" to be documented in the manual page. Probably there is sufficient
@ -32,13 +32,13 @@
.\"
.\" See Documentation/pi-futex.txt
.\"
.\" FIXME
.\" FIXME .
.\" 2.6.25 adds FUTEX_WAKE_BITSET, FUTEX_WAIT_BITSET
.\" commit cd689985cf49f6ff5c8eddc48d98b9d581d9475d
.\" Author: Thomas Gleixner <tglx@linutronix.de>
.\" Date: Fri Feb 1 17:45:14 2008 +0100
.\"
.\" FIXME
.\" FIXME .
.\" 2.6.31 adds FUTEX_WAIT_REQUEUE_PI, FUTEX_CMP_REQUEUE_PI
.\" commit 52400ba946759af28442dee6265c5c0180ac7122
.\" Author: Darren Hart <dvhltc@us.ibm.com>

4
man2/getdents.2
View File

@ -191,8 +191,8 @@ fields employed in the
.IR linux_dirent
structure.
.SH EXAMPLE
.\" FIXME: This program uses the older getdents() system call
.\" and the structure with smaller field widths.
.\" FIXME The example program needs to be revised, since it uses the older
.\" getdents() system call and the structure with smaller field widths.
The program below demonstrates the use of
.BR getdents ().
The following output shows an example of what we see when running this

3
man2/getpriority.2
View File

@ -42,9 +42,6 @@
.\" Clarified meaning of 0 value for 'who' argument
.\" Modified 2004-05-27 by Michael Kerrisk <mtk.manpages@gmail.com>
.\"
.\" FIXME Oct 2008: Denys Vlasenko is working on a PRIO_THREAD feature that
.\" is likely to get included in mainline; this will need to be documented.
.\"
.TH GETPRIORITY 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
getpriority, setpriority \- get/set program scheduling priority

11
man2/getrlimit.2
View File

@ -439,7 +439,7 @@ must match the real user ID of the caller
.I and
the real, effective, and saved set group IDs of the target process
must match the real group ID of the caller.
.\" FIXME this permission check is strange
.\" FIXME . this permission check is strange
.\" Asked about this on LKML, 7 Nov 2010
.\" "Inconsistent credential checking in prlimit() syscall"
.SH RETURN VALUE
@ -552,12 +552,6 @@ but instead employ
.BR prlimit (),
for the reasons described in BUGS.
.SH BUGS
.\" FIXME prlimit() does not suffer
.\" https://bugzilla.kernel.org/show_bug.cgi?id=5042
.\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=12201
.\" Since versions 2.13, glibc has library implementations of
.\" getrlimit() and setrlimit() that use prlimit() to work around
.\" this bug.
In older Linux kernels, the
.B SIGXCPU
and
@ -613,7 +607,7 @@ do not change the
soft limit in this manner,
and the Linux behavior is probably not standards conformant;
portable applications should avoid relying on this Linux-specific behavior.
.\" FIXME https://bugzilla.kernel.org/show_bug.cgi?id=50951
.\" FIXME . https://bugzilla.kernel.org/show_bug.cgi?id=50951
The Linux-specific
.BR RLIMIT_RTTIME
limit exhibits the same behavior when the soft limit is encountered.
@ -648,6 +642,7 @@ the kernel represents resource limits on 32-bit platforms as
.IR "unsigned long" .
However, a 32-bit data type is not wide enough.
.\" https://bugzilla.kernel.org/show_bug.cgi?id=5042
.\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=12201
The most pertinent limit here is
.BR RLIMIT_FSIZE ,
which specifies the maximum size to which a file can grow:

2
man2/gettid.2
View File

@ -62,7 +62,7 @@ are intended to be portable.
.SH NOTES
Glibc does not provide a wrapper for this system call; call it using
.BR syscall (2).
.\" FIXME See http://sourceware.org/bugzilla/show_bug.cgi?id=6399
.\" FIXME . See http://sourceware.org/bugzilla/show_bug.cgi?id=6399
.\" "gettid() should have a wrapper"
The thread ID returned by this call is not the same thing as a

2
man2/gettimeofday.2
View File

@ -100,7 +100,7 @@ If either
or
.I tz
is NULL, the corresponding structure is not set or returned.
.\" FIXME The compilation warning looks to be going away in 2.17
.\" FIXME . The compilation warning looks to be going away in 2.17
.\" see glibc commit 4b7634a5e03b0da6f8875de9d3f74c1cf6f2a6e8
(However, compilation warnings will result if
.I tv

2
man2/ioprio_set.2
View File

@ -70,7 +70,7 @@ is 0, then operate on the process group of which the caller is a member.
.I who
is a user ID identifying all of the processes that
have a matching real UID.
.\" FIXME who==0 needs to be documented,
.\" FIXME . Need to document the behavior when 'who" is specified as 0
.\" See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652443
.PP
If

7
man2/kexec_load.2
View File

@ -50,7 +50,7 @@ The following values can be specified in
.TP
.BR KEXEC_ON_CRASH " (since Linux 2.6.13)"
Execute the new kernel automatically on a system crash.
.\" FIXME figure out how this is really used
.\" FIXME Explain in more detail how KEXEC_ON_CRASH is actually used
.TP
.BR KEXEC_PRESERVE_CONTEXT " (since Linux 2.6.27)"
Preserve the system hardware and
@ -109,7 +109,8 @@ struct kexec_segment {
.fi
.in
.PP
.\" FIXME elaborate on the following:
.\" FIXME Explain the details of how the kernel image defined by segments
.\" is copied from the calling process into previously reserved memory.
The kernel image defined by
.I segments
is copied from the calling process into previously reserved memory.
@ -152,7 +153,7 @@ Call it using
The required constants are in the Linux kernel source file
.IR linux/kexec.h ,
which is not currently exported to glibc.
.\" FIXME Andi submitted a patch for this.
.\" FIXME . Andi submitted a patch for this.
.\" Check if it got accepted later.
Therefore, these constants must be defined manually.

2
man2/migrate_pages.2
View File

@ -108,7 +108,7 @@ to access the specified target nodes.
No process matching
.I pid
could be found.
.\" FIXME There are other errors
.\" FIXME Document the other errors that can occur for migrate_pages()
.SH VERSIONS
The
.BR migrate_pages ()

2
man2/modify_ldt.2
View File

@ -62,7 +62,7 @@ and
.I bytecount
must equal the size of this structure.
.\"
.\" FIXME ? say something about func == 2 and func == 0x11?
.\" FIXME Should this page 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

9
man2/mount.2
View File

@ -102,7 +102,6 @@ in the low order 16 bits:
.\"
.\" These settings are visible in proc/mountinfo
.\"
.\"
.\" These need to be documented on this page.
.\" See:
.\" Documentation/filesystems/sharedsubtree.txt
@ -126,7 +125,7 @@ in the low order 16 bits:
.\" Ram Pai (linuxram@us.ibm.com), Software Engineer, IBM
.\" Date: 17 Sep 2007
.\"
.\" 2.6.25 Added MS_I_VERSION, which needs to be documented.
.\" FIXME 2.6.25 Added MS_I_VERSION, which needs to be documented.
.\"
.TP
.BR MS_BIND " (Linux 2.4 onward)"
@ -159,7 +158,7 @@ Permit mandatory locking on files in this filesystem.
(Mandatory locking must still be enabled on a per-file basis,
as described in
.BR fcntl (2).)
.\" FIXME Say more about MS_MOVE
.\" FIXME Describe the MS_MOVE flag in more detail
.TP
.B MS_MOVE
Move a subtree.
@ -412,8 +411,8 @@ The definitions of
and
.BR MS_STRICTATIME
were added to glibc headers in version 2.12.
.\" FIXME: Definitions of the so-far-undocumented MS_UNBINDABLE, MS_PRIVATE,
.\" MS_SHARED, and MS_SLAVE were (also) only added to glibc headers in 2.12.
.\" FIXME . Definitions of the so-far-undocumented MS_UNBINDABLE, MS_PRIVATE,
.\" MS_SHARED, and MS_SLAVE were (also) only added to glibc headers in 2.12.
.SH "CONFORMING TO"
This function is Linux-specific and should not be used in
programs intended to be portable.

12
man2/move_pages.2
View File

@ -12,9 +12,10 @@
.\" permission notice identical to this one.
.\" %%%LICENSE_END
.\"
.\" FIXME Should programs normally be using this API directly, or should
.\" FIXME Should programs normally be using move_pages() directly, or should
.\" they rather be using interfaces in the numactl package?
.\" (e.g., compare with recommendation in mbind(2)).
.\" Does this page need to give advise on this topic?
.TH MOVE_PAGES 2 2010-06-11 "Linux" "Linux Programmer's Manual"
.SH NAME
move_pages \- move individual pages of a process to another node
@ -65,7 +66,8 @@ and
.I pages
is an array of pointers to the pages that should be moved.
These are pointers that should be aligned to page boundaries.
.\" FIXME what if they are not aligned?
.\" FIXME Describe the result if pointers in the 'pages' array are
.\" not aligned to page boundaries
Addresses are specified as seen by the process specified by
.IR pid .
@ -142,7 +144,7 @@ Unable to allocate memory on target node.
On success
.BR move_pages ()
returns zero.
.\" FIXME Is the following quite true: does the wrapper in numactl
.\" FIXME . Is the following quite true: does the wrapper in numactl
.\" do the right thing?
On error, it returns \-1, and sets
.I errno
@ -153,8 +155,8 @@ to indicate the error.
Too many pages to move.
.TP
.B EACCES
.\" FIXME Clarify "current cpuset". Is that the cpuset of the caller
.\" or the target?
.\" FIXME Clarify "current cpuset" in the description of the EACCESS error.
.\" Is that the cpuset of the caller or the target?
One of the target nodes is not allowed by the current cpuset.
.TP
.B EFAULT

3
man2/mprotect.2
View File

@ -29,6 +29,7 @@
.\" Modified 2004-08-16 by Andi Kleen <ak@muc.de>
.\" 2007-06-02, mtk: Fairly substantial rewrites and additions, and
.\" a much improved example program.
.\"
.\" FIXME The following protection flags need documenting:
.\" PROT_SEM
.\" PROT_GROWSDOWN
@ -73,8 +74,6 @@ The memory can be modified.
.TP
.B PROT_EXEC
The memory can be executed.
.\" FIXME
.\" Document PROT_GROWSUP and PROT_GROWSDOWN
.SH RETURN VALUE
On success,
.BR mprotect ()

7
man2/msgop.2
View File

@ -35,7 +35,8 @@
.\" Modified, 11 Nov 2004, Michael Kerrisk <mtk.manpages@gmail.com>
.\" Language and formatting clean-ups
.\" Added notes on /proc files
.\" FIXME . Add example programs to this page.
.\"
.\" FIXME Add example programs to this page.
.\"
.TH MSGOP 2 2014-08-19 "Linux" "Linux Programmer's Manual"
.SH NAME
@ -551,7 +552,7 @@ and the message queue contained less than
.I msgtyp
messages, then the call would block until the next message is written
to the queue.
.\" FIXME http://marc.info/?l=linux-kernel&m=139048542803605&w=2
.\" http://marc.info/?l=linux-kernel&m=139048542803605&w=2
At that point, the call would return a copy of the message,
.I regardless
of whether that message was at the ordinal position
@ -569,7 +570,7 @@ in
is a logical error (since these flags impose different interpretations on
.IR msgtyp ).
In Linux 3.13 and earlier,
.\" FIXME http://marc.info/?l=linux-kernel&m=139048542803605&w=2
.\" http://marc.info/?l=linux-kernel&m=139048542803605&w=2
this error was not diagnosed by
.BR msgrcv ().
This bug is fixed

2
man2/nfsservctl.2
View File

@ -2,7 +2,7 @@
.\" This text is in the public domain.
.\" %%%LICENSE_END
.\"
.\" FIXME The description of nfsservctl() on this page
.\" FIXME . The description of nfsservctl() on this page
.\" is woefully thin.
.\"
.TH NFSSERVCTL 2 2013-09-17 "Linux" "Linux Programmer's Manual"

8
man2/perf_event_open.2
View File

@ -149,11 +149,11 @@ then
.BR execve (2).
.TP
.BR PERF_FLAG_FD_NO_GROUP
.\" FIXME The following sentence is unclear
.\" FIXME . The following sentence is unclear
This flag allows creating an event as part of an event group but
having no group leader.
It is unclear why this is useful.
.\" FIXME So, why is it useful?
.\" FIXME . So, why is it useful?
.TP
.BR PERF_FLAG_FD_OUTPUT
This flag reroutes the output from an event to the group leader.
@ -2279,8 +2279,8 @@ once the value reaches 0, a signal is sent of type
and
the underlying event is disabled.
Note: on newer kernels (definitely noticed with 3.2)
.\" FIXME(Vince) : Find out when this was introduced
Note: on newer kernels (since at least as early as Linux 3.2),
.\" FIXME . Find out when this was introduced
a signal is provided for every overflow, even if
.I wakeup_events
is not set.

2
man2/pread.2
View File

@ -150,7 +150,7 @@ flag should have no affect on the location at which
.BR pwrite ()
writes data.
However, on Linux, if a file is opened with
.\" FIXME https://bugzilla.kernel.org/show_bug.cgi?id=43178
.\" FIXME . https://bugzilla.kernel.org/show_bug.cgi?id=43178
.BR O_APPEND ,
.BR pwrite ()
appends data to the end of the file, regardless of the value of

13
man2/ptrace.2
View File

@ -263,7 +263,7 @@ in the tracer.
As for
.BR PTRACE_POKEUSER ,
some general-purpose register modifications may be disallowed.
.\" FIXME In the preceding sentence, which modifications are disallowed,
.\" FIXME . In the preceding sentence, which modifications are disallowed,
.\" and when they are disallowed, how does user space discover that fact?
.RI ( addr
is ignored.)
@ -949,7 +949,7 @@ Example:
/* r can still be 0 here! */
}
.fi
.\" FIXME:
.\" FIXME .
.\" waitid usage? WNOWAIT?
.\" describe how wait notifications queue (or not queue)
.LP
@ -1454,7 +1454,7 @@ or
.SS PTRACE_SINGLESTEP, PTRACE_SYSEMU, PTRACE_SYSEMU_SINGLESTEP stops
[Details of these kinds of stops are yet to be documented.]
.\"
.\" FIXME
.\" FIXME .
.\" document stops occurring with PTRACE_SINGLESTEP, PTRACE_SYSEMU,
.\" PTRACE_SYSEMU_SINGLESTEP
.SS Informational and restarting ptrace commands
@ -1566,8 +1566,7 @@ may race and the concurrent
.B SIGSTOP
may be lost.
.\"
.\" FIXME: Describe how to attach to a thread which is already
.\" group-stopped.
.\" FIXME . Describe how to attach to a thread which is already group-stopped.
.LP
Since attaching sends
.B SIGSTOP
@ -1660,7 +1659,7 @@ Yet another complication is to be sure that
the tracee is not already ptrace-stopped,
because no signal delivery happens while it is\(emnot even
.BR SIGSTOP .
.\" FIXME: Describe how to detach from a group-stopped tracee so that it
.\" FIXME . Describe how to detach from a group-stopped tracee so that it
.\" doesn't run, but continues to wait for SIGCONT.
.LP
If the tracer dies, all tracees are automatically detached and restarted,
@ -2004,7 +2003,7 @@ One possible workaround is to
.B PTRACE_DETACH
the thread group leader instead of restarting it in this case.
Last confirmed on 2.6.38.6.
.\" FIXME: ^^^ need to test/verify this scenario
.\" FIXME . need to test/verify this scenario
.LP
A
.B SIGKILL

2
man2/recvmmsg.2
View File

@ -268,7 +268,7 @@ main(void)
The
.I timeout
argument does not work as intended.
.\" FIXME https://bugzilla.kernel.org/show_bug.cgi?id=75371
.\" FIXME . https://bugzilla.kernel.org/show_bug.cgi?id=75371
.\" http://thread.gmane.org/gmane.linux.man/5677
The timeout is checked only after the receipt of each datagram,
so that if up to

4
man2/rename.2
View File

@ -65,7 +65,7 @@ _XOPEN_SOURCE\ >=\ 700 || _POSIX_C_SOURCE\ >=\ 200809L
.TP
Before glibc 2.10:
_ATFILE_SOURCE
.\" FIXME need to define FTMs for renameat2(), once it hits glibc
.\" FIXME . need to define FTMs for renameat2(), once it hits glibc
.RE
.ad
.PD
@ -401,7 +401,7 @@ library support was added to glibc in version 2.4.
.BR renameat2 ()
was added to Linux in kernel 3.15.
.\" FIXME glibc support is pending.
.\" FIXME . glibc support is pending.
.SH CONFORMING TO
.BR rename ():
4.3BSD, C89, C99, POSIX.1-2001, POSIX.1-2008.

6
man2/restart_syscall.2
View File

@ -107,7 +107,7 @@ to the process that made the system call that is restarted,
it appears as though that system call executed and
returned in the usual fashion.
.\"
.\" FIXME
.\" FIXME .
.\" There is one oddness in the implementation though, with respect to
.\" nanosleep() (and probably also clock_nanosleep()). The scenario
.\" is as follows:
@ -124,7 +124,7 @@ returned in the usual fashion.
.BR sigaction (2),
.BR sigreturn (2),
.BR signal (7)
.\" FIXME select(2) should probably get the restart_syscall() treatment:
.\" FIXME . select(2) should probably get the restart_syscall() treatment:
.\" If a select() call is suspended by stop-sig+SIGCONT, the time
.\" spent suspended is *not* deducted when the select() is restarted.
.\" FIXME: check whether recvmmsg() handles stop-sig+SIGCONT properly.
.\" FIXME . check whether recvmmsg() handles stop-sig+SIGCONT properly.

8
man2/sched_setattr.2
View File

@ -37,7 +37,7 @@ set and get scheduling policy and attributes
.BI "int sched_getattr(pid_t " pid ", const struct sched_attr *" attr ,
.BI " unsigned int " size ", unsigned int " flags );
.fi
.\" FIXME Add feature test macro requirements
.\" FIXME . Add feature test macro requirements
.SH DESCRIPTION
.SS sched_setattr()
The
@ -347,7 +347,7 @@ does not include all CPUs in the system
.BR sched_setaffinity (2)).
.SH VERSIONS
These system calls first appeared in Linux 3.14.
.\" FIXME Add glibc version
.\" FIXME . Add glibc version
.SH CONFORMING TO
These system calls are nonstandard Linux extensions.
.SH NOTES
@ -368,7 +368,7 @@ and (partially)
.BR getpriority (2).
.SH BUGS
In Linux versions up to
.\" FIXME patch sent to Peter Zijlstra
.\" FIXME . patch sent to Peter Zijlstra
3.15,
.BR sched_settattr ()
failed with the error
@ -377,7 +377,7 @@ instead of
.BR E2BIG
for the case described in ERRORS.
.\" In Linux versions up to up 3.15,
.\" .\" FIXME patch from Peter Zijlstra pending
.\" FIXME . patch from Peter Zijlstra pending
.\" .BR sched_setattr ()
.\" allowed a negative
.\" .I attr.sched_policy

2
man2/send.2
View File

@ -162,7 +162,7 @@ The
.I flags
argument 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 " (since Linux 2.3.15)"
Tell the link layer that forward progress happened: you got a successful

2
man2/shmop.2
View File

@ -274,8 +274,6 @@ many other implementations do not support it.
The following system parameter affects
.BR shmat ():
.TP
.\" FIXME A good explanation of the rationale for the existence
.\" of SHMLBA would be useful here
.B SHMLBA
Segment low boundary address multiple.
When explicitly specifying an attach address in a call to

2
man2/shutdown.2
View File

@ -106,7 +106,7 @@ As currently implemented,
checks for the validity of
.I how
are done in domain-specific code, and not all domains perform these checks.
.\" FIXME
.\" FIXME .
.\" https://bugzilla.kernel.org/show_bug.cgi?id=47111
Most notably, UNIX domain sockets simply ignore invalid values;
this may change in the future.

4
man2/sigaction.2
View File

@ -266,7 +266,7 @@ siginfo_t {
hardware-generated signal
(unused on most architectures) */
.\" FIXME
.\" si_trapno seems to be only used on SPARC and Alpha;
.\" The siginfo_t 'si_trapno' filed seems to be used only on SPARC and Alpha;
.\" this page could use a little more detail on its purpose there.
pid_t si_pid; /* Sending process ID */
uid_t si_uid; /* Real user ID of sending process */
@ -398,7 +398,7 @@ and
fill in
.I si_addr
with the address of the fault.
.\" FIXME SIGTRAP also sets the following for ptrace_notify() ?
.\" FIXME . SIGTRAP also sets the following for ptrace_notify() ?
.\" info.si_code = exit_code;
.\" info.si_pid = task_pid_vnr(current);
.\" info.si_uid = current_uid(); /* Real UID */

2
man2/signalfd.2
View File

@ -191,7 +191,7 @@ struct signalfd_siginfo {
uint64_t ssi_addr; /* Address that generated signal
(for hardware-generated signals) */
.\" FIXME Since Linux 2.6.37 there is 'uint16_t ssi_addr_lsb'
.\" which is not yet documented
.\" in the signalfd_siginfo structure. This needs to be documented.
uint8_t pad[\fIX\fP]; /* Pad size to 128 bytes (allow for
additional fields in the future) */
};

4
man2/syscalls.2
View File

@ -304,7 +304,7 @@ T}
.\" Implements System V IPC calls
\fBkcmp\fP(2) 3.5
\fBkern_features\fP(2) 3.7 Sparc64
.\" FIXME: document kern_features():
.\" FIXME . document kern_features():
.\" commit 517ffce4e1a03aea979fe3a18a3dd1761a24fafb
\fBkexec_load\fP(2) 2.6.13
.\" The entry in the syscall table was reserved starting in 2.6.7
@ -587,7 +587,7 @@ T}
\fButimensat\fP(2) 2.6.22
\fButimes\fP(2) 2.2
\fButrap_install\fP(2) 2.2 Sparc
.\" FIXME: document utrap_install()
.\" FIXME . document utrap_install()
.\" There's a man page for Solaris 5.11
\fBvfork\fP(2) 2.2
\fBvhangup\fP(2) 1.0

6
man2/timer_create.2
View File

@ -23,9 +23,11 @@
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
.\" FIXME: Linux 2.6.39 adds CLOCK_BOOTTIME
.\" FIXME Linux 2.6.39 adds CLOCK_BOOTTIME, which needs be documented
.\" Does this also affect timerfd_create()?
.\" FIXME: Linux 2.3.0 adds CLOCK_BOOTTIME_ALARM and CLOCK_REALTIME_ALARM
.\"
.\" FIXME Linux 3.0 adds CLOCK_BOOTTIME_ALARM and CLOCK_REALTIME_ALARM,
.\" which need be documented
.\" Does this also affect timerfd_create()?
.\"
.TH TIMER_CREATE 2 2014-08-19 Linux "Linux Programmer's Manual"

3
man2/timerfd_create.2
View File

@ -16,7 +16,8 @@
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
.\" FIXME: Linux 3.0: timerfd_settime() adds a TFD_TIMER_CANCEL_ON_SET flag.
.\" FIXME Linux 3.0: timerfd_settime() adds a TFD_TIMER_CANCEL_ON_SET flag;
.\" This flag needs to documented.
.\"
.TH TIMERFD_CREATE 2 2011-09-14 Linux "Linux Programmer's Manual"
.SH NAME

2
man2/tkill.2
View File

@ -59,7 +59,7 @@ It allows only the target thread ID to be specified,
which may result in the wrong thread being signaled if a thread
terminates and its thread ID is recycled.
Avoid using this system call.
.\" FIXME: Maybe say something about the following:
.\" FIXME Maybe say something about the following:
.\" http://sourceware.org/bugzilla/show_bug.cgi?id=12889
.\" Rich Felker <bugdal@aerifal.cx>
.\" There is a race condition in pthread_kill: it is possible that,

2
man2/vmsplice.2
View File

@ -98,7 +98,7 @@ but may be implemented in the future; see
.B SPLICE_F_GIFT
The user pages are a gift to the kernel.
The application may not modify this memory ever,
.\" FIXME Explain the following line in a little more detail:
.\" FIXME . Explain the following line in a little more detail:
or page cache and on-disk data may differ.
Gifting pages to the kernel means that a subsequent
.BR splice (2)

2
man2/wait.2
View File

@ -374,7 +374,7 @@ was specified and no child(ren) specified by
.I id
has yet changed state;
on error, \-1 is returned.
.\" FIXME: As reported by Vegard Nossum, if infop is NULL, then waitid()
.\" FIXME As reported by Vegard Nossum, if infop is NULL, then waitid()
.\" returns the PID of the child. Either this is a bug, or it is intended
.\" behavior that needs to be documented. See my Jan 2009 LKML mail
.\" "waitid() return value strangeness when infop is NULL".

2
man3/aio_init.3
View File

@ -81,7 +81,7 @@ This field should specify the maximum number of simultaneous I/O requests
that the caller expects to enqueue.
If a value less than 32 is specified for this field,
it is rounded up to 32.
.\" FIXME But, if aio_num > 32, the behavior looks strange. See
.\" FIXME . But, if aio_num > 32, the behavior looks strange. See
.\" http://sourceware.org/bugzilla/show_bug.cgi?id=12083
The default value is 64.
.TP

1
man3/confstr.3
View File

@ -28,6 +28,7 @@
.\" See <bits/confname.h> for the rest.
.\" These should all be added to this page.
.\" See also the POSIX.1-2001 specification of confstr()
.\"
.TH CONFSTR 3 2014-03-20 "GNU" "Linux Programmer's Manual"
.SH NAME
confstr \- get configuration dependent string variables

2
man3/exit.3
View File

@ -22,7 +22,7 @@
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
.\" FIXME There are a lot of other process termination actions that
.\" FIXME . There are a lot of other process termination actions that
.\" could be listed on this page. See, for example, the list in the
.\" POSIX exit(3p) page.
.\"

8
man3/fmemopen.3
View File

@ -224,7 +224,7 @@ is specified as zero,
.BR fmemopen ()
fails with the error
.BR EINVAL .
.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=11216
.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=11216
It would be more consistent if this case successfully created
a stream that then returned end of file on the first attempt at reading.
Furthermore, POSIX.1-2008 does not specify a failure for this case.
@ -232,7 +232,7 @@ Furthermore, POSIX.1-2008 does not specify a failure for this case.
Specifying append mode ("a" or "a+") for
.BR fmemopen ()
sets the initial file position to the first null byte, but
.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=13152
.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=13152
(if the file offset is reset to a location other than
the end of the stream)
does not force subsequent writes to append at the end of the stream.
@ -249,7 +249,7 @@ then, according to POSIX.1-2008,
the initial file position should be set to
the next byte after the end of the buffer.
However, in this case the glibc
.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=13151
.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=13151
.BR fmemopen ()
sets the file position to \-1.
@ -261,7 +261,7 @@ character in
.IR mode .
Thus, for example, "wb+" has the desired effect, but "w+b" does not.
This is inconsistent with the treatment of
.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=12836
.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=12836
.IR mode
by
.BR fopen (3).

4
man3/fopen.3
View File

@ -288,7 +288,7 @@ is attempted only for a file opened for reading.
.TP
.B x
.\" Since glibc 2.0?
.\" FIXME C11 specifies this flag
.\" FIXME . C11 specifies this flag
Open the file exclusively
(like the
.B O_EXCL
@ -333,7 +333,7 @@ When parsing for individual flag characters in
.IR mode
(i.e., the characters preceding the "ccs" specification),
the glibc implementation of
.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=12685
.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=12685
.BR fopen ()
and
.BR freopen ()

1
man3/getaddrinfo.3
View File

@ -37,6 +37,7 @@
.\" 2008-06-18, mtk: many parts rewritten
.\" 2008-12-04, Petr Baudis <pasky@suse.cz>
.\" Describe results ordering and reference /etc/gai.conf.
.\"
.\" FIXME . glibc's 2.9 NEWS file documents DCCP and UDP-lite support
.\" and is SCTP support now also there?
.\"

2
man3/getauxval.3
View File

@ -24,7 +24,7 @@
.\"
.\" See also https://lwn.net/Articles/519085/
.\"
.\" FIXME glibc 2.18 added AT_HWCAP2
.\" FIXME glibc 2.18 added AT_HWCAP2, which needs to e documented
.\"
.TH GETAUXVAL 3 2014-08-19 "GNU" "Linux Programmer's Manual"
.SH NAME

2
man3/getspnam.3
View File

@ -88,7 +88,7 @@ the traditional password database
.BR getpwnam (3)
and
.BR getpwent (3)).
.\" FIXME I've commented out the following for the
.\" FIXME . I've commented out the following for the
.\" moment. The relationship between PAM and nsswitch.conf needs
.\" to be clearly documented in one place, which is pointed to by
.\" the pages for the user, group, and shadow password functions.

2
man3/isalpha.3
View File

@ -240,7 +240,7 @@ The
and
.BR isxdigit ()
functions are thread-safe.
.\" FIXME: need a thread-safety statement about the *_l functions
.\" FIXME . need a thread-safety statement about the *_l functions
.SH VERSIONS
.BR isalnum_l (),
.BR isalpha_l (),

2
man3/isatty.3
View File

@ -57,7 +57,7 @@ is not a valid file descriptor.
refers to a file other than a terminal.
POSIX.1-2001 specifies the error
.BR ENOTTY
.\" FIXME File a bug for this?
.\" FIXME . File a bug for this?
for this case.
.SH ATTRIBUTES
.SS Multithreading (see pthreads(7))

2
man3/mallinfo.3
View File

@ -112,7 +112,7 @@ This function is not specified by POSIX or the C standards.
A similar function exists on many System V derivatives,
and was specified in the SVID.
.SH BUGS
.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=208
.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=208
.\" See the 24 Aug 2011 mail by Paul Pluzhnikov:
.\" "[patch] Fix mallinfo() to accumulate results for all arenas"
.\" on libc-alpha@sourceware.org

4
man3/malloc.3
View File

@ -27,8 +27,8 @@
.\" Documented MALLOC_CHECK_, Wolfram Gloger (wmglo@dent.med.uni-muenchen.de)
.\" 2007-09-15 mtk: added notes on malloc()'s use of sbrk() and mmap().
.\"
.\" FIXME: Review http://austingroupbugs.net/view.php?id=374
.\" to see what changes are req uired on this page.
.\" FIXME . Review http://austingroupbugs.net/view.php?id=374
.\" to see what changes are required on this page.
.\"
.TH MALLOC 3 2014-05-21 "GNU" "Linux Programmer's Manual"
.SH NAME

4
man3/mallopt.3
View File

@ -410,7 +410,7 @@ does not generate an error.
A calculation error within the glibc implementation means that
a call of the form:
.\" FIXME This looks buggy:
.\" FIXME . This looks buggy:
.\" setting the M_MXFAST limit rounds up: (s + SIZE_SZ) & ~MALLOC_ALIGN_MASK)
.\" malloc requests are rounded up:
.\" (req) + SIZE_SZ + MALLOC_ALIGN_MASK) & ~MALLOC_ALIGN_MASK
@ -444,7 +444,7 @@ the bytes of the region are initialized to the byte specified in
However, there is an
.RI off-by- sizeof(size_t)
error in the implementation:
.\" FIXME http://sources.redhat.com/bugzilla/show_bug.cgi?id=12140
.\" FIXME . http://sources.redhat.com/bugzilla/show_bug.cgi?id=12140
instead of initializing precisely the block of memory
being freed by the call
.IR free(p) ,

4
man3/psignal.3
View File

@ -104,11 +104,11 @@ In glibc versions up to 2.12,
had the following bugs:
.IP * 3
In some circumstances, a trailing newline is not printed.
.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=12107
.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=12107
.\" Reportedly now fixed; check glibc 2.13
.IP *
Additional details are not displayed for real-time signals.
.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=12108
.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=12108
.\" Reportedly now fixed; check glibc 2.13
.SH SEE ALSO
.BR sigaction (2),

2
man3/pthread_attr_setinheritsched.3
View File

@ -78,7 +78,7 @@ Threads that are created using
.I attr
take their scheduling attributes from the values specified
by the attributes object.
.\" FIXME what are the defaults for scheduler settings?
.\" FIXME Document the defaults for scheduler settings
.PP
The default setting of the inherit-scheduler attribute in
a newly initialized thread attributes object is

2
man3/qecvt.3
View File

@ -50,7 +50,7 @@ Feature Test Macro Requirements for glibc (see
.BR qgcvt ():
_SVID_SOURCE
.ad b
.\" FIXME The full FTM picture looks to have be something like the
.\" FIXME . The full FTM picture looks to have be something like the
.\" following mess:
.\" glibc 2.20 onward
.\" _DEFAULT_SOURCE

2
man3/queue.3
View File

@ -261,7 +261,7 @@ LIST_INSERT_AFTER(n1, n2, entries);
for (np = head.lh_first; np != NULL; np = np\->entries.le_next)
np\-> ...
.\" FIXME http://sourceware.org/bugzilla/show_bug.cgi?id=1506
.\" FIXME . http://sourceware.org/bugzilla/show_bug.cgi?id=1506
while (head.lh_first != NULL) /* Delete. */
LIST_REMOVE(head.lh_first, entries);
.fi

3
man3/rtnetlink.3
View File

@ -84,8 +84,7 @@ These macros are nonstandard Linux extensions.
.SH BUGS
This manual page is 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 the MTU of a device:
.nf
#include <linux/rtnetlink.h>

2
man3/strerror.3
View File

@ -208,7 +208,7 @@ function is not thread-safe.
The
.BR strerror_r ()
function is thread-safe.
.\" FIXME Need a thread-safety statement about strerror_l()
.\" FIXME . Need a thread-safety statement about strerror_l()
.SH VERSIONS
The
.BR strerror_l ()

2
man3/strftime.3
View File

@ -56,7 +56,7 @@ result in the character array
.I s
of size
.IR max .
.\" FIXME POSIX says: Local timezone information is used as though
.\" FIXME . POSIX says: Local timezone information is used as though
.\" strftime() called tzset(). But this doesn't appear to be the case
.PP
The format specification is a null-terminated string and may contain

4
man3/toupper.3
View File

@ -123,7 +123,7 @@ These functions can be safely used in multithreaded applications,
as long as
.BR setlocale (3)
is not called to change the locale during their execution.
.\" FIXME Add toupper_l() and tolower_l()
.\" FIXME . Add toupper_l() and tolower_l()
.SH CONFORMING TO
.BR toupper (),
.BR tolower ():
@ -141,7 +141,7 @@ locale does not know about umlauts, so no conversion is done for them.
.PP
In some non-English locales, there are lowercase letters with no
corresponding uppercase equivalent;
.\" FIXME: One day the statement about "sharp s" needs to be reworked,
.\" FIXME One day the statement about "sharp s" needs to be reworked,
.\" since there is nowadays a capital "sharp s" that has a codepoint
.\" in Unicode 5.0; see https://en.wikipedia.org/wiki/Capital_%E1%BA%9E
the German sharp s is one example.

2
man3/towlower.3
View File

@ -96,7 +96,7 @@ function is thread-safe with exceptions.
It can be safely used in multithreaded applications, as long as
.BR setlocale (3)
is not called to change the locale during its execution.
.\" FIXME need a thread-safety statement about towlower_l()
.\" FIXME . need a thread-safety statement about towlower_l()
.SH VERSIONS
The
.BR towlower_l ()

4
man3/towupper.3
View File

@ -1,4 +1,4 @@
.\" Copyright (c) Bruno Haible <haible@clisp.cons.org>
.\" and Copyright (C) 2014 Michael Kerrisk <mtk.manpages@gmail.com>
.\"
.\" %%%LICENSE_START(GPLv2+_DOC_ONEPARA)
@ -96,7 +96,7 @@ function is thread-safe with exceptions.
It can be safely used in multithreaded applications, as long as
.BR setlocale (3)
is not called to change the locale during its execution.
.\" FIXME need a thread-safety statement about towupper_l()
.\" FIXME . need a thread-safety statement about towupper_l()
.SH VERSIONS
The
.BR towupper_l ()

2
man4/initrd.4
View File

@ -310,7 +310,7 @@ as well as
and
.BR pivot_root (8)
for information on the modern method of changing the root filesystem.
.\" FIXME the manual page should describe the pivot_root mechanism.
.\" FIXME . Should this manual page describe the pivot_root mechanism?
.\"
.\"
.\"

37
man5/locale.5
View File

@ -217,12 +217,13 @@ The definition starts with the string
in the first column.
The following keywords are allowed:
.\" FIXME translit_start + translit_end are not documented
.\" FIXME 'charclass' is not documented
.\" FIXME 'charconv' is not documented
.\" FIXME 'outdigit' is not documented
.\" FIXME 'include' is not documented
.\" FIXME 'map' (to_inpunct, to_outpunct) is not documented
.\" FIXME The following LC_CTYPE keywords are not documented:
.\" translit_start + translit_end
.\" charclass
.\" charconv
.\" outdigit
.\" include
.\" map (to_inpunct, to_outpunct)
.TP
.I upper
followed by a list of uppercase letters.
@ -411,7 +412,7 @@ The
definition ends with the string
.IR "END LC_CTYPE" .
.SS LC_COLLATE
.\" FIXME: the description of LC_COLLATE lacks a lot of details
.\" FIXME The description of LC_COLLATE lacks a lot of details
The
.B LC_COLLATE
category defines the rules for collating characters.
@ -423,8 +424,9 @@ The definition starts with the string
in the first column.
The following keywords are allowed:
.\" FIXME 'script' is not documented
.\" FIXME 'symbol-equivalence' is not documented
.\" FIXME The following LC_COLLATE keywords are not documented:
.\" script
.\" symbol-equivalence
.TP
.I collating-element
followed by the definition of a collating-element symbol
@ -445,10 +447,11 @@ or
The order definition consists of lines that describe the order
and is terminated with the keyword
.IR order_end .
.\" FIXME 'reorder-after' is not documented
.\" FIXME 'reorder-end' is not documented
.\" FIXME 'reorder-sections-after' is not documented
.\" FIXME 'reorder-sections-end' is not documented
.\" FIXME The following LC_COLLATE keywords are not documented:
.\" reorder-after
.\" reorder-end
.\" reorder-sections-after
.\" reorder-sections-end
.PP
The
.B LC_COLLATE
@ -966,8 +969,12 @@ The definition starts with the string
in the first column.
The following keywords are allowed:
.\" FIXME 'era', 'era_d_fmt', 'era_d_t_fmt', 'era_t_fmt', are not documented
.\" FIXME 'timezone' is not documented
.\" FIXME The following LC_TIME keywords are not documented:
.\" era
.\" era_d_fmt
.\" era_d_t_fmt
.\" era_t_fmt
.\" timezone
.TP
.I abday
followed by a list of abbreviated names of the days of the week.

13
man5/proc.5
View File

@ -48,7 +48,7 @@
.\" 2008-06-19, mtk, Documented /proc/[pid]/status.
.\" 2008-07-15, mtk, added /proc/config.gz
.\"
.\" FIXME cross check against Documentation/filesystems/proc.txt
.\" FIXME . cross check against Documentation/filesystems/proc.txt
.\" to see what information could be imported from that file
.\" into this file.
.\"
@ -1113,10 +1113,12 @@ are not available if the main thread has already terminated
.BR pthread_exit (3)).
.\" FIXME Describe /proc/[pid]/seccomp
.\" Added in 2.6.12
.\"
.\" FIXME Describe /proc/[pid]/sessionid
.\" Added in 2.6.25; read-only; only readable by real UID
.\" commit 1e0bd7550ea9cf474b1ad4c6ff5729a507f75fdc
.\" CONFIG_AUDITSYSCALL
.\"
.\" FIXME Describe /proc/[pid]/sched
.\" Added in 2.6.23
.\" CONFIG_SCHED_DEBUG, and additional fields if CONFIG_SCHEDSTATS
@ -2640,7 +2642,8 @@ It became once more nonoptionally enabled in Linux 2.4.
Next, it was deprecated in Linux 2.6 (still available with
.B CONFIG_PCI_LEGACY_PROC
set), and finally removed altogether since Linux 2.6.17.
.\" FIXME /proc/sched_debug
.\" FIXME Document /proc/sched_debug
.\"
.\" .TP
.\" .IR /proc/sched_debug " (since Linux 2.6.23)"
.\" See also /proc/[pid]/sched
@ -2770,7 +2773,7 @@ that the system spent in various states:
.TP
.I idle
(4) Time spent in the idle task.
.\" FIXME Actually, the following info about the /proc/stat 'cpu' field
.\" FIXME . Actually, the following info about the /proc/stat 'cpu' field
.\" does not seem to be quite right (at least in 2.6.12 or 3.6):
.\" the idle time in /proc/uptime does not quite match this value
This value should be USER_HZ times the
@ -2809,7 +2812,7 @@ out (from disk).
\fIswap 1 0\fP
The number of swap pages that have been brought in and out.
.TP
.\" FIXME The following is not the full picture for the 'intr' of
.\" FIXME . The following is not the full picture for the 'intr' of
.\" /proc/stat on 2.6:
\fIintr 1462898\fP
This line shows counts of interrupts serviced since boot time,
@ -4124,7 +4127,7 @@ Linux version 1.0.9 (quinlan@phaze) #1 Sat May 14 01:51:54 EDT 1994
.ft
.in +2
.fi
.\" FIXME 2.6.13 seems to have /proc/vmcore implemented
.\" FIXME 2.6.13 seems to have /proc/vmcore implemented; document this
.\" See Documentation/kdump/kdump.txt
.\" commit 666bfddbe8b8fd4fd44617d6c55193d5ac7edb29
.\" Needs CONFIG_VMCORE

2
man7/bootparam.7
View File

@ -24,7 +24,7 @@
.\" This man page written 950814 by aeb, based on Paul Gortmaker's HOWTO
.\" (dated v1.0.1, 15/08/95).
.\" Major update, aeb, 970114.
.\" FIXME ? The use of quotes on this page is inconsistent with the
.\" FIXME . The use of quotes on this page is inconsistent with the
.\" rest of man-pages.
.\"
.TH BOOTPARAM 7 2014-06-13 "Linux" "Linux Programmer's Manual"

5
man7/capabilities.7
View File

@ -148,7 +148,7 @@ set the set-group-ID bit for a file whose GID does not match
the filesystem or any of the supplementary GIDs of the calling process.
.TP
.B CAP_IPC_LOCK
.\" FIXME As at Linux 3.2, there are some strange uses of this capability
.\" FIXME . As at Linux 3.2, there are some strange uses of this capability
.\" in other places; they probably should be replaced with something else.
Lock memory
.RB ( mlock (2),
@ -166,7 +166,7 @@ This includes use of the
.BR ioctl (2)
.B KDSIGACCEPT
operation.
.\" FIXME CAP_KILL also has an effect for threads + setting child
.\" FIXME . CAP_KILL also has an effect for threads + setting child
.\" termination signal to other than SIGCHLD: without this
.\" capability, the termination signal reverts to SIGCHLD
.\" if the child does an exec(). What is the rationale
@ -456,6 +456,7 @@ to be migrated to arbitrary nodes;
.\" migrate_pages(2):
.\" do_migrate_pages(mm, &old, &new,
.\" capable(CAP_SYS_NICE) ? MPOL_MF_MOVE_ALL : MPOL_MF_MOVE);
.\" Document this.
.IP *
apply
.BR move_pages (2)

6
man7/ddp.7
View File

@ -116,7 +116,7 @@ wildcard and also implies \(lqthis node.\(rq The value of
.B ATADDR_BCAST
is a link
local broadcast address.
.\" FIXME this doesn't make sense [johnl]
.\" FIXME . this doesn't make sense [johnl]
.SS Socket options
No protocol-specific socket options are supported.
.SS /proc interfaces
@ -145,9 +145,9 @@ changed.
All ioctls described in
.BR socket (7)
apply to DDP.
.\" FIXME Add a section about multicasting
.\" FIXME . Add a section about multicasting
.SH ERRORS
.\" FIXME document all errors. We should really fix the kernels to
.\" FIXME . document all errors. We should really fix the kernels to
.\" give more uniform error returns (ENOMEM vs ENOBUFS, EPERM vs
.\" EACCES etc.)
.TP

2
man7/fanotify.7
View File

@ -488,7 +488,7 @@ In this case, events are lost.
As of Linux 3.15,
the following bugs exist:
.IP * 3
.\" FIXME: A patch was proposed.
.\" FIXME . A patch was proposed.
When an event is generated,
no check is made to see whether the user ID of the
receiving process has authorization to read or write the file

2
man7/icmp.7
View File

@ -46,7 +46,7 @@ The parameters can be accessed by reading or writing files in the directory
.IR /proc/sys/net/ipv4/ .
Most of these parameters are rate limitations for specific ICMP types.
Linux 2.2 uses a token bucket filter to limit ICMPs.
.\" FIXME better description needed
.\" FIXME . better description needed
The value is the timeout in jiffies until the token bucket filter is
cleared after a burst.
A jiffy is a system dependent unit, usually 10ms on i386 and

4
man7/inotify.7
View File

@ -752,7 +752,7 @@ and also the possibility that there may not be any
.B IN_MOVED_TO
event.
.SH BUGS
.\" FIXME kernel commit 611da04f7a31b2208e838be55a42c7a1310ae321
.\" FIXME . kernel commit 611da04f7a31b2208e838be55a42c7a1310ae321
.\" implies that unmount events were buggy 2.6.11 to 2.6.36
.\"
In kernels before 2.6.16, the
@ -806,7 +806,7 @@ and then recycle that watch descriptor.
For this reason, and because there have been no reports
of the bug occurring in real-world applications,
as of Linux 3.15,
.\" FIXME https://bugzilla.kernel.org/show_bug.cgi?id=77111
.\" FIXME . https://bugzilla.kernel.org/show_bug.cgi?id=77111
no kernel changes have yet been made to eliminate this possible bug.
.SH EXAMPLE
The following program demonstrates the usage of the inotify API.

11
man7/ip.7
View File

@ -10,7 +10,7 @@
.\"
.\" $Id: ip.7,v 1.19 2000/12/20 18:10:31 ak Exp $
.\"
.\" FIXME: The following socket options are yet to be documented
.\" FIXME The following socket options are yet to be documented
.\" IP_XFRM_POLICY (2.5.48)
.\" Needs CAP_NET_ADMIN
.\" IP_IPSEC_POLICY (2.5.47)
@ -56,7 +56,7 @@ described in RFC\ 791 and RFC\ 1122.
.B ip
contains a level 2 multicasting implementation conforming to RFC\ 1112.
It also contains an IP router including a packet filter.
.\" FIXME has someone verified that 2.1 is really 1812 compliant?
.\" FIXME . has someone verified that 2.1 is really 1812 compliant?
.PP
The programming interface is BSD-sockets compatible.
For more information on sockets, see
@ -499,7 +499,7 @@ take it into account for their packet retransmit strategy.
To bootstrap the path MTU discovery process on unconnected sockets, it
is possible to start with a big datagram size
(up to 64K-headers bytes long) and let it shrink by updates of the path MTU.
.\" FIXME this is an ugly hack
.\" FIXME . this is an ugly hack
To get an initial estimate of the
path MTU, connect a datagram socket to the destination address using
@ -629,7 +629,7 @@ struct in_pktinfo {
.fi
.in
.IP
.\" FIXME elaborate on that.
.\" FIXME . elaborate on that.
.I ipi_ifindex
is the unique index of the interface the packet was received on.
.I ipi_spec_dst
@ -1070,8 +1070,8 @@ Contains an integer with the number of bytes.
See
.BR arp (7).
.\" FIXME Document the conf/*/* interfaces
.\"
.\" FIXME Document the route/* interfaces
.\" FIXME document them all
.SS Ioctls
All ioctls described in
.BR socket (7)
@ -1286,4 +1286,3 @@ does not work in some 2.2 kernels.
RFC\ 791 for the original IP specification.
RFC\ 1122 for the IPv4 host requirements.
RFC\ 1812 for the IPv4 router requirements.
.\" FIXME autobind INADDR REUSEADDR

1
man7/ipv6.7
View File

@ -349,7 +349,6 @@ The default value for this flag is defined by the contents of the file
The default value for that file is 0 (false).
.\" FLOWLABEL_MGR, FLOWINFO_SEND
.SH ERRORS
.\" FIXME document all errors.
.TP
.B ENODEV
The user tried to

2
man7/netdevice.7
View File

@ -328,7 +328,7 @@ will be returned.
.\" .IR ifr_slave .
.\" Setting the slave device is a privileged operation.
.\" .PP
.\" FIXME add amateur radio stuff.
.\" FIXME . add amateur radio stuff.
.PP
Most protocols support their own ioctls to configure protocol-specific
interface options.

2
man7/netlink.7
View File

@ -200,7 +200,7 @@ NLM_F_MATCH:T{
Return all entries matching criteria passed in message content.
Not implemented yet.
T}
.\" FIXME NLM_F_ATOMIC is not used any more?
.\" FIXME NLM_F_ATOMIC is not used anymore?
NLM_F_ATOMIC:Return an atomic snapshot of the table.
NLM_F_DUMP:T{
Convenience macro; equivalent to

6
man7/path_resolution.7
View File

@ -201,7 +201,7 @@ Similarly, Linux uses the fsgid ("filesystem group ID")
instead of the effective group ID.
See
.BR setfsgid (2).
.\" FIXME say something about filesystem mounted read-only ?
.\" FIXME . say something about filesystem mounted read-only ?
.SS Bypassing permission checks: superuser and capabilities
On a traditional UNIX system, the superuser
.RI ( root ,
@ -232,8 +232,8 @@ The
.B CAP_DAC_READ_SEARCH
capability grants read and search permission
on directories, and read permission on ordinary files.
.\" FIXME say something about immutable files
.\" FIXME say something about ACLs
.\" FIXME . say something about immutable files
.\" FIXME . say something about ACLs
.SH SEE ALSO
.BR readlink (2),
.BR capabilities (7),

4
man7/rtld-audit.7
View File

@ -388,7 +388,7 @@ argument points to a bit mask that conveys information about,
and can be used to modify subsequent auditing of, this PLT entry, as for
.BR la_symbind* ().
.\" FIXME is the following correct?
.\" FIXME . Is the following correct?
The
.IR framesizep
argument points to a
@ -495,7 +495,7 @@ specifying more than one audit library in
.B LD_AUDIT
results in a run-time crash.
This is reportedly fixed in glibc 2.10.
.\" FIXME Specifying multiple audit libraries doesn't work on GNU.
.\" FIXME . Specifying multiple audit libraries doesn't work on GNU.
.\" My simple tests on Solaris work okay, but not on Linux -- mtk, Jan 2009
.\" glibc bug filed: http://sourceware.org/bugzilla/show_bug.cgi?id=9733
.\" Reportedly, this is fixed on 16 Mar 2009 (i.e., for glibc 2.10)

8
man7/rtnetlink.7
View File

@ -38,7 +38,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:
@ -77,7 +77,7 @@ struct ifinfomsg {
};
.fi
.\" FIXME ifi_type
.\" FIXME Document ifinfomsg.ifi_type
.I ifi_flags
contains the device flags, see
.BR netdevice (7);
@ -171,7 +171,7 @@ IFA_BROADCAST:raw protocol address:broadcast address.
IFA_ANYCAST:raw protocol address:anycast address
IFA_CACHEINFO:struct ifa_cacheinfo:Address information.
.TE
.\" FIXME struct ifa_cacheinfo
.\" FIXME Document struct ifa_cacheinfo
.TP
.BR RTM_NEWROUTE ", " RTM_DELROUTE ", " RTM_GETROUTE
Create, remove or receive information about a network route.
@ -378,7 +378,7 @@ NTF_PROXY:a proxy arp entry
NTF_ROUTER:an IPv6 router
.TE
.\" FIXME
.\" FIXME .
.\" document the members of the struct better
The
.I rtattr

3
man7/sched.7
View File

@ -280,7 +280,7 @@ structure; see
.BR sched_setattr (2).
These fields express value in nanoseconds.
.\" FIXME It looks as though specifying sched_period as 0 means
.\" "make sched_period the same as sched_deadline", right?
.\" "make sched_period the same as sched_deadline".
.\" This needs to be documented.
If
.IR sched_period
@ -352,7 +352,6 @@ will yield the current job and wait for a new period to begin.
.\" fails with EINVAL, but sched_getscheduler() succeeds.
.\" Is that intended? (Why?)
.\"
.\"
.SS SCHED_OTHER: Default Linux time-sharing scheduling
\fBSCHED_OTHER\fP can be used at only static priority 0.
\fBSCHED_OTHER\fP is the standard Linux time-sharing scheduler that is

6
man7/signal.7
View File

@ -676,7 +676,7 @@ Socket interfaces:
.BR send (2),
.BR sendto (2),
and
.\" FIXME What about sendmmsg()?
.\" FIXME . What about sendmmsg()?
.BR sendmsg (2),
unless a timeout has been set on the socket (see below).
.IP *
@ -739,7 +739,7 @@ has been set on the socket using
.BR send (2),
.BR sendto (2),
and
.\" FIXME What about sendmmsg()?
.\" FIXME . What about sendmmsg()?
.BR sendmsg (2).
.IP *
Interfaces used to wait for signals:
@ -819,7 +819,7 @@ has been set on the socket using
.BR send (2),
.BR sendto (2),
and
.\" FIXME What about sendmmsg()?
.\" FIXME . What about sendmmsg()?
.BR sendmsg (2),
if a send timeout
.RB ( SO_SNDTIMEO )

2
man7/socket.7
View File

@ -288,7 +288,7 @@ Unless otherwise noted,
.I optval
is a pointer to an
.IR int .
.\" FIXME
.\" FIXME .
.\" In the list below, the text used to describe argument types
.\" for each socket option should be more consistent
.\"

4
man7/svipc.7
View File

@ -22,10 +22,10 @@
.\" the source, must acknowledge the copyright and authors of this work.
.\" %%%LICENSE_END
.\"
.\" FIXME There is now duplication of some of the information
.\" FIXME . There is now duplication of some of the information
.\" below in semctl.2, msgctl.2, and shmctl.2 -- MTK, Nov 04
.\"
.\" FIXME Ultimately, there should probably be
.\" FIXME . Ultimately, there should probably be
.\" svmq_overview(7), svshm_overview(7), and sem_overview(7)
.\" that provide an overview of each System V IPC mechanism.
.\" In that case:

2
man7/tcp.7
View File

@ -1199,7 +1199,7 @@ is returned.
.B SIOCOUTQ
is defined in
.IR <linux/sockios.h> .
.\" FIXME http://sources.redhat.com/bugzilla/show_bug.cgi?id=12002,
.\" FIXME . http://sources.redhat.com/bugzilla/show_bug.cgi?id=12002,
.\" filed 2010-09-10, may cause SIOCOUTQ to be defined in glibc headers
Alternatively,
you can use the synonymous

2
man7/unix.7
View File

@ -306,7 +306,7 @@ is returned.
.B SIOCINQ
is defined in
.IR <linux/sockios.h> .
.\" FIXME http://sources.redhat.com/bugzilla/show_bug.cgi?id=12002,
.\" FIXME . http://sources.redhat.com/bugzilla/show_bug.cgi?id=12002,
.\" filed 2010-09-10, may cause SIOCINQ to be defined in glibc headers
Alternatively,
you can use the synonymous

4
man8/ld.so.8
View File

@ -417,8 +417,8 @@ For security reasons, since glibc 2.3.5,
is ignored for set-user-ID/set-group-ID binaries.
.\" FIXME
.\" Document LD_TRACE_PRELINKING (e.g.: LD_TRACE_PRELINKING=libx1.so ./prog)
.\" Since glibc 2.3
.\" Also enables DL_DEBUG_PRELINK
.\" Available since glibc 2.3
.\" Also enables DL_DEBUG_PRELINK
.TP
.B LD_USE_LOAD_BIAS
.\" http://sources.redhat.com/ml/libc-hacker/2003-11/msg00127.html