I have been using diskless boots for some time, and selecting different
kernels is very easy, see
ftp://ftp.cs.huji.ac.il/users/danny/freebsd/diskless-boot
danny
>
> :Seems like diskless clients would have to have separate kernels with
> :the "option BOOTP" while any servers must omit this option.
> :
> :How do you keep them separate? or am I missing something fundamental?
> :
> :Thanks.
>
> You can compile pxeboot with the LOADER_TFTP_SUPPORT=YES option.
> Add LOADER_TFTP_SUPPORT=YES to your /etc/make.conf and recompile
> /usr/src/sys/boot (make clean; make obj; make; make install from
> within /usr/src/sys/boot).
>
> If you do this pxeboot will attempt to load the kernel via TFTP
> instead of via NFS. You then put your kernel in /tftpboot right along
> side a copy of pxeboot.
>
> This allows you to netboot a different kernel then the one in the
> server's root directory.
>
> :PS: could you show me your dhcpd.conf so I can see how you're
> : specifying your root filesystem? Mine's currently:
> : option root-path "192.168.255.185:/";
>
> subnet 216.240.41.0 netmask 255.255.255.192 {
> range ...;
>
> server-name "apollo.backplane.com";
> option subnet-mask 255.255.255.192;
> option domain-name-servers 216.240.41.2;
> option domain-name "backplane.com";
> option broadcast-address 216.240.41.63;
> option routers 216.240.41.15;
>
> group {
> filename "pxeboot";
> option root-path "216.240.41.2:/";
>
> host net1 {
> # Alternative server to boot -current
> # option root-path "216.240.41.12:/";
> # next-server 216.240.41.12;
> hardware ethernet ...;
> }
> host net2 {
> hardware ethernet ...;
> }
> ...
> }
> }
>
> -Matt
> Matthew Dillon
> <[EMAIL PROTECTED]>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
