> ebiederm@xmission.com said:
> > There wasn't even DHCP support before so yes you did. As you can't
> > get the nfs mount point from bootp.
>
> Wasn't there a default? The Indy behind me seems to try to mount
> /tftpboot/172.16.18.195, so I put a filesystem there just to make it happy.
>
> It's a 2.4.3 kernel.
Duh. I forgot about the default path.
> > Well I think in the CONFIG_BLK_DEV=n case it might wind up being a
> > ramfs or tmpfs image. Something like a simplified version of tar.
>
> Well, if it stops working and stays broken, I suppose I'll just have to
> hack up a built-in command line option. ISTR ARM already has such an option.
>
> I'd rather it didn't break, though.
The clean way to handle it, and I'll take a look it to have
root=/dev/nfs (and the rdev equivalent) to set ip=on if it isn't
already. The current 2.4.4 behavior of root=/dev/hda3 doing ip
autoconfig when the code is compiled into the kernel is just bad.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/