From owner-freebsd-current  Thu Jan 27 16:12:18 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 D80E0158E1; Thu, 27 Jan 2000 16:12:15 -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 QAA03272;
	Thu, 27 Jan 2000 16:20:54 -0800 (PST)
	(envelope-from msmith@mass.cdrom.com)
Message-Id: <200001280020.QAA03272@mass.cdrom.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: 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 16:06:31 PST."
             <46146.949017991@zippy.cdrom.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 27 Jan 2000 16:20:54 -0800
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > IMHO, that is the wrong assumption.  Most DHCP servers I've seen aren't
> > setup to provide hostnames to the requrestor.
> 
> Seems they're set up incorrectly then.  You can't be a good "network
> citizen" these days without a resolvable hostname that also matches
> your primary IP address or, among other things, you won't be able to
> send mail directly to anyone who practices traditional spam filtering
> techniques.

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).

> This also isn't just pedantry because, as I noted before, specifying
> the hostname will currently cause it to override the DHCP hostname
> value even if it is specified (as it certainly is on *my* DHCP server :-)
> and result in broken behavior for the aformentioned mailers.  If we
> were to fix that in our rc scripts, I could remove this assumption in
> sysinstall in good conscience.

Personally I'd prefer to just fix the DHCP client so that it correctly 
sets the hostname as obtained from the server...


-- 
\\ 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