Date: Thu, 27 Jan 2000 19:15:35 -0800 From: "David O'Brien" <obrien@freebsd.org> To: current@freebsd.org Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Message-ID: <20000127191535.B82635@dragon.nuxi.com> In-Reply-To: <200001280222.SAA05076@mass.cdrom.com>; from msmith@freebsd.org on Thu, Jan 27, 2000 at 06:22:55PM -0800 References: <20000127180916.B82262@dragon.nuxi.com> <200001280222.SAA05076@mass.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 27, 2000 at 06:22:55PM -0800, Mike Smith wrote: > Correct behaviour would be not to set the hostname unless: > a) it is not already set > or > b) it was previously set by the DHCP client > > You could probably ignore b) and satisfy most people. At the moment, the > hostname is _never_ set by the DHCP client _unless_ it finds a lease that > is still valid. This is clearly a bug. Agreed. I will happily accept a patch anybody that got to this before I manage do. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000127191535.B82635>