[BusyBox] Init problem (was: typo)

Matt Kraai kraai at alumni.carnegiemellon.edu
Fri Dec 15 00:42:02 UTC 2000


On Thu, Dec 14, 2000 at 02:17:06PM +0100, kissg at sztaki.hu wrote:
> 
> > Do let me know if you see the same problems...
> 
> Dear Erik,
> 
> I was trying different inittab configurations.
> It is almost working now. However I found some difference between
> docs and the reality:
> 
> You wrote on the init man page:
> <id>: 
> 
>    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. ...
> 
> I found that init sends a message to the serial console:
> 	serial console detected ...
> then it does not ignore this inittab entry but executes well:
> 	ttyS1::respawn:/sbin/getty 9600 ttyS1
> 
> However man page wrote this won't work.
> 
> Moreover I don't understand the manual:
> 1. If this field is left blank, it is completely ignored.
> 2. if BusyBox detects that a serial console is in use, then all entries
>    containing non-empty id fields will _not_ be run.
> 
> This means, that in case of serial console NO entry will run.
> Unfortunately this is not true. :-)

An empty id field is equivalent to the name of the console.  If a
serial console is used, only those entries which have an id field
that corresponds to the serial console or to /dev/null are
started.  How about the following patch to the docs:

Index: docs/busybox.pod
===================================================================
RCS file: /var/cvs/busybox/docs/busybox.pod,v
retrieving revision 1.83
diff -u -r1.83 busybox.pod
--- docs/busybox.pod	2000/12/13 17:59:37	1.83
+++ docs/busybox.pod	2000/12/15 00:42:11
@@ -887,10 +887,11 @@
 		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>: 
 

Matt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url : http://lists.busybox.net/pipermail/busybox/attachments/20001214/e0e5ebff/attachment.pgp 


More information about the busybox mailing list