From owner-freebsd-current Thu Jan 27 18:45:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 3D9EB157E7 for ; Thu, 27 Jan 2000 18:45:14 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA05541; Thu, 27 Jan 2000 18:53:51 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001280253.SAA05541@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 21:26:44 EST." <200001280226.VAA21947@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jan 2000 18:53:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > That's not correct; your DHCP configuration should reflect the hostname. > > No, it shouldn't. As I keep on trying to explain, the DHCP addresses > are: > > 1) Temporary. > 2) Meaningless. > 3) Temporary. > 4) Temporary. > 5) Temporary. Since the hostname is simply a plain-text token for the IP address, it has to remain bound to the IP address (whether that binding is fixed or dynamic is outside the scope of this discussion). Having a hostname that doesn't map to your IP address is a misconfiguration, and not a useful one at that. The only argument for having a dysfunctional hostname of the variety you describe is vanity, which is not a valid engineering constraint. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message