1
#! /bin/sh /usr/share/dpatch/dpatch-run
2
## 10_doc_manuals.dpatch by the Debian ALSA psychos
4
## All lines beginning with `## DP:' are a description of the patch.
5
## DP: Misc patches to manual pages
8
diff -urNad --exclude=CVS --exclude=.svn ./man/bootlogd.8 /tmp/dpep-work.VkakEo/trunk/man/bootlogd.8
9
--- ./man/bootlogd.8 2005-12-02 17:22:58.000000000 +0100
10
+++ /tmp/dpep-work.VkakEo/trunk/man/bootlogd.8 2006-02-15 17:10:18.000000000 +0100
13
\fBBootlogd\fP runs in the background and copies all strings sent to the
14
\fI/dev/console\fP device to a logfile. If the logfile is not accessible,
15
-the messages will be buffered in-memory until it is.
16
+the messages will be kept in memory until it is.
19
Do not fork and run in the background.
21
\fIlogfile~\fP unless \fIlogfile~\fP already exists.
24
-.IP \fB\-l logfile\fP
25
+.IP "\fB\-l\fP \fIlogfile\fP"
26
Log to this logfile. The default is \fI/var/log/boot\fP.
27
-.IP \fB\-p pidfile\fP
28
+.IP "\fB\-p\fP \fIpidfile\fP"
29
Put process-id in this file. The default is no pidfile.
31
-Bootlogd works by redirecting the console output from the console
32
-device. It copies that output to the real console device and a
33
-logfile. There is no standard way to find out the real console device
34
-if you have a new-style \fI/dev/console\fP device (major 5, minor 1).
35
-\fBBootlogd\fP tries to parse the kernel command line, looking for
36
-console= lines and deducts the real console device from that. If that
37
-syntax is ever changed by the kernel, or a console-type is used
38
-bootlogd does not know about, bootlogd will not work.
39
+Bootlogd works by redirecting the console output from the console device.
40
+(Consequently \fBbootlogd\fP requires PTY support in the kernel configuration.)
41
+It copies that output to the real console device and to a log file.
42
+There is no standard way of ascertaining the real console device
43
+if you have a new-style \fI/dev/console\fP device (major 5, minor 1)
44
+so \fBbootlogd\fP parses the kernel command line looking for
45
+\fBconsole=...\fP lines and deduces the real console device from that.
46
+If that syntax is ever changed by the kernel, or a console type is used that
47
+\fBbootlogd\fP does not know about then \fBbootlogd\fP will not work.
50
Miquel van Smoorenburg, miquels@cistron.nl
52
diff -urNad --exclude=CVS --exclude=.svn ./man/halt.8 /tmp/dpep-work.VkakEo/trunk/man/halt.8
53
--- ./man/halt.8 2005-12-02 17:22:58.000000000 +0100
54
+++ /tmp/dpep-work.VkakEo/trunk/man/halt.8 2006-02-15 17:10:18.000000000 +0100
57
\fBHalt\fP notes that the system is being brought down in the file
58
\fI/var/log/wtmp\fP, and then either tells the kernel to halt, reboot or
60
+power-off the system.
62
If \fBhalt\fP or \fBreboot\fP is called when the system is
63
\fInot\fP in runlevel \fB0\fP or \fB6\fP, in other words when it's running
66
Shut down all network interfaces just before halt or reboot.
68
-Put all harddrives on the system in standby mode just before halt or poweroff.
69
+Put all hard drives on the system in stand-by mode just before halt or power-off.
71
-When halting the system, do a poweroff. This is the default when halt is
72
+When halting the system, switch off the power. This is the default when halt is
73
called as \fBpoweroff\fP.
77
correctly) \fBshutdown\fP will be called, which might not be what you want.
78
Use the \fB-f\fP flag if you want to do a hard \fBhalt\fP or \fBreboot\fP.
80
-The \fB-h\fP flag puts all harddisks in standby mode just before halt
81
-or poweroff. Right now this is only implemented for IDE drives. A side
82
-effect of putting the drive in standby mode is that the write cache
83
+The \fB-h\fP flag puts all hard disks in standby mode just before halt
84
+or power-off. Right now this is only implemented for IDE drives. A side
85
+effect of putting the drive in stand-by mode is that the write cache
86
on the disk is flushed. This is important for IDE drives, since the
87
-kernel doesn't flush the write-cache itself before poweroff.
88
+kernel doesn't flush the write cache itself before power-off.
90
The \fBhalt\fP program uses /proc/ide/hd* to find all IDE disk devices,
91
-which means that /proc needs to be mounted when \fBhalt\fP or
92
+which means that \fI/proc\fP needs to be mounted when \fBhalt\fP or
93
\fBpoweroff\fP is called or the \fB-h\fP switch will do nothing.
96
diff -urNad --exclude=CVS --exclude=.svn ./man/init.8 /tmp/dpep-work.VkakEo/trunk/man/init.8
97
--- ./man/init.8 2005-12-02 17:22:58.000000000 +0100
98
+++ /tmp/dpep-work.VkakEo/trunk/man/init.8 2006-02-15 17:10:18.000000000 +0100
100
only a selected group of processes to exist. The processes spawned by
101
\fBinit\fP for each of these runlevels are defined in the
102
\fB/etc/inittab\fP file. \fBInit\fP can be in one of eight runlevels:
103
-\fB0\(en6\fP and \fBS\fP or \fBs\fP. The runlevel is
104
+\fB0\(en6\fP and \fBS\fP (a.k.a. \fBs\fP). The runlevel is
105
changed by having a privileged user run \fBtelinit\fP, which sends
106
appropriate signals to \fBinit\fP, telling it which runlevel to change
109
-Runlevels \fB0\fP, \fB1\fP, and \fB6\fP are reserved. Runlevel 0 is used to
110
-halt the system, runlevel 6 is used to reboot the system, and runlevel
111
-1 is used to get the system down into single user mode. Runlevel \fBS\fP
112
-is not really meant to be used directly, but more for the scripts that are
113
-executed when entering runlevel 1. For more information on this,
114
+Runlevels \fBS\fP, \fB0\fP, \fB1\fP, and \fB6\fP are reserved.
115
+Runlevel S is used to initialize the system on boot.
116
+When starting runlevel S (on boot)
117
+or runlevel 1 (switching from a multi-user runlevel)
118
+the system is entering ``single-user mode'', after which the
119
+current runlevel is S.
120
+Runlevel 0 is used to halt the system;
121
+runlevel 6 is used to reboot the system.
123
+After booting through S the system automatically enters one of
124
+the multi-user runlevels 2 through 5, unless there was some
125
+problem that needs to be fixed by the administrator in
127
+Normally after entering single-user mode
128
+the administrator performs maintenance and then reboots the system.
130
+For more information,
131
see the manpages for \fBshutdown\fP(8) and \fBinittab\fP(5).
133
Runlevels 7-9 are also valid, though not really documented. This is
134
because "traditional" Unix variants don't use them.
135
-In case you're curious, runlevels \fIS\fP and \fIs\fP are in fact the same.
137
+Runlevels \fIS\fP and \fIs\fP are the same.
138
Internally they are aliases for the same runlevel.
142
entry (or no \fB/etc/inittab\fP at all), a runlevel must be
143
entered at the system console.
145
-Runlevel \fBS\fP or \fBs\fP bring the system to single user mode
146
-and do not require an \fB/etc/inittab\fP file. In single user mode,
147
-\fB/sbin/sulogin\fP is invoked on \fB/dev/console\fP.
148
+Runlevel \fBS\fP or \fBs\fP initialize the system
149
+and do not require an \fB/etc/inittab\fP file.
151
+In single user mode, \fB/sbin/sulogin\fP is invoked on \fB/dev/console\fP.
153
When entering single user mode, \fBinit\fP initializes the consoles
154
\fBstty\fP settings to sane values. Clocal mode is set. Hardware
156
for them. If the processes change their group, \fBinit\fP can't
157
kill them and you may end up with two processes reading from one
160
+On a Debian system, entering runlevel 1 causes all processes
161
+to be killed except for kernel threads and the script that does
162
+the killing and other processes in its session.
163
+As a consequence of this, it isn't safe to return from runlevel 1
164
+to a multi-user runlevel: daemons that were started in runlevel S
165
+and are needed for normal operation are no longer running.
166
+The system should be rebooted.
170
diff -urNad --exclude=CVS --exclude=.svn ./man/initscript.5 /tmp/dpep-work.VkakEo/trunk/man/initscript.5
171
--- ./man/initscript.5 2005-12-02 17:22:58.000000000 +0100
172
+++ /tmp/dpep-work.VkakEo/trunk/man/initscript.5 2006-02-15 17:10:18.000000000 +0100
174
PATH=/bin:/sbin:/usr/bin:/usr/sbin
177
- # Increase the hard filedescriptor limit for all processes
178
- # to 8192. The soft limit is still 1024, but any unpriviliged
179
- # process can increase it's soft limit up to the hardlimit
180
+ # Increase the hard file descriptor limit for all processes
181
+ # to 8192. The soft limit is still 1024, but any unprivileged
182
+ # process can increase its soft limit up to the hard limit
183
# with "ulimit -Sn xxx" (needs a 2.2.13 or later Linux kernel).
186
diff -urNad --exclude=CVS --exclude=.svn ./man/inittab.5 /tmp/dpep-work.VkakEo/trunk/man/inittab.5
187
--- ./man/inittab.5 2005-12-02 17:22:58.000000000 +0100
188
+++ /tmp/dpep-work.VkakEo/trunk/man/inittab.5 2006-02-15 17:10:18.000000000 +0100
192
.IP \fBpowerokwait\fP
193
-This process will be executed as soon as \fBinit\fP is informormed that the
194
+This process will be executed as soon as \fBinit\fP is informed that the
195
power has been restored.
198
diff -urNad --exclude=CVS --exclude=.svn ./man/last.1 /tmp/dpep-work.VkakEo/trunk/man/last.1
199
--- ./man/last.1 2005-12-02 17:22:58.000000000 +0100
200
+++ /tmp/dpep-work.VkakEo/trunk/man/last.1 2006-02-15 17:10:18.000000000 +0100
205
+.IP "\fB\-f\fP \fIfile\fP"
206
+Tells \fBlast\fP to use a specific file instead of \fB/var/log/wtmp\fP.
207
.IP \fB\-\fP\fInum\fP
208
This is a count telling \fBlast\fP how many lines to show.
209
.IP "\fB\-n\fP \fInum\fP"
210
diff -urNad --exclude=CVS --exclude=.svn ./man/mesg.1 /tmp/dpep-work.VkakEo/trunk/man/mesg.1
211
--- ./man/mesg.1 2005-12-02 17:22:58.000000000 +0100
212
+++ /tmp/dpep-work.VkakEo/trunk/man/mesg.1 2006-02-15 17:10:18.000000000 +0100
215
If no option is given, \fBmesg\fP prints out the current access state of your
221
\fBMesg\fP assumes that its standard input is connected to your
222
terminal. That also means that if you are logged in multiple times,
223
you can get/set the mesg status of other sessions by using redirection.
224
diff -urNad --exclude=CVS --exclude=.svn ./man/pidof.8 /tmp/dpep-work.VkakEo/trunk/man/pidof.8
225
--- ./man/pidof.8 2005-12-02 17:22:58.000000000 +0100
226
+++ /tmp/dpep-work.VkakEo/trunk/man/pidof.8 2006-02-15 17:12:34.000000000 +0100
228
Tells \fIpidof\fP to omit processes with that process id. The special
229
pid \fB%PPID\fP can be used to name the parent process of the \fIpidof\fP
230
program, in other words the calling shell or shell script.
234
+At least one program was found with the requested name.
237
+No program was found with the requested name.
239
-\fIpidof\fP is simply a (symbolic) link to the \fIkillall5\fP program,
240
-which should also be located in \fP/sbin\fP.
241
+\fIpidof\fP is actually the same program as \fIkillall5\fP;
242
+the program behaves according to the name under which it is called.
244
When \fIpidof\fP is invoked with a full pathname to the program it
245
should find the pid of, it is reasonably safe. Otherwise it is possible
246
diff -urNad --exclude=CVS --exclude=.svn ./man/shutdown.8 /tmp/dpep-work.VkakEo/trunk/man/shutdown.8
247
--- ./man/shutdown.8 2005-12-02 17:22:58.000000000 +0100
248
+++ /tmp/dpep-work.VkakEo/trunk/man/shutdown.8 2006-02-15 17:10:18.000000000 +0100
253
-Halt or poweroff after shutdown.
254
+Halt or power off after shutdown.
258
@@ -100,10 +100,11 @@
259
Second, it can be in the format \fB+\fP\fIm\fP, in which \fIm\fP is the
260
number of minutes to wait. The word \fBnow\fP is an alias for \fB+0\fP.
262
-If shutdown is called with a delay, it creates the advisory file
263
+If shutdown is called with a delay, it will create the advisory file
265
which causes programs such as \fIlogin(1)\fP to not allow new user
266
-logins. Shutdown removes this file if it is stopped before it
267
+logins. This file is created five minutes before the shutdown sequence
268
+starts. Shutdown removes this file if it is stopped before it
269
can signal init (i.e. it is cancelled or something goes wrong).
270
It also removes it before calling init to change the runlevel.
272
@@ -117,13 +118,13 @@
273
file \fI/forcefsck\fP which can be tested by the system when it comes
274
up again. The boot rc file can test if this file is present, and decide
275
to run \fBfsck\fP(1) with a special `force' flag so that even properly
276
-unmounted filesystems get checked.
277
+unmounted file systems get checked.
278
After that, the boot process should remove \fI/forcefsck\fP.
280
The \fB-n\fP flag causes \fBshutdown\fP not to call \fBinit\fP,
281
but to kill all running processes itself.
282
\fBshutdown\fP will then turn off quota, accounting, and swapping
283
-and unmount all filesystems.
284
+and unmount all file systems.
288
diff -urNad --exclude=CVS --exclude=.svn ./man/sulogin.8 /tmp/dpep-work.VkakEo/trunk/man/sulogin.8
289
--- ./man/sulogin.8 2005-12-02 17:22:58.000000000 +0100
290
+++ /tmp/dpep-work.VkakEo/trunk/man/sulogin.8 2006-02-15 17:10:18.000000000 +0100
292
-.TH SULOGIN 8 "04 Nov 2003" "" "Linux System Administrator's Manual"
293
+.TH SULOGIN 8 "17 Jan 2006" "" "Linux System Administrator's Manual"
295
-sulogin -- Single-user login
296
+sulogin \- Single-user login
301
-.RB [ " -t timeout " ]
302
-.RB [ " tty-device " ]
305
+[ \fB\-t\fP \fISECONDS\fP ]
309
-is invoked by \fBinit(8)\fP when the system goes into single user mode
310
-(this is done through an entry in \fIinittab(5)\fP). \fBInit\fP also
311
-tries to execute \fIsulogin\fP when it is passed the \fB-b\fP flag
312
-from the bootmonitor (eg, LILO).
313
+is invoked by \fBinit(8)\fP when the system goes into single user mode.
314
+(This is done through an entry in \fIinittab(5)\fP.)
316
+tries to execute \fIsulogin\fP when
317
+the boot loader (e.g., \fBgrub\fP(8))
318
+passes it the \fB\-b\fP option.
322
Give root password for system maintenance
324
-(or type Control-D for normal startup):
325
+(or type Control\-D for normal startup):
327
\fIsulogin\fP will be connected to the current terminal, or to the
328
optional device that can be specified on the command line
329
(typically \fB/dev/console\fP).
331
-If the \fB-p\fP flag was set, the single-user shell will be invoked
332
-with a \fIdash\fP as the first character in \fIargv[0]\fP. That will
333
-cause most shells to behave as a login shell. The default is \fInot\fP
334
-to do this, so that the shell will \fInot\fP read \fB/etc/profile\fP
335
+If the \fB\-t\fP option is used then the program only waits
336
+the given number of seconds for user input.
338
+If the \fB\-p\fP option is used then the single-user shell is invoked
339
+with a \fIdash\fP as the first character in \fIargv[0]\fP.
340
+This causes the shell process to behave as a login shell.
341
+The default is \fInot\fP to do this,
342
+so that the shell will \fInot\fP read \fB/etc/profile\fP
343
or \fB$HOME/.profile\fP at startup.
345
-After the user exits the single-user shell, or presses control-d at the
346
-prompt, the system will (continue to) boot to the default runlevel.
347
+After the user exits the single-user shell,
348
+or presses control\-D at the prompt,
349
+the system will (continue to) boot to the default runlevel.
350
.SH ENVIRONMENT VARIABLES
351
\fIsulogin\fP looks for the environment variable \fBSUSHELL\fP or
352
\fBsushell\fP to determine what shell to start. If the environment variable
353
is not set, it will try to execute root's shell from /etc/passwd. If that
354
fails it will fall back to \fB/bin/sh\fP.
356
-This is very valuable together with the \fB-b\fP flag to init. To boot
357
+This is very valuable together with the \fB\-b\fP option to init. To boot
358
the system into single user mode, with the root file system mounted read/write,
359
-using a special "failsafe" shell that is statically linked (this example
360
+using a special "fail safe" shell that is statically linked (this example
361
is valid for the LILO bootprompt)
363
-boot: linux -b rw sushell=/sbin/sash
364
+boot: linux \-b rw sushell=/sbin/sash
366
\fIsulogin\fP checks the root password using the standard method (getpwnam)
368
-Then, if the \fB-e\fP option was specified,
369
+Then, if the \fB\-e\fP option was specified,
370
\fIsulogin\fP examines these files directly to find the root password:
374
/etc/shadow (if present)
376
-If they are damaged or non-existant, sulogin will start a root shell
377
-without asking for a password. Only use the \fB-e\fP option if you
378
+If they are damaged or nonexistent, sulogin will start a root shell
379
+without asking for a password. Only use the \fB\-e\fP option if you
380
are sure the console is physically protected against unauthorized access.
382
Miquel van Smoorenburg <miquels@cistron.nl>
added
removed
debian/patches/10_doc_manuals.dpatch
