Thanks,
This works for me.
One small detail, on my DHCP-server, the option
next-server "192.168.1.8" didn't work, I had to use
next-server 192.168.1.8
Bert.
On Thursday 29 November 2001 19:39, Chad Walstrom wrote:
> Ah, yes. I floundered on this for a while. You can force Linux to look
> for the correct NFS root server at the lilo prompt with the kernel
> parameter "nfsroot". This is not very practical, since you could easily
> want different clients to go to different servers (as in the BOOTP
> protocol, which DHCP extends).
>
> The answer to your dilemma is in the dhcpd.conf(5) manpage. What you're
> looking for is the option called "next-server", which is quite
> appropriately named. It is the "next-server" you want the dhcp client
> to look at for the root directory.
>
> Here's the section from dhcpd.conf(5) that explains the difference
> between "server-name" and "next-server":
>
> The server-name statement
>
> server-name "name";
>
> The server-name statement can be used to inform the client
> of the name of the server from which it is booting. Name
> should be the name that will be provided to the client.
>
> Note: the client is "booting" -- getting its IP address. Next it will
> look for it's root/boot file.
>
> The next-server statement
>
> next-server server-name;
>
> The next-server statement is used to specify the host
> address of the server from which the initial boot file
> (specified in the filename statement) is to be loaded.
> Server-name should be a numeric IP address or a domain
> name. If no next-server parameter applies to a given
> client, the DHCP server's IP address is used.
>
> So this should work:
>
> # FAI Clients
> group {
> server-name "dhcp.mydomain.tld";
> next-server "nfsroot.mydomain.tld";
> file-name "/usr/lib/fai/nfsroot"
> use-host-decl-names on;
>
> # other FAI options...
>
> host myhost {
> hardware address 00:00:00:00:00:00;
> fixed-address myhost.mydomain.tld;
> }
> #...
> }
>
> I hope this helps.
