Date: Sat, 04 Sep 1999 23:19:11 -0700 From: Mike Smith <mike@smith.net.au> To: Chris Dillon <cdillon@wolves.k12.mo.us> Cc: config@FreeBSD.ORG, small@FreeBSD.ORG Subject: Re: Odd idea Message-ID: <199909050619.XAA09759@dingo.cdrom.com> In-Reply-To: Your message of "Sun, 05 Sep 1999 00:20:48 CDT." <Pine.BSF.4.10.9909042356050.80314-100000@mail.wolves.k12.mo.us>
next in thread | previous in thread | raw e-mail | index | archive | help
> > You need a physical token of some sort to identify the machine; either > > you use the MAC address or in some cases the GUID or UUID storage (on an > > intel system) or some other NVRAM token depending on the system in > > question. > > > > But the ethernet MAC address is about the only universal uniquifier > > that any system has, so you really don't have much choice. > > I was thinking more along the line of the dhcp-client-identifier which > is sent to the DHCP server by the client (which I guess is what you > are referring to, also, in the case of the "token"). Since the > hostname can be used as this identifier, it would be possible for me > to give each install disk a hostname of install# and then configure > dhcpd to give anything with hostname install* a certain configuration. In this case, the physical token is the floppy disk. > Would the DHCP client in the loader support doing this? If it didn't, you would have the source code, and I would be very receptive to any input along those lines. 8) -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909050619.XAA09759>