From owner-freebsd-current Thu Jan 27 18:15:37 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 60F5015C20; Thu, 27 Jan 2000 18:15:29 -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 SAA05093; Thu, 27 Jan 2000 18:24:07 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001280224.SAA05093@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Jordan K. Hubbard" Cc: Mike Smith , Garrett Wollman , obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 18:10:45 PST." <86640.949025445@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jan 2000 18:24:07 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That's not correct; your DHCP configuration should reflect the hostname. > > > > Sysinstall doesn't fill in the hostname field because the crunched binary > > is missing the hostname(1) command. If we were to add that, it's just > > possible that we'd get hostnames working too. > > Actually, that's not quite true and hasn't been for awhile now: > > jkh@highwing-> grep hostname /usr/src/release/*conf* > /usr/src/release/boot_crunch.conf.generic:progs dhclient arp hostname In that case I can only assume that the dhclient-script is looking for it in the wrong place. The last snap I installed was around the 25th and it still failed to pick up the hostname. -- \\ 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