shock wrote:
>
> Where did you get your init? And are it's /lib dependancies being met?
[snip]
Thanks for the help. I was missing some of /lib. It now boots up from a
new / just fine.
Kyle.
>
> At 04:23 PM 5/22/00 -0500, Kyle Harris is qutoed as saying:
> >Hi folks,
> >
> >I'm trying to trim down a workable image to fit on a DOM. So, I created
> >a small partition on my development drive to create the image. But when
> >I use this new partition for / the kernel panics complaining that it
> >can't find init, which I have verified is in /sbin. Below is lilo.conf.
> >
> ># start of lilo.conf
> >
> >disk=/dev/hda
> > bios=0x80
> > sectors=63
> > heads=128
> > cylinders=787
> >boot=/dev/hda
> >map=/boot/map
> >install=/boot/boot.b
> >prompt
> >timeout=50
> ># this fails
> >image=/boot/bzImage.i586.slim
> > label=embedded
> > root=/dev/hda4
> > vga=791
> > read-only
> >
> ># this works
> >image=/boot/bzImage.i586.slim
> > label=linuxsvga
> > root=/dev/hda1
> > vga=791
> > read-only
> >
> ># end of lilo.conf
> >
> >Shouldn't I be able to simply specify a new root filesystem either when
> >booting or in lilo.conf. Are there other restrictions? (I did run lilo
> >after updating).
> >
> >Thanks, Kyle.
--
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the command "unsubscribe linux-embedded" in the message body.
For more information, see <http://waste.org/mail/linux-embedded>.
