Date: Mon, 5 Jun 2006 12:37:05 -0400 From: "Zaphod Beeblebrox" <zbeeble@gmail.com> To: "Lowell Gilbert" <freebsd-stable-local@be-well.ilk.org> Cc: Damian Gerow <dgerow@afflictions.org>, freebsd-stable@freebsd.org Subject: Re: [OT] resolv.conf and dhclient Message-ID: <5f67a8c40606050937s7317e9c6hfdf36903ceaadb9a@mail.gmail.com> In-Reply-To: <44r72365l3.fsf@be-well.ilk.org> References: <44842282.6050409@veldy.net> <448428D8.5030501@orchid.homeunix.org> <20060605134049.GB99893@afflictions.org> <44r72365l3.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/5/06, Lowell Gilbert <freebsd-stable-local@be-well.ilk.org> wrote: > > Damian Gerow <dgerow@afflictions.org> writes: > > > I've often wondered why dhclient.conf doesn't have an 'ignore' > directive. > > There's a 'require' in there; it doesn't seem like much of a stretch to > > 'ignore' something. > > Why not just write a simple script for one of the hooks that > dhclient-script(8) supports? Well... this would be mildly acceptable if he were the only one with this problem, but I suspect it's much more common. I use the wireless interface on my laptop (in general) for internet access ... and thus desire the behaviour where the nameservers are written to resolv.conf and I use the wired ethernet (in general) to configure all manner of little routers and whatnot (so I don't want resolv.conf rewritten). Thus the simple solution 'chflags /etc/resolv.conf' doesn't work. An ignore directive would work --- as would writing a script --- but it seems that this issue is common enough to argue for the ignore directive.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5f67a8c40606050937s7317e9c6hfdf36903ceaadb9a>