In message <200306101917.h5AJHJY4001774@fearless-vampire-killer.waterside.net>,
I wrote:

-> In message <bc5348$7rk$1@main.gmane.org>, you write: 
-> 
-> -> Victor Sudakov <sudakov@sibptus.tomsk.ru> wrote:
-> -> 
-> -> >>        subclass "allocation-class-2" 1:08:00:2b:a1:11:31 {
-> -> >>          option root-path "samsara:/var/diskless/alphapc";
-> -> >>          filename "/tftpboot/netbsd.alphapc-diskless";
-> -> >>        }
-> -> > 
-> -> > Yes, option root-path is indeed option 17.
-> -> > Unfortunately ofwboot.net does not parse the option string as you expec
-> t.
-> -> 
-> -> My reading of sys/lib/libsa/bootp.c is that 'rootip' is inite from
-> -> option 16 (swap-server, doh!) if supplied.  root path (options 17)
-> -> should be just the pathname.
-> 
-> ISC's dhcpd has a 'next-server', here's what all my netboot-capable
-> entries look like:
-> 
-> host blah {
->   option host-name "blah";
->   hardware ethernet xx:xx:xx:xx:xx:xx;
->   fixed-address 1.2.3.4;
->   server-name "root-server:/roots/myroot";
->   next-server root-server;
-> }
-> 
-> I'm not sure if I really need the "root-server:" in the server-name field, 
-> but it works, so I haven't mucked with it.  Most of my netbooting boxes
-> are sgimips machines, but I'm pretty sure the same type of syntax has 
-> worked for my Ultra5 and Shark as well.

Ah, my bad.  I think "next-server" is the tftp server it gets the kernel
from and the server in the "server-name" field is the NFS host, but I do
note that in all the cases in my dhcpd.conf, the two are the same (either
one of my generic servers which contains "production" stuff, or a dev box
which has faster-moving stuff...).

--rafal

----
Rafal Boni                                                     rafal@attbi.com
  We are all worms.  But I do believe I am a glowworm.  -- Winston Churchill