On Mon Jul 31, 2000 at 03:20:10PM +0200, Christian Meder wrote:
> Package: boot-floppies
> Version: 2.2.16-2000-07-14;
> Severity: important
>
> The kernel boots ok but when init starts busybox things fall apart:
>
> init started: BusyBox 0.43 (2000.07.06-13.xxx) multi-call binary
> E: /proc does not appear to be mounted (No such file or directory)
> E: /proc does not appear to be mounted (No such file or directory)
> E: /proc does not appear to be mounted (No such file or directory)
> E: /proc does not appear to be mounted (No such file or directory)
> E: /proc does not appear to be mounted (No such file or directory)
To clarify, init _is_ busybox. And it looks like busybox init has done its job
of starting dbootstrap, since the error message you are seeing is coming from
dbootstrap/main.c in the function check_proc(), which is the _very_ first thing
that dbootstrap does. When check_proc() fails to find /proc/version,
dbootstrap exits, and busybox init notices that dbootstrap has exited, and
dutifully restarts it. Ad infinitum.
What is _very_ curious here is that for some reason /proc isn't getting
mounted. Since busybox init is obviously running, it should also have run
/etc/init.d/rcS which has as its first line
mount proc /proc -t proc
So either this script is not being run on your system (perhaps /dev/null is
missing?), or when it is run, it it not managing to mount /proc for some very
wierd reason. Is this repeatable? If so, are you in a position to run some
tests?
-Erik
--
Erik B. Andersen Web: http://www.xmission.com/~andersen/
email: [EMAIL PROTECTED]
--This message was written using 73% post-consumer electrons--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
