From owner-freebsd-current Sat Feb 22 23:40:32 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24F1937B401 for ; Sat, 22 Feb 2003 23:40:30 -0800 (PST) Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7243A43FB1 for ; Sat, 22 Feb 2003 23:40:29 -0800 (PST) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by cs.huji.ac.il with esmtp id 18mqkK-000BdZ-00; Sun, 23 Feb 2003 09:40:24 +0200 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Matthew Dillon Cc: Chris Shenton , current@FreeBSD.ORG Subject: Re: Diskless: 5.0R scripts, boot, NFS mount problems I didn't have in 4.7S In-Reply-To: Message from Matthew Dillon of "Sat, 22 Feb 2003 17:46:26 PST." <200302230146.h1N1kQrZ024560@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Feb 2003 09:40:24 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message