At the lilo/grub prompt > kernelname init=/bin/sh
On Thu, 2003-02-27 at 12:20, Ryurick M. Hristev wrote: > On Tue, 25 Feb 2003, G. M. Bodnar wrote: > > > I was playing around on the weekend with kernels and I decided to try to > > run devfs and use initrd during the boot process. It didn't work, and > > I'm left wondering why. It's not overly critical, but I hate it when I > > can't figure out why it doesn't work. > > > > Has anyone run into similar problems or gotten this combination to work > > on a 2.4.20 kernel? The kernel source isn't vanilla, though. It's a > > debian kernel source package with lowlatency and preempt patches (which > > shouldn't affect things at boot up.) The kernel boots fine, but panics > > when it can't mount the root partition (ext3, hda2) to run /sbin/init. > > Support for ext3 is compiled in, and works fine as long as I'm not using > > initrd. > > > > I've looked through /linuxrc on the initrd image, and nothing strikes me > > as wrong, but this is the first time I've looked at it. > > One option to debug such things is to replace the /sbin/init with something > you know it should load, e.g. a statically linked shell in an obvious > and "no tricks" place. I forgot the kernel boot param but you can find it > easily. Then you can start debugging the problem. > > Cheers, > -- > Ryurick M. Hristev mailto:[EMAIL PROTECTED] > Computer Systems Manager > University of Canterbury, Physics & Astronomy Dept., New Zealand
