Date: Thu, 07 Sep 2006 10:48:39 -0400 From: "Brian A. Seklecki" <bseklecki@collaborativefusion.com> To: Erik Norgaard <norgaard@locolomo.org> Cc: alfred@FreeBSD.org, doc@FreeBSD.org Subject: Re: FreeBSD Jumpstart Guide / PXE Docs (TFTP ONLY) Message-ID: <1157640519.83171.129.camel@soundwave.pgh.priv.collaborativefusion.com> In-Reply-To: <44FE8B9D.5080707@locolomo.org> References: <1157495592.83171.49.camel@soundwave.pgh.priv.collaborativefusion.com> <44FE8B9D.5080707@locolomo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> The problem with NFS/TFTP you mention have existed for years, I reported > it in 2004: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/74352 > > The workaround/solution is documented in the guide I wrote: > > a) Compile kernel w/o NFS support and load these as modules after boot Actually, now that I'm working it more closely (took a day to hack the Dell PE 1950 problems), it would seem that your problem has to do with a post-kernel load issue of finding the NFS root. My problem is that even when you compile the pxeboot(8) binary w/o NFS support, it still tries to do NFS (depending on DHCP variables, it seems). The other problem is that the NFS code sets the destination UDP port of the NFS Mount request to port "0", which causes my PIX Firewall to, well, you know... ~BAS > b) Specify in loader.conf that the root device is mfs > > I cleaned up the guide I wrote and I posted here some months ago if > anyone would take a look at it: > > http://www.daemonsecurity.com/pub/pxeboot/ > > Cheers, Erik -- Brian A. Seklecki <bseklecki@collaborativefusion.com> Collaborative Fusion, Inc.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1157640519.83171.129.camel>