[BusyBox] strange problem with BBinit and root=

[Erik Andersen]

On Wed May 08, 2002 at 05:11:50PM -0700, Joshua J. England wrote:
> > 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

none taken.  :)

> how busybox calls its own init (/linuxrc) regardless, so that the real
> init can use the init= arg.

What I have done in such situations is disable busybox's BB_INIT
and BB_FEATURE_LINUXRC, and then used a shell script for /linuxrc

> 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.

If you run with root=/dev/ram0, the kernel doesn't ever execute
/linuxrc unless you explicitly add "root=/linuxrc"

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--