emo/busybox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Doc update from Matt Kraai, better describing the init process.

Browse Source
This commit is contained in:
Eric Andersen 2000-12-18 20:36:02 +00:00
parent 86349776d0
commit 0d2acb0ead
2 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/busybox.pod
View File

@ -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 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 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 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 field is left blank, the controlling tty is set to the console. Also
BusyBox detects that a serial console is in use, then all entries note that if BusyBox detects that a serial console is in use, then only
containing non-empty id fields will _not_ be run. BusyBox init does entries whose controlling tty is either the serial console or /dev/null
nothing with utmp. We don't need no stinkin' utmp. will be run. BusyBox init does nothing with utmp. We don't need no
stinkin' utmp.
<runlevels>: <runlevels>:
@ -2293,4 +2294,4 @@ Enrique Zanardi <ezanardi@ull.es>
=cut =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 $

25
docs/busybox.sgml
View File

@ -1512,19 +1512,18 @@
<sect2> <sect2>
<title>id</title> <title>id</title>
<para> <para>
WARNING: This field has a non-traditional
meaning for BusyBox init! The id field is used WARNING: This field has a non-traditional meaning for BusyBox init!
by BusyBox init to specify the controlling tty The id field is used by BusyBox init to specify the controlling tty
for the specified process to run on. The for the specified process to run on. The contents of this field
contents of this field are appended to "/dev/" are appended to "/dev/" and used as-is. There is no need for this
and used as-is. There is no need for this field field to be unique, although if it isn't you may have strange
to be unique, although if it isn't you may have results. If this field is left blank, the controlling tty is set
strange results. If this field is left blank, to the console. Also note that if BusyBox detects that a serial
it is completely ignored. Also note that if console is in use, then only entries whose controlling tty is
BusyBox detects that a serial console is in use, either the serial console or /dev/null will be run. BusyBox init
then all entries containing non-empty id fields does nothing with utmp. We don't need no stinkin' utmp.
will _not_ be run. BusyBox init does nothing
with utmp. We don't need no stinkin' utmp.
</para> </para>
</sect2> </sect2>