capget.2, ptrace.2, vhangup.2, wait.2, ttyslot.3, console.4, proc.5, utmp.5, boot.7: tfix: page xrefs for init

man2/capget.2

@@ -151,7 +151,7 @@ For
 .I pid
 can also be: \-1, meaning perform the change on all threads except the
 caller and
-.BR init (8);
+.BR init (1);
 or a value less than \-1, in which case the change is applied
 to all members of the process group whose ID is \-\fIpid\fP.
 

man2/ptrace.2

@@ -1900,7 +1900,7 @@ cannot send signals to or those running
 set-user-ID/set-group-ID programs, for obvious reasons.
 Alternatively, the process may already be being traced,
 or (on kernels before 2.6.26) be
-.BR init (8)
+.BR init (1)
 (PID 1).
 .TP
 .B ESRCH
@@ -1927,7 +1927,7 @@ or
 .LP
 In Linux kernels before 2.6.26,
 .\" See commit 00cd5c37afd5f431ac186dd131705048c0a11fdb
-.BR init (8),
+.BR init (1),
 the process with PID 1, may not be traced.
 .LP
 The layout of the contents of memory and the USER area are

man2/vhangup.2

@@ -65,4 +65,4 @@ This call is Linux-specific, and should not be used in programs
 intended to be portable.
 .SH SEE ALSO
 .BR capabilities (7),
-.BR init (8)
+.BR init (1)

man2/wait.2

@@ -433,7 +433,7 @@ it will consume a slot in the kernel process table, and if
 this table fills, it will not be possible to create further processes.
 If a parent process terminates, then its "zombie" children (if any)
 are adopted by
-.BR init (8),
+.BR init (1),
 which automatically performs a wait to remove the zombies.
 
 POSIX.1-2001 specifies that if the disposition of

man3/ttyslot.3

@@ -59,7 +59,7 @@ Well, let's first look at some history.
 There used to be a file
 .I /etc/ttys
 in UNIX\ V6, that was read by the
-.BR init (8)
+.BR init (1)
 program to find out what to do with each terminal line.
 Each line consisted of three characters.
 The first character was either \(aq0\(aq or \(aq1\(aq,

man4/console.4

@@ -45,7 +45,7 @@ as soon as they are needed.
 .LP
 Common ways to start a process on a console are:
 (a) tell
-.BR init (8)
+.BR init (1)
 (in
 .BR inittab (5))
 to start a
@@ -95,6 +95,7 @@ All escape sequences can be found in
 .SH SEE ALSO
 .BR chvt (1),
 .BR deallocvt (1),
+.BR init (1),
 .BR loadkeys (1),
 .BR mknod (1),
 .BR openvt (1),
@@ -104,7 +105,6 @@ All escape sequences can be found in
 .BR ttyS (4),
 .BR charsets (7),
 .BR agetty (8),
-.BR init (8),
 .BR mapscrn (8),
 .BR mingetty (8),
 .BR resizecons (8),

man5/proc.5

@@ -3431,7 +3431,7 @@ This file
 controls the handling of Ctrl-Alt-Del from the keyboard.
 When the value in this file is 0, Ctrl-Alt-Del is trapped and
 sent to the
-.BR init (8)
+.BR init (1)
 program to handle a graceful restart.
 When the value is greater than zero, Linux's reaction to a Vulcan
 Nerve Pinch (tm) will be an immediate reboot, without even
@@ -4319,7 +4319,7 @@ of thing that needs to be updated very often.
 .BR arp (8),
 .BR hdparm (8),
 .BR ifconfig (8),
-.BR init (8),
+.BR init (1),
 .BR lsmod (8),
 .BR lspci (8),
 .BR mount (8),

man5/utmp.5

@@ -98,7 +98,7 @@ struct utmp {
                                      messages */
     struct  exit_status ut_exit;  /* Exit status of a process
                                      marked as DEAD_PROCESS; not
-                                     used by Linux init(8) */
+                                     used by Linux init (1 */
     /* The ut_session and ut_tv fields must be the same size when
        compiled 32- and 64-bit.  This allows data files and shared
        memory to be shared between 32- and 64-bit applications. */
@@ -139,18 +139,18 @@ if they are shorter than the size
 of the field.
 .PP
 The first entries ever created result from
-.BR init (8)
+.BR init (1)
 processing
 .BR inittab (5).
 Before an entry is processed, though,
-.BR init (8)
+.BR init (1)
 cleans up utmp by setting \fIut_type\fP to \fBDEAD_PROCESS\fP, clearing
 \fIut_user\fP, \fIut_host\fP, and \fIut_time\fP with null bytes for each
 record which \fIut_type\fP is not \fBDEAD_PROCESS\fP or \fBRUN_LVL\fP
 and where no process with PID \fIut_pid\fP exists.
 If no empty record
 with the needed \fIut_id\fP can be found,
-.BR init (8)
+.BR init (1)
 creates a new one.
 It sets \fIut_id\fP from the inittab, \fIut_pid\fP and \fIut_time\fP to the
 current values, and \fIut_type\fP to \fBINIT_PROCESS\fP.
@@ -175,7 +175,7 @@ records may be located by
 \fIut_line\fP instead of the preferable \fIut_pid\fP.
 .PP
 When
-.BR init (8)
+.BR init (1)
 finds that a process has exited, it locates its utmp
 entry by \fIut_pid\fP, sets \fIut_type\fP to \fBDEAD_PROCESS\fP, and
 clears \fIut_user\fP, \fIut_host\fP and \fIut_time\fP with null bytes.
@@ -212,7 +212,7 @@ logs the old/new system time when
 changes it.
 \fIwtmp\fP is maintained by
 .BR login (1),
-.BR init (8),
+.BR init (1),
 and some versions of
 .BR getty (8)
 (e.g.,
@@ -348,4 +348,4 @@ ut.ut_tv.tv_usec = tv.tv_usec;
 .BR logout (3),
 .BR logwtmp (3),
 .BR updwtmp (3),
-.BR init (8)
+.BR init (1)

man7/boot.7

@@ -7,7 +7,7 @@
 .\" I tried to be as much generic in the description as possible:
 .\" - General boot sequence is applicable to almost any
 .\" OS/Machine (DOS/PC, Linux/PC, Solaris/SPARC, CMS/S390)
-.\" - kernel and init(8) is applicable to almost any UNIX/Linux
+.\" - kernel and init(1) is applicable to almost any UNIX/Linux
 .\" - boot scripts are applicable to SYSV-R4 based UNIX/Linux
 .\"
 .\" Modified 2004-11-03 patch from Martin Schulze <joey@infodrom.org>
@@ -117,7 +117,7 @@ each run-level is associated with a set of services (e.g,
 services start).
 The administrator may change the current
 run-level via
-.BR init (8)
+.BR init (1)
 and query the current run-level via
 .BR runlevel (8).
 
@@ -202,6 +202,6 @@ files, and then use the variable values.
 .SH SEE ALSO
 .BR inittab (5),
 .BR bootparam (7),
-.BR init (8),
+.BR init (1),
 .BR runlevel (8),
 .BR shutdown (8)