Kernel Bootp autoconfig 2.2.x vs 2.0.x

Kenneth James Baker (bakerkj@engin.umich.edu)
Sat, 29 May 1999 15:02:11 -0400 (EDT)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Matthew Wilcox: "Re: Minor bug in lib/string.c"
Previous message: Chris Evans: "Re: [PATCH]: alternative security - special gids"

I'm attempting to upgrade a remote boot machine (etherboot 4.0
bootrom) from 2.0.34 to 2.2.5. I am using dhcpd to provide boot info
including "option root-path". The 2.0.34 kernel sends a bootp request,
gets a bootp answer, and gets a file handle for the directory specified in
the root-path option. With the same dhcpd configuration fails to get the
directory specified in root-path.

The kernel command line options are "auto rw root=/dev/nfs nfsroot=kernel
nfsaddrs=kernel".

Are there any changes that would effect this? And if so do you have any
suggestions how to fix it? Have the kernel options just changed?

Thanks so much for your help,
Ken

-
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.tux.org/lkml/

Next message: Matthew Wilcox: "Re: Minor bug in lib/string.c"
Previous message: Chris Evans: "Re: [PATCH]: alternative security - special gids"