[BusyBox] strange problem with BBinit and root=
Joshua J. England
jjengla at sandia.gov
Wed May 8 18:15:03 UTC 2002
> I need to teach busybox how to handle init=foo properly. Right
> now it just runs busybox init regardless, right?
Right. Except seemingly in the root=/dev/ram0 case. I actually prefer
that behavior over busybox grabbing the init= arg: I'm using busybox in
an initrd before passing control to the real (no-offense) init. I like
how busybox calls its own init (/linuxrc) regardless, so that the real
init can use the init= arg.
I've done an additional test and enabled BB_INIT. When I pass
'root=/dev/ram0', busybox calls init as 'init' instead of '/linuxrc',
which explains why it would bail out with usage info when BB_INIT is
disabled.
Why does busybox single out 'root=/dev/ram0' and then ignore
BB_FEATURE_LINUXRC? Dunno....I'll start looking into source.
-Josh
On Wed, 2002-05-08 at 16:06, Erik Andersen wrote:
> On Wed May 08, 2002 at 02:51:30PM -0700, Joshua J. England wrote:
> > For some reason, when I pass 'root=/dev/ram0', it behaves as if the
> > BB_FEATURE_LINUXRC was turned off. This wouldn't be such a big deal,
> > but i need to pass init=/bin/bash (for instance) for testing.
> >
> > Any ideas what could be causing this?
>
> I need to teach busybox how to handle init=foo properly. Right
> now it just runs busybox init regardless, right?
>
> -Erik
>
> --
> Erik B. Andersen http://codepoet-consulting.com/
> --This message was written using 73% post-consumer electrons--
More information about the busybox
mailing list