Re: Problems booting 2.1.15

Richard B. Johnson (
Mon, 16 Dec 1996 13:30:05 -0500 (EST)

On Mon, 16 Dec 1996, Ian Bonnycastle wrote:

> "Peter T. Breuer" writes:
> >/etc/
> >
> >("locate cache | grep ld")
> Thanks. I checked my cache, and its completely up to date. In fact, it
> updates itself everytime I boot. So 2.1.15 isn't halting because of it.
> Ian
I strongly recommend that, when using development kernels, you link
init statically and put copies in all the directories checked, i.e.,
/sbin/init /bin/init /usr/bin/init....

/usr/src/sysvinit-2.62[68]# gcc -o init -static init.c
/usr/src/sysvinit-2.62[69]# mv /sbin/init /sbin/init.O
/usr/src/sysvinit-2.62[70]# mv /bin/init /bin/init.O
/usr/src/sysvinit-2.62[71]# mv /usr/bin/init /usr/bin/init.O
/usr/src/sysvinit-2.62[72]# cp init /sbin
/usr/src/sysvinit-2.62[73]# cp init /bin
/usr/src/sysvinit-2.62[74]# cp init /usr/bin
^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^
My prompt commands

If you can get to the root mount point from another kernel, you can
modify /etc/rc.d/rc.S to:


... on its first line.

This will get you up to a very dumb mode with a shell. Just exit the
shell to continue.

You can then execute each of the startup commands, one at a time, to
see what hangs the system. If you get the shell upon startup, you know
that init started and forked its first shell to execute the commands
in /etc/rc.d/rc.

Init is not a very complicated program, but if it doesn't run, you are
screwed big-time trying to find out why.

Dick Johnson
Richard B. Johnson
Project Engineer
Analogic Corporation
Voice : (508) 977-3000 ext. 3754
Fax : (508) 532-6097
Modem : (508) 977-6870
Ftp :
Email :,
Penguin : Linux version 2.1.15 on an i586 machine.
Warning : It's hard to remain at the trailing edge of technology.