From owner-freebsd-arch Mon Apr 8 17:15:13 2002 Delivered-To: freebsd-arch@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 6475637B420 for ; Mon, 8 Apr 2002 17:14:38 -0700 (PDT) Received: from caddis.yogotech.com (yogotech.nokia.com [4.22.66.156]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id SAA13023; Mon, 8 Apr 2002 18:14:35 -0600 (MDT) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by caddis.yogotech.com (8.11.6/8.11.6) id g390EXD01292; Mon, 8 Apr 2002 18:14:33 -0600 (MDT) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15538.12905.744914.71228@caddis.yogotech.com> Date: Mon, 8 Apr 2002 18:14:33 -0600 To: Luigi Rizzo Cc: arch@FreeBSD.ORG Subject: Re: proposed code: automatic setting of hostname from MAC address In-Reply-To: <20020407035941.B37911@iguana.icir.org> References: <20020407035941.B37911@iguana.icir.org> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > as part of the PicoBSD "rc" scripts, there is some code which > determines the hostname (and IP) of a box from the MAC address > of the first ethernet interface, using /etc/hosts > as a database of known machines. The relevant code is in > > src/release/picobsd/floppy.tree/etc/rc.conf.defaults For what it's worth, I think this code is of little value (and I use PicoBSD) code. Can you explain why you believe this code is of more value than simply configuring the interfaces based on their order? > I was wondering whether, with the necessary modifications (see > NOTES), there is interest in merging this feature into the standard > startup scripts. For PicoBSD the usefulness is obvious -- being > images often resident on removable media, this lets you use the > exact same image for different machines. How so vs. the standard way of just configuring an interface? > I have other setups where this can be useful, e.g. I often use disks > on removable frames and move them back and forth across different > machines; or, for some centrally-administered configurations, this > mechanism can also be very useful, as it permits to centralise the > configuration to one or two files (rc.conf plus the database of > MAC<->hostnames). > > Comments ? In my opinion, it's less flexible than the current scheme of ifconfig_ed0="inet 192.168.0.1/24" ifconfig_fxp0="inet 192.168.0.1/24" Or whatever in /etc/rc.conf. You're setup requires a very non-standard configuration file of /etc/hosts, which is still a custom configuration file, vs. the standard customized file in /etc/rc.conf. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message