From owner-freebsd-small Sat Sep 4 19:30:37 1999 Delivered-To: freebsd-small@freebsd.org Received: from dingo.cdrom.com (castles529.castles.com [208.214.165.93]) by hub.freebsd.org (Postfix) with ESMTP id E5FF914BD5; Sat, 4 Sep 1999 19:30:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id TAA08660; Sat, 4 Sep 1999 19:14:11 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909050214.TAA08660@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chris Dillon Cc: "David O'Brien" , config@FreeBSD.ORG, small@FreeBSD.ORG Subject: Re: Odd idea In-reply-to: Your message of "Sat, 04 Sep 1999 21:13:49 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Sep 1999 19:14:10 -0700 From: Mike Smith Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Doh. I wish there were some way other than specifying the MAC address > to say to the DHCP/BOOTP server "give me FOO configuration". I was > trying to think of a way to make a boot disk which required a minimal > amount of system-dependant information tied to the boot disk itself or > to the station you are booting it from. Unfortunately I guess neither > BOOTP nor DHCP can fit this bill (or can it?). 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. -- \\ 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