Thank you for your quick answer. :-)
> > Thanx, but the problem is that I boot from a usb floppy drive, and I
> > can't access it after the kernel booted.
>
> That's why I'm suggesting to use initrd.
>
> > Initrd is strange anyway, as normaly it asks for a floppy and to press
> > enter.
>
> Uh ? No, initrd is loaded by the boot loader, not the kernel ...
So I don't need to read the initrd from the floppy with support in the
kernel for the usb floppy drive because the boot loader loads it? Hmm,
then I have to read up on initrd. :-) Will try that, thnx. :-)
> If your boot loader has problems with the BIOS, maube you should try
> another one then, e.g. LILO almost certainly works for this.
Yeah, lilo boots the kernel fine.
> > If I make the nic work, then nfsroot should work without even knowing
> > the nick is a pcmcia, shouldn't it?
>
> Okay, second possibility, which may or may not work: again, use initrd,
> but this time, exit from initrd after bringing up the NIC. Now you're
> using the old change root mechanism, which executes the "standard" root
> mount code for you, see also
>
> ftp://icaftp.epfl.ch/pub/people/almesber/booting/bootinglinux-current.ps.gz
>
> AFAIK, you can't set up the NIC without user-space PCMCIA support, so
> you still have to use initrd for this. Iff you figure out a way to do
> this, you could use a simple initrd that just sleeps for a few seconds,
> or loops until it finds the devices it wants.
Oke, will try that if I can make initrd work.
> For constructing small initrds, see also
> ftp://icaftp.epfl.ch/pub/people/almesber/misc/newlib-linux/
> newlib-linux-21.tar.gz
> (but in your case, just statically linking against glibc is probably
> okay, even if you waste some space this way.)
Thanks a lot!!
Ookhoi
|