[BusyBox] Weird Console behavior

[Jim Gleason]

In the init.c file at line 718, there is comments (and code) that
disallows all entries not refering to the console or null devices if a
serial console has been specified.  The following code snippet seems
suspect to me.

         /* If BusyBox detects that a serial console is in use,
          * then entries not refering to the console or null devices
     will _not_ be run.
          * The exception to this rule is the null device.
          */
         if (secondConsole == NULL && strcmp(cons, console)
             && strcmp(cons, "/dev/null"))
             return;

It appears to me that this code assumes the serial console WILL be
specified first. (?)

I know that this is primarily associated with the starting up of other
processes (it is in new_initAction()), but it just doesn't feel right to
me - however, I don't mess with this code very much.

Jim Gleason

"Richard A. Smith" wrote:

> On Thu, 28 Jun 2001 01:29:08 -0600, Erik Andersen wrote:
>
> >On Wed Jun 27, 2001 at 05:04:28PM -0500, Richard A. Smith wrote:
> >>
> >> I remembered that there was some sort of issue with 2.4.x and the
> >> console serial port. Is this some sort of manifestation of that and
> >> completly unrelated to BB or something else?
> >
> >Well, there was a problem some time ago, but it was the result
> >of a revealed bug in bb init, which was corrected quite a while
> >back.
>
> So if its not that bug then anyone have any ideas?  Almost seems like
> a kernel issue to me.
>
> --
> Richard A. Smith                         Bitworks, Inc.
> rsmith at bitworks.com               501.846.5777
> Sr. Design Engineer        http://www.bitworks.com
>
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/mailman/listinfo/busybox
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.busybox.net/pipermail/busybox/attachments/20010628/3c5737c6/attachment-0001.htm