On Tue, Feb 20, 2001 at 11:02:10PM +0000, Russell King wrote:
> Ben LaHaise writes:
> > Yeah, that's the problem I was trying to work around, mostly because the
> > docs on dhcpd are sufficiently vague and obscure. Personally, I don't
> > actually need tftp support, so I've just configured the system to now
> > point at the NFS server. For anyone who cares, the last patch was wrong,
> > this one is right.
>
> This is the dhcp entry for a host that I use to tftp a kernel from a
> different machine to that running dhcpd:
>
> host tasslehoff
> {
> hardware ethernet 00:10:57:00:03:EC;
> fixed-address tasslehoff;
> next-server raistlin;
> filename "/usr/src/k/tasslehoff";
> }
>
> The booting host is called "tasslehoff". The tftp server host is called
> "raistlin", and the dhcp server is called "flint".
>
> According to Tom, this should also cause Linux to nfs mount from the
> "next-server" address, and it is fair that this is not documented by
> the dhcp man pages since it appears to be a Linux Kernel quirk.
Well, assuming next-server gets translated into TFTP server by the
dhcp-doing-bootp bit, yes. I'm using that right now to bootp on
one box and NFS off another.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
