aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorEric Andersen <andersen@codepoet.org>2000-12-18 20:36:02 +0000
committerEric Andersen <andersen@codepoet.org>2000-12-18 20:36:02 +0000
commit0d2acb0eadf2d6ae9d60fa3fe9f897e254eaadda (patch)
tree60d041f1c0f5b660f456a55782c97cbe2bd628e3 /docs
parent86349776d0006440c0fefab7dc05a38329bcc466 (diff)
downloadbusybox-0d2acb0eadf2d6ae9d60fa3fe9f897e254eaadda.tar.gz
Doc update from Matt Kraai, better describing the init process.
Diffstat (limited to 'docs')
-rw-r--r--docs/busybox.pod11
-rw-r--r--docs/busybox.sgml25
2 files changed, 18 insertions, 18 deletions
diff --git a/docs/busybox.pod b/docs/busybox.pod
index 4dd3a3a98..8f6e1381c 100644
--- a/docs/busybox.pod
+++ b/docs/busybox.pod
@@ -887,10 +887,11 @@ If you choose to use an /etc/inittab file, the inittab entry format is as follow
the specified process to run on. The contents of this field are
appended to "/dev/" and used as-is. There is no need for this field to
be unique, although if it isn't you may have strange results. If this
- field is left blank, it is completely ignored. Also note that if
- BusyBox detects that a serial console is in use, then all entries
- containing non-empty id fields will _not_ be run. BusyBox init does
- nothing with utmp. We don't need no stinkin' utmp.
+ field is left blank, the controlling tty is set to the console. Also
+ note that if BusyBox detects that a serial console is in use, then only
+ entries whose controlling tty is either the serial console or /dev/null
+ will be run. BusyBox init does nothing with utmp. We don't need no
+ stinkin' utmp.
<runlevels>:
@@ -2293,4 +2294,4 @@ Enrique Zanardi <ezanardi@ull.es>
=cut
-# $Id: busybox.pod,v 1.83 2000/12/13 17:59:37 andersen Exp $
+# $Id: busybox.pod,v 1.84 2000/12/18 20:36:02 andersen Exp $
diff --git a/docs/busybox.sgml b/docs/busybox.sgml
index fda66a619..c64dab80f 100644
--- a/docs/busybox.sgml
+++ b/docs/busybox.sgml
@@ -1512,19 +1512,18 @@
<sect2>
<title>id</title>
<para>
- WARNING: This field has a non-traditional
- meaning for BusyBox init! The id field is used
- by BusyBox init to specify the controlling tty
- for the specified process to run on. The
- contents of this field are appended to "/dev/"
- and used as-is. There is no need for this field
- to be unique, although if it isn't you may have
- strange results. If this field is left blank,
- it is completely ignored. Also note that if
- BusyBox detects that a serial console is in use,
- then all entries containing non-empty id fields
- will _not_ be run. BusyBox init does nothing
- with utmp. We don't need no stinkin' utmp.
+
+ WARNING: This field has a non-traditional meaning for BusyBox init!
+ The id field is used by BusyBox init to specify the controlling tty
+ for the specified process to run on. The contents of this field
+ are appended to "/dev/" and used as-is. There is no need for this
+ field to be unique, although if it isn't you may have strange
+ results. If this field is left blank, the controlling tty is set
+ to the console. Also note that if BusyBox detects that a serial
+ console is in use, then only entries whose controlling tty is
+ either the serial console or /dev/null will be run. BusyBox init
+ does nothing with utmp. We don't need no stinkin' utmp.
+
</para>
</sect2>