Date: Tue, 13 Dec 2005 12:00:48 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: Daniel Feenberg <feenberg@nber.org> Cc: brooks@freebsd.org, jhb@freebsd.org, gwr@mc.com, ps@freebsd.org, net@freebsd.org, dwhite@freebsd.org Subject: Re: Does pxeboot support option 134? Message-ID: <20051213114709.D71016@carver.gumbysoft.com> In-Reply-To: <Pine.GSO.4.10.10512131242440.17248-100000@nber1.nber.org> References: <Pine.GSO.4.10.10512131242440.17248-100000@nber1.nber.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Remove duplicate ps@.
On Tue, 13 Dec 2005, Daniel Feenberg wrote:
>
> I am trying to do diskless booting. Right now I am trying to make the
> /conf/${class}/ function provided in FreeBSD 6.0 work. I have had success
> with /conf/${ip}/ but not with ${class}.
>
> I have
>
> option t134-cookie code 134=text
>
> at the beginning of my dhcpd.conf file, and
>
> option t134-cookie "client"
>
> with the other parameters for the diskless client. The dhcpd server is on
> a FreeBSD 5.2.1 system (everything else is 6.0). I have the impression
> that the dhcp server is ok with these settings, however, no mention of
> T134 makes appears in the output of bootptest when run on the client.
>From my reading of the source, vendor-option 134 is only parsed by the
nfsclient bootp code which is activated with the BOOTP kernel option. If
you want to use that feature via PXE then pxe_open() in
src/sys/boot/i386/libi386/pxe.c needs modification, specifically to parse
the array in bootplayer.d.
pxeboot passes its information via kenv and would require a bit of code
hidden somewhere to convert it into a sysctl to maintain compatibility
with the BOOTP feature.
--
Doug White | FreeBSD: The Power to Serve
dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051213114709.D71016>