From owner-freebsd-current Thu Jan 27 16:13:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E481C15C2A; Thu, 27 Jan 2000 16:13:32 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA46201; Thu, 27 Jan 2000 16:14:15 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 18:25:30 EST." <200001272325.SAA60073@server.baldwin.cx> Date: Thu, 27 Jan 2000 16:14:15 -0800 Message-ID: <46198.949018455@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why not check to see what the hostname is after dhclient is run and then > stick that name in the network setup dialog box. If the user does edit > the hostname themselves, then you can flag that event. That would work in that one specific case with that specific dhcp server. Now change the dhcp server post-install time and watch what happens. :-) What is clearly needed is some idea of "fallback hostname" vs the one you *might* be automatically assigned by "something else" (one current value for something else being DHCP) and should probably use preferentially. Split the hostname into two variables and do the appropriate rc dance magic, off ya go. Of course, this also fails to address a more fundamental failing in our rc scripts, this being that the concept of "network identity" is currently handled in too simplistic a fashion. When dealing with the "local vs on the road" scenario, many laptop users (including myself) end up hand-editing their rc.conf files or adding some cheesy menu to the rc files which say, in effect, "choose one of the following canned configurations" and then go work the appropriate variable-setting magic. The fact that I've seen so many people re-invent this particular wheel also sends a strong hint that a better, more general, mechanism is now overdue. As the original architect of FreeBSD's rc.conf (nee /etc/sysconfig) mechanism, I can also say with some assurance that it's reached its limits. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message