Date: Fri, 04 Apr 1997 21:12:46 +0100 From: Brian Somers <brian@awfulhak.org> Cc: CVS-committers@freebsd.org, cvs-all@freebsd.org, cvs-ports@freebsd.org Subject: Re: cvs commit: ports/net/wide-dhcp/patches patch-aw patch-ax patch-ay patch-az Message-ID: <199704042012.VAA13390@awfulhak.demon.co.uk> In-Reply-To: Your message of "Thu, 03 Apr 1997 18:37:15 -0800." <199704040237.SAA08531@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> brian 97/04/03 18:37:14
>
> Added: net/wide-dhcp/patches patch-aw patch-ax patch-ay patch-az
> Log:
> Finish the update to wide-dhcp so that it compiles with the
> new interface stuff and if_var.h
>
> Closes pr3161
>
> Submitted by: MIHIRA Yoshiro <sanpei@yy.cs.keio.ac.jp>
> Obtained from: pr3161
>
In fact, I should have mentioned that dhcpc now has a -r and -n
option. -r says to update /etc/resolv.conf and -n says to update
the current hostname.
This (-n) is "hugely" good for laptops (IMHO), 'cos it allows X,
nmbd etc. to work.
<RANT>
I've moaned before about the fundamental mistake that lots of
programs that "send their machine name" make - they send the
value of gethostent() - a bogus leftover from the dark ages if
you ask me ! They "should" send the IP of the interface that's
maintaining the connection on which they're sending the info.
What is gethostent() for anyway ?
</RANT> (now *stop* that!)
If we must live with gethostent(), the -n option allows us to
set up our most probable hostname :)
--
Brian <brian@awfulhak.org>, <brian@freebsd.org>
<http://www.awfulhak.demon.co.uk/>;
Don't _EVER_ lose your sense of humour....
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704042012.VAA13390>