man*/: ffix

Signed-off-by: Alejandro Colomar <alx@kernel.org>

25 files changed, 54 insertions, 51 deletions

diff --git a/man2/chroot.2 b/man2/chroot.2
index 9e99b1bae..8a2a78502 100644
--- a/man2/chroot.2
+++ b/man2/chroot.2
@@ -150,7 +150,7 @@ The root directory is left unchanged by
 .BR execve (2).
 .PP
 The magic symbolic link,
-.IR /proc/[pid]/root ,
+.IR /proc/ pid /root ,
 can be used to discover a process's root directory; see
 .BR proc (5)
 for details.
diff --git a/man2/ioctl_ns.2 b/man2/ioctl_ns.2
index ff2df4835..859fab4ad 100644
--- a/man2/ioctl_ns.2
+++ b/man2/ioctl_ns.2
@@ -162,7 +162,7 @@ operations can return the following errors:
 .B ENOTTY
 .I fd
 does not refer to a
-.I /proc/[pid]/ns/*
+.IR /proc/ pid /ns/ *
 file.
 .SH STANDARDS
 Linux.
diff --git a/man2/ioprio_set.2 b/man2/ioprio_set.2
index 3cd15b47d..a232686c8 100644
--- a/man2/ioprio_set.2
+++ b/man2/ioprio_set.2
@@ -232,7 +232,7 @@ as 0 can be used to reset to the default I/O scheduling behavior.
 .SS Selecting an I/O scheduler
 I/O schedulers are selected on a per-device basis via the special
 file
-.IR /sys/block/<device>/queue/scheduler .
+.IR /sys/block/ device /queue/scheduler .
 .PP
 One can view the current I/O scheduler via the
 .I /sys
diff --git a/man2/madvise.2 b/man2/madvise.2
index 46fd8763b..529b14835 100644
--- a/man2/madvise.2
+++ b/man2/madvise.2
@@ -490,7 +490,7 @@ that are known not to be useful in a core dump.
 The effect of
 .B MADV_DONTDUMP
 takes precedence over the bit mask that is set via the
-.I /proc/[pid]/coredump_filter
+.IR /proc/ pid /coredump_filter
 file (see
 .BR core (5)).
 .TP
diff --git a/man2/memfd_create.2 b/man2/memfd_create.2
index fcf2fab4d..3274b3983 100644
--- a/man2/memfd_create.2
+++ b/man2/memfd_create.2
@@ -313,7 +313,7 @@ since they are running under the same user ID.
 Therefore, file sealing would not normally be necessary.)
 .IP \[bu]
 The second process opens the file
-.IR /proc/<pid>/fd/<fd> ,
+.IR /proc/ pid /fd/ fd,
 where
 .I <pid>
 is the PID of the first process (the one that called
diff --git a/man2/mlock.2 b/man2/mlock.2
index d36e8680c..30828fbdf 100644
--- a/man2/mlock.2
+++ b/man2/mlock.2
@@ -276,7 +276,7 @@ is page aligned, so portable applications should ensure this.
 The
 .I VmLck
 field of the Linux-specific
-.I /proc/[pid]/status
+.IR /proc/ pid /status
 file shows how many kilobytes of memory the process with ID
 .I PID
 has locked using
diff --git a/man2/mmap.2 b/man2/mmap.2
index 04f117e02..8b8e11b1a 100644
--- a/man2/mmap.2
+++ b/man2/mmap.2
@@ -796,7 +796,7 @@ is hazardous because it forcibly removes preexisting mappings,
 making it easy for a multithreaded process to corrupt its own address space.
 .PP
 For example, suppose that thread A looks through
-.I /proc/<pid>/maps
+.IR /proc/ pid /maps
 in order to locate an unused address range that it can map using
 .BR MAP_FIXED ,
 while thread B simultaneously acquires part or all of that same
@@ -1026,10 +1026,10 @@ main(int argc, char *argv[])
 .PP
 The descriptions of the following files in
 .BR proc (5):
-.IR /proc/[pid]/maps ,
-.IR /proc/[pid]/map_files ,
+.IR /proc/ pid /maps ,
+.IR /proc/ pid /map_files ,
 and
-.IR /proc/[pid]/smaps .
+.IR /proc/ pid /smaps .
 .PP
 B.O. Gallmeister, POSIX.4, O'Reilly, pp. 128\[en]129 and 389\[en]391.
 .\"
diff --git a/man2/mount.2 b/man2/mount.2
index bab18bcae..7a9cf4f82 100644
--- a/man2/mount.2
+++ b/man2/mount.2
@@ -718,7 +718,7 @@ A bind operation
 was requested where
 .I source
 referred a mount namespace magic link (i.e., a
-.I /proc/[pid]/ns/mnt
+.IR /proc/ pid /ns/mnt
 magic link or a bind mount to such a link)
 and the propagation type of the parent mount of
 .I target
@@ -938,16 +938,16 @@ the parent of the new mount is the previous mount that was stacked
 at that location.
 .PP
 The parental relationship between mounts can be discovered via the
-.I /proc/[pid]/mountinfo
+.IR /proc/ pid /mountinfo
 file (see below).
 .\"
-.SS /proc/[pid]/mounts and /proc/[pid]/mountinfo
+.SS \fI/proc/\fPpid\fI/mounts\fP and \fI/proc/\fPpid\fI/mountinfo\fP
 The Linux-specific
-.I /proc/[pid]/mounts
+.IR /proc/ pid /mounts
 file exposes the list of mounts in the mount
 namespace of the process with the specified ID.
 The
-.I /proc/[pid]/mountinfo
+.IR /proc/ pid /mountinfo
 file exposes even more information about mounts,
 including the propagation type and mount ID information that makes it
 possible to discover the parental relationship between mounts.
diff --git a/man2/open.2 b/man2/open.2
index d9386c48f..77c06b55d 100644
--- a/man2/open.2
+++ b/man2/open.2
@@ -1491,11 +1491,11 @@ and
 fields are set to the current time.
 .PP
 The files in the
-.I /proc/[pid]/fd
+.IR /proc/ pid /fd
 directory show the open file descriptors of the process with the PID
 .IR pid .
 The files in the
-.I /proc/[pid]/fdinfo
+.IR /proc/ pid /fdinfo
 directory show even more information about these file descriptors.
 See
 .BR proc (5)
diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
index ee65d20d0..61a62f7f4 100644
--- a/man2/perf_event_open.2
+++ b/man2/perf_event_open.2
@@ -2145,7 +2145,7 @@ This indicates there is extended data available (currently not used).
 .\" commit 930e6fcd2bcce9bcd9d4aa7e755678d33f3fe6f4
 This bit is not set by the kernel.
 It is reserved for the user-space perf utility to indicate that
-.I /proc/i[pid]/maps
+.IR /proc/ pid /maps
 parsing was taking too long and was stopped, and thus the mmap
 records may be truncated.
 .RE
diff --git a/man2/pidfd_open.2 b/man2/pidfd_open.2
index 68e4c23fa..701abd419 100644
--- a/man2/pidfd_open.2
+++ b/man2/pidfd_open.2
@@ -187,7 +187,7 @@ The
 system call is the preferred way of obtaining a PID file descriptor
 for an already existing process.
 The alternative is to obtain a file descriptor by opening a
-.I /proc/[pid]
+.IR /proc/ pid
 directory.
 However, the latter technique is possible only if the
 .BR proc (5)
diff --git a/man2/seccomp_unotify.2 b/man2/seccomp_unotify.2
index 94bbf2b27..4fde10db1 100644
--- a/man2/seccomp_unotify.2
+++ b/man2/seccomp_unotify.2
@@ -980,7 +980,7 @@ in order to continue a system call, the supervisor should be sure that
 another security mechanism or the kernel itself will sufficiently block
 the system call if its arguments are rewritten to something unsafe.
 .\"
-.SS Caveats regarding the use of /proc/[tid]/mem
+.SS Caveats regarding the use of \fI/proc/\fPtid\fI/mem\fP
 The discussion above noted the need to use the
 .B SECCOMP_IOCTL_NOTIF_ID_VALID
 .BR ioctl (2)
diff --git a/man2/setns.2 b/man2/setns.2
index 93e9933fc..b4ce783f4 100644
--- a/man2/setns.2
+++ b/man2/setns.2
@@ -35,7 +35,7 @@ The
 .I nstype
 argument is interpreted differently in each case.
 .\"
-.SS fd refers to a /proc/[pid]/ns/ link
+.SS fd refers to a \fI/proc/\fPpid\fI/ns/\fP link
 If
 .I fd
 refers to a
diff --git a/man3/getauxval.3 b/man3/getauxval.3
index a0e2e5df5..25a88bf35 100644
--- a/man3/getauxval.3
+++ b/man3/getauxval.3
@@ -255,7 +255,7 @@ $ LD_SHOW_AUXV=1 sleep 1
 .PP
 The auxiliary vector of any process can (subject to file permissions)
 be obtained via
-.IR /proc/[pid]/auxv ;
+.IR /proc/ pid /auxv ;
 see
 .BR proc (5)
 for more information.
diff --git a/man3/pthread_setname_np.3 b/man3/pthread_setname_np.3
index 0e326bc5c..71c871497 100644
--- a/man3/pthread_setname_np.3
+++ b/man3/pthread_setname_np.3
@@ -78,7 +78,7 @@ and
 is too small to hold the thread name.
 .PP
 If either of these functions fails to open
-.IR /proc/self/task/[tid]/comm ,
+.IR /proc/self/task/ tid /comm ,
 then the call may fail with one of the errors described in
 .BR open (2).
 .SH ATTRIBUTES
@@ -111,7 +111,7 @@ internally writes to the thread-specific
 file under the
 .I /proc
 filesystem:
-.IR /proc/self/task/[tid]/comm .
+.IR /proc/self/task/ tid /comm .
 .BR pthread_getname_np ()
 retrieves it from the same location.
 .SH EXAMPLES
diff --git a/man4/cciss.4 b/man4/cciss.4
index 35ddda6d3..5db37159e 100644
--- a/man4/cciss.4
+++ b/man4/cciss.4
@@ -168,39 +168,39 @@ cciss/c2d0:   36.38GB       RAID 0
 .\"
 .SS Files in /sys
 .TP
-.I /sys/bus/pci/devices/<dev>/ccissX/cXdY/model
+.IR /sys/bus/pci/devices/ dev /cciss X /c X d Y /model
 Displays the SCSI INQUIRY page 0 model for logical drive
 .I Y
 of controller
 .IR X .
 .TP
-.I /sys/bus/pci/devices/<dev>/ccissX/cXdY/rev
+.IR /sys/bus/pci/devices/ dev /cciss X /c X d Y /rev
 Displays the SCSI INQUIRY page 0 revision for logical drive
 .I Y
 of controller
 .IR X .
 .TP
-.I /sys/bus/pci/devices/<dev>/ccissX/cXdY/unique_id
+.IR /sys/bus/pci/devices/ dev /cciss X /c X d Y /unique_id
 Displays the SCSI INQUIRY page 83 serial number for logical drive
 .I Y
 of controller
 .IR X .
 .TP
-.I /sys/bus/pci/devices/<dev>/ccissX/cXdY/vendor
+.IR /sys/bus/pci/devices/ dev /cciss X /c X d Y /vendor
 Displays the SCSI INQUIRY page 0 vendor for logical drive
 .I Y
 of controller
 .IR X .
 .TP
-.I /sys/bus/pci/devices/<dev>/ccissX/cXdY/block:cciss!cXdY
+.IR /sys/bus/pci/devices/ dev /cciss X /c X d Y /block:cciss!c X d Y
 A symbolic link to
-.IR /sys/block/cciss!cXdY .
+.IR /sys/block/cciss!c X d Y.
 .TP
-.I /sys/bus/pci/devices/<dev>/ccissX/rescan
+.IR /sys/bus/pci/devices/ dev /cciss X /rescan
 When this file is written to, the driver rescans the controller
 to discover any new, removed, or modified logical drives.
 .TP
-.I /sys/bus/pci/devices/<dev>/ccissX/resettable
+.IR /sys/bus/pci/devices/ dev /cciss X /resettable
 A value of 1 displayed in this file indicates that
 the "reset_devices=1" kernel parameter (used by
 .BR kdump )
@@ -209,19 +209,19 @@ A value of 0 indicates that the
 "reset_devices=1" kernel parameter will not be honored.
 Some models of Smart Array are not able to honor this parameter.
 .TP
-.I /sys/bus/pci/devices/<dev>/ccissX/cXdY/lunid
+.IR /sys/bus/pci/devices/ dev /cciss X /c X d Y /lunid
 Displays the 8-byte LUN ID used to address logical drive
 .I Y
 of controller
 .IR X .
 .TP
-.I /sys/bus/pci/devices/<dev>/ccissX/cXdY/raid_level
+.IR /sys/bus/pci/devices/ dev /cciss X /c X d Y /raid_level
 Displays the RAID level of logical drive
 .I Y
 of controller
 .IR X .
 .TP
-.I /sys/bus/pci/devices/<dev>/ccissX/cXdY/usage_count
+.IR /sys/bus/pci/devices/ dev /cciss X /c X d Y /usage_count
 Displays the usage count (number of opens) of logical drive
 .I Y
 of controller
diff --git a/man5/utmp.5 b/man5/utmp.5
index eefb8241c..ec68b97e6 100644
--- a/man5/utmp.5
+++ b/man5/utmp.5
@@ -176,7 +176,8 @@ with null bytes.
 and other terminal emulators directly create a
 \fBUSER_PROCESS\fP record and generate the \fIut_id\fP by using the
 string that suffix part of the terminal name (the characters
-following \fI/dev/[pt]ty\fP).
+following
+.IR /dev/ [pt] ty ).
 If they find a \fBDEAD_PROCESS\fP for this ID,
 they recycle it, otherwise they create a new entry.
 If they can, they
diff --git a/man7/cgroups.7 b/man7/cgroups.7
index 7670ab9a5..6ac3f59e1 100644
--- a/man7/cgroups.7
+++ b/man7/cgroups.7
@@ -1796,7 +1796,7 @@ or 0 if it has been disabled (via the
 kernel command-line boot parameter).
 .RE
 .TP
-.IR /proc/[pid]/cgroup " (since Linux 2.6.24)"
+.IR /proc/ pid /cgroup " (since Linux 2.6.24)"
 This file describes control groups to which the process
 with the corresponding PID belongs.
 The displayed information differs for
diff --git a/man7/cpuset.7 b/man7/cpuset.7
index dffb3563e..3bda1dc79 100644
--- a/man7/cpuset.7
+++ b/man7/cpuset.7
@@ -342,13 +342,13 @@ See \fBScheduler Relax Domain Level\fR, below, for further details.
 In addition to the above pseudo-files in each directory below
 .IR /dev/cpuset ,
 each process has a pseudo-file,
-.IR /proc/<pid>/cpuset ,
+.IR /proc/ pid /cpuset ,
 that displays the path of the process's cpuset directory
 relative to the root of the cpuset filesystem.
 .\" ================== proc status ==================
 .PP
 Also the
-.I /proc/<pid>/status
+.IR /proc/ pid /status
 file for each process has four added lines,
 displaying the process's
 .I Cpus_allowed
@@ -854,7 +854,7 @@ CPUs and memory nodes.
 .SS Mask format
 The \fBMask Format\fR is used to represent CPU and memory-node bit masks
 in the
-.I /proc/<pid>/status
+.IR /proc/ pid /status
 file.
 .PP
 This format displays each 32-bit
@@ -1240,7 +1240,7 @@ a cpuset into a different directory.
 Attempted to
 .BR read (2)
 a
-.I /proc/<pid>/cpuset
+.IR /proc/ pid /cpuset
 file for a cpuset path that is longer than the kernel page size.
 .TP
 .B ENAMETOOLONG
diff --git a/man7/fanotify.7 b/man7/fanotify.7
index 3963e7420..9026375be 100644
--- a/man7/fanotify.7
+++ b/man7/fanotify.7
@@ -815,7 +815,7 @@ Upon
 outstanding permission events will be set to allowed.
 .SS /proc interfaces
 The file
-.I /proc/[pid]/fdinfo/[fd]
+.IR /proc/ pid /fdinfo/ fd
 contains information about fanotify marks for file descriptor
 .I fd
 of process
diff --git a/man7/hier.7 b/man7/hier.7
index 7c9f69000..dc254c269 100644
--- a/man7/hier.7
+++ b/man7/hier.7
@@ -293,7 +293,7 @@ These directories are variants of
 .I /usr/lib
 on system which support more than one binary format requiring separate
 libraries, except that the symbolic link
-.I /usr/lib<qual>/X11
+.IR /usr/lib qual /X11
 is not required (optional).
 .TP
 .I /usr/lib/X11
@@ -404,7 +404,7 @@ Locale information goes here (optional).
 .I /usr/share/man
 Manual pages go here in subdirectories according to the man page sections.
 .TP
-.I /usr/share/man/<locale>/man[1\-9]
+.IR /usr/share/man/ locale /man[1\-9]
 These directories contain manual pages for the
 specific locale in source code form.
 Systems which use a unique language and code set for all manual pages
diff --git a/man7/namespaces.7 b/man7/namespaces.7
index 97d9c1bce..209be5f19 100644
--- a/man7/namespaces.7
+++ b/man7/namespaces.7
@@ -128,7 +128,7 @@ no privilege is required to create a user namespace.
 .\"
 .\" ==================== The /proc/[pid]/ns/ directory ====================
 .\"
-.SS The /proc/[pid]/ns/ directory
+.SS The \fI/proc/\fPpid\fI/ns/\fP directory
 Each process has a
 .IR /proc/ pid /ns/
 .\" See commit 6b4e306aa3dc94a0545eb9279475b1ab6209a31f
diff --git a/man7/numa.7 b/man7/numa.7
index c6ea67514..1f106bfcd 100644
--- a/man7/numa.7
+++ b/man7/numa.7
@@ -31,7 +31,7 @@ and
 However, applications should normally use the interface provided by
 .IR libnuma ;
 see "Library Support" below.
-.SS /proc/[number]/numa_maps  (since Linux 2.6.14)
+.SS \fI/proc/\fPpid\fI/numa_maps\fP  (since Linux 2.6.14)
 .\" See also Changelog-2.6.14
 This file displays information about a process's
 NUMA memory policy and allocation.
@@ -43,14 +43,14 @@ that memory range and on which nodes the pages have been allocated.
 .I numa_maps
 is a read-only file.
 When
-.I /proc/<pid>/numa_maps
+.IR /proc/ pid /numa_maps
 is read, the kernel will scan the virtual address space of the
 process and report how memory is used.
 One line is displayed for each unique memory range of the process.
 .PP
 The first field of each line shows the starting address of the memory range.
 This field allows a correlation with the contents of the
-.I /proc/<pid>/maps
+.IR /proc/ pid /maps
 file,
 which contains the end address of the range and other information,
 such as the access permissions and sharing.
diff --git a/man7/signal.7 b/man7/signal.7
index ea279d0e2..bd2aa8bff 100644
--- a/man7/signal.7
+++ b/man7/signal.7
@@ -927,7 +927,7 @@ For a discussion of async-signal-safe functions, see
 .BR signal\-safety (7).
 .PP
 The
-.I /proc/[pid]/task/[tid]/status
+.IR /proc/ pid /task/ tid /status
 file contains various fields that show the signals
 that a thread is blocking
 .RI ( SigBlk ),
@@ -943,7 +943,7 @@ as well as the set of pending signals that are directed
 to the process as a whole
 .RI ( ShdPnd ).
 The corresponding fields in
-.I /proc/[pid]/status
+.IR /proc/ pid /status
 show the information for the main thread.
 See
 .BR proc (5)
diff --git a/man7/symlink.7 b/man7/symlink.7
index 4403f6214..caf844ed4 100644
--- a/man7/symlink.7
+++ b/man7/symlink.7
@@ -67,7 +67,9 @@ known as "magic links", which
 can be found in certain pseudofilesystems such as
 .BR proc (5)
 (examples include
-.IR /proc/[pid]/exe " and " /proc/[pid]/fd/* ).
+.IR /proc/ pid /exe
+and
+.IR /proc/ pid /fd/ *).
 Unlike normal symbolic links, magic links are not resolved through
 pathname-expansion, but instead act as direct references to the kernel's own
 representation of a file handle.