From 0d2acb0eadf2d6ae9d60fa3fe9f897e254eaadda Mon Sep 17 00:00:00 2001 From: Eric Andersen Date: Mon, 18 Dec 2000 20:36:02 +0000 Subject: Doc update from Matt Kraai, better describing the init process. --- docs/busybox.pod | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'docs/busybox.pod') 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. : @@ -2293,4 +2294,4 @@ Enrique Zanardi =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 $ -- cgit v1.2.3