I'm building a machine that uses an initrd to create a larger ramdisk for
the root filesystem, load it, then continue booting. (Yes, I know it's
volatile, we'll be getting Coda running soon)
Anyway, I noticed that if you're not very careful with the kernel config
parameters, you end up in a situation where the root device is *not*
/dev/nfs, yet the IP autoconfiguration still fails because it's configured
into the kernel, and there is no nfsaddrs= parameter, only ip=. So, this
is a quick hack (very probably somewhat incorrect) that 'fixes' the check.
I grabbed the check for the nfsroot stuff from fs/nfs/nfsroot.c I believe,
but it looks very iffy for this purpose.
..
Erik,
Your patch may fix a more general problem (or it may not), but we find
that the following works when creating an initrd (for use as the initial
root filesystem in what then becomes a (pseudo-)Coda-based system):
.../netboot/s/mknbi-linux/mknbi \
-i kernel \
-r ${IMAGE}.gz \
-k linux/arch/i386/boot/bzImage \
-a 'ramdisk_size='$NBLOCKS' root=/dev/ramdisk ip=bootp' \
-o ${IMAGE}.nb
Regards,
bruce.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html