Date: Thu, 27 Jan 2000 18:09:16 -0800 From: "David O'Brien" <obrien@freebsd.org> To: Mike Smith <msmith@freebsd.org> Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, current@freebsd.org Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Message-ID: <20000127180916.B82262@dragon.nuxi.com> In-Reply-To: <200001280020.QAA03272@mass.cdrom.com>; from msmith@freebsd.org on Thu, Jan 27, 2000 at 04:20:54PM -0800 References: <46146.949017991@zippy.cdrom.com> <200001280020.QAA03272@mass.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 27, 2000 at 04:20:54PM -0800, Mike Smith wrote: > > Actually, the problem here is that our dhclient doesn't pick the hostname > up the first time around. If it's set in an existing lease that is just > confirmed, it works, but if you're starting without a lease, you won't > get a hostname set (but it will be in the lease file, so if you restart > before the lease expires you're OK). Are you sure? In the case I know you experience, the server changed its behavior WRT handing out hostnames. I don't doubt that such a switch mid-stream in using DHCP would confuse things. > Personally I'd prefer to just fix the DHCP client so that it correctly > sets the hostname as obtained from the server... Nope. Poll larger shops first on their DHCP usage. -- -- 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?20000127180916.B82262>