BusyBox/inittab weirdness

Rob Landley rob at landley.net
Mon Dec 5 19:57:37 UTC 2005

On Monday 05 December 2005 11:41, Rory Vieira wrote:
> Hi,
> I stumbled on this without even knowing it...
> I compiled BusyBox with almost all options enabled (including init).
> It also includes 'standalone shell'...
> Now my inittab start off like:
> -------------------------------
> ::sysinit:echo "Starting up Linux `uname -r`..."
> null::sysinit:/bin/mount -n -t proc proc /proc
> null::sysinit:/bin/mount -n -o remount,rw /dev/root /
> null::sysinit:/bin/busybox --install -s

Meaning the console they're attached to is /dev/null.

> The first line shows 'echo' and 'uname' without a path specification.

Did you give an absolute path to either one?

> The second line though is '/bin/mount'!

_You_ gave an absolute path to mount.

> Obviously I needed to make the 'mount', 'sh', and 'init' links beforehand.
> Why do I need to do this for mount etc, but not with echo or uname?

Why did you specify an absolute path for them, but not for echo and uname?

> I can understand the echo (builtin), but not the uname.

Look at your code.

> If I change the second line to just 'mount...' it claims it can find mount
> at all...

I have no idea what your $PATH is set to.

Steve Ballmer: Innovation!  Inigo Montoya: You keep using that word.
I do not think it means what you think it means.

More information about the busybox mailing list