Date: Wed, 10 Feb 1999 01:04:18 -0800 From: "David O'Brien" <obrien@NUXI.com> To: current@FreeBSD.ORG Subject: Re: Which DHCP client Message-ID: <19990210010418.B8770@relay.nuxi.com> In-Reply-To: <199902091904.LAA12340@pinhead.parag.codegen.com>; from Parag Patel on Tue, Feb 09, 1999 at 11:04:27AM -0800 References: <mi@misha.cisco.com> <199902091904.LAA12340@pinhead.parag.codegen.com>
next in thread | previous in thread | raw e-mail | index | archive | help
OK, I've decided to import the ISC client. I am not pleased with this
choice, but I believe the FreeBSD community in general seems to prefer
this choice.
Swaying arguments:
1. OpenBSD uses the ISC client and keep a careful eye on it for software
engineering issues. (which is really all that buffov problems are)
2. Mike Smith's emails (priv and public) show that the ISC client offers
us more options in configuring a system than the WIDE client. Issues
include sysinstall bootstrapping support and /etc/rc* hooks.
For the record, version 2 of the ISC client *DOES* in fact require an
/etc/dhclient.conf file:
# dhclient fxp0
Can't open /etc/dhclient.conf: No such file or directory
exiting.
this is stupid and I have a mind to change it to:
Can't open /etc/dhclient.conf: using built-in defaults
continuing.
Also, /etc/dhclient-script *IS* required:
# dhclient fxp0
/tmp/dcsFoU405: /etc/dhclient-script: not found
/tmp/dcsWOk405: /etc/dhclient-script: not found
fxp0: not found
exiting.
NOTE that unlike the WIDE client, the ISC client defaults to overwriting
your /etc/resolv.conf file. In my case, an action that pisses me off
because I now have to write a messy /etc/dhclient.conf file to stop this
nonsence.
--
-- David (obrien@NUXI.com -or- obrien@FreeBSD.org)
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?19990210010418.B8770>