Date: Thu, 8 Jul 2004 16:14:46 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Brian Somers <brian@Awfulhak.org> Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Witness breakage Message-ID: <20040708231446.GA3362@troutmask.apl.washington.edu> In-Reply-To: <20040708233037.3e310ca1@dev.lan.Awfulhak.org> References: <20040707182018.GA45659@atrbg11.informatik.tu-muenchen.de> <200407081310.37603.jhb@FreeBSD.org> <200407081715.19073.jhb@FreeBSD.org> <20040708214922.GA2328@troutmask.apl.washington.edu> <20040708150037.N46651@carver.gumbysoft.com> <20040708220858.GB2680@troutmask.apl.washington.edu> <20040708151522.L46651@carver.gumbysoft.com> <20040708233037.3e310ca1@dev.lan.Awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 08, 2004 at 11:30:37PM +0100, Brian Somers wrote: > On Thu, 8 Jul 2004 15:18:03 -0700 (PDT), Doug White <dwhite@gumbysoft.com> wrote: > > On Thu, 8 Jul 2004, Steve Kargl wrote: > > > > > There are no BOOTP or NFS related options. See below > > > > Therein lies the rub -- the removal of the BOOTP kernel option by brian@ > > makes NFSCLIENT required, since the bootp client is tightly bound to the > > NFS client. It should be backed out and bootp properly disentangled if > > its going to be mandatory. I've added him to the thread. > > > > Hmm, without options NFSCLIENT, you should be able to load nfsclient.ko then > set bootp="YES" and bootp.nfsboot="YES".... You first need to be able to build a kernel. ;-) Thanks for backing out the earlier commit. "make buildkernel" is again functioning. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040708231446.GA3362>