From owner-freebsd-arch Mon Apr 8 17:45:10 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id E75D537B416 for ; Mon, 8 Apr 2002 17:45:05 -0700 (PDT) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g390j3sH493438; Mon, 8 Apr 2002 20:45:04 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <15538.12905.744914.71228@caddis.yogotech.com> References: <20020407035941.B37911@iguana.icir.org> <15538.12905.744914.71228@caddis.yogotech.com> Date: Mon, 8 Apr 2002 20:45:02 -0400 To: nate@yogotech.com (Nate Williams), Luigi Rizzo From: Garance A Drosihn Subject: Re: proposed code: automatic setting of hostname from MAC address Cc: arch@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) 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 At 6:14 PM -0600 4/8/02, Nate Williams wrote: >Luigi Rizzo wrote: > > >> 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. Hmm. I did not understand Luigi's reference to /etc/hosts, but I had assumed that the feature was similar to how MacOS 10 works. The machine gets an IP address via DHCP (for instance), and then sets the machine's hostname based on what DNS says is the hostname for that IP address. That works out pretty well. But Now that I've read his message a little closer, I see he's talking about something else. While his code does require a custom configuration, there still is some point to it, if he's using it on a lot of machines. It's *one* custom image which can be used on a hundred different machines (if you personally are running a hundred different machines, such as in a public-lab setting). I must admit I haven't had a lot of time to think about the specific implementation he's asking about, although I have the feeling that something like it could be generally useful. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message