atom feed23 messages in org.freebsd.freebsd-smallRe: Odd idea
FromSent OnAttachments
Mike SmithSep 2, 1999 11:41 pm 
Warner LoshSep 2, 1999 11:44 pm 
Skip HansenSep 3, 1999 8:10 am 
Chris DillonSep 3, 1999 10:10 am 
Mike SmithSep 3, 1999 12:08 pm 
Mike SmithSep 3, 1999 12:35 pm 
John IoannidisSep 3, 1999 12:35 pm 
Warner LoshSep 3, 1999 12:41 pm 
Skip HansenSep 3, 1999 1:38 pm 
David O'BrienSep 3, 1999 2:16 pm 
Broderick WoodSep 3, 1999 2:59 pm 
Chris DillonSep 3, 1999 3:02 pm 
David O'BrienSep 3, 1999 3:39 pm 
Mike SmithSep 3, 1999 3:44 pm 
David O'BrienSep 3, 1999 4:15 pm 
Mike SmithSep 3, 1999 4:19 pm 
Jac BackusSep 4, 1999 12:36 pm 
Kent BerggrenSep 4, 1999 1:48 pm 
Chris DillonSep 4, 1999 7:13 pm 
Mike SmithSep 4, 1999 7:13 pm 
Chris DillonSep 4, 1999 10:20 pm 
Mike SmithSep 4, 1999 11:18 pm 
Chris DillonSep 5, 1999 12:01 am 
Subject:Re: Odd idea
From:Mike Smith (mi@smith.net.au)
Date:Sep 4, 1999 11:18:49 pm
List:org.freebsd.freebsd-small

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)

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message