Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 06 Jun 2006 09:51:37 -0400
From:      Lowell Gilbert <freebsd-stable-local@be-well.ilk.org>
To:        Damian Gerow <dgerow@afflictions.org>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: [OT] resolv.conf and dhclient
Message-ID:  <44u06ywfx2.fsf@be-well.ilk.org>
In-Reply-To: <20060605195654.GK99893@afflictions.org> (Damian Gerow's message of "Mon, 5 Jun 2006 15:56:54 -0400")
References:  <44842282.6050409@veldy.net> <448428D8.5030501@orchid.homeunix.org> <20060605134049.GB99893@afflictions.org> <44r72365l3.fsf@be-well.ilk.org> <20060605195654.GK99893@afflictions.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Damian Gerow <dgerow@afflictions.org> writes:

> Thus spake Lowell Gilbert (freebsd-stable-local@be-well.ilk.org) [05/06/06 10:32]:
> : > 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?  
>
> I'd looked at this before (a few months back), and deemed it insufficient
> for the job.  However, upon your re-suggestion, I can't see why it /won't/
> work.  It should also be able to figure out which wired LAN the machine is
> connected to, and assign the appropriate DNS servers.  So this /may/
> actually address my problem.  (Goodness knows why I originally dismissed
> it.)
>
> However, this ignores my original question: why is there no 'ignore'
> directive in dhclient.conf? 

I don't think it does really beg the question: the existence of other
options reduces the impetus for someone to write it and get it
accepted in to the codebase.

And hidden in there is the direct answer to your question:  the
feature doesn't exist because no one has written it.

>                              It seems like a potentially incredibly useful
> thing, and I run across posts from people who could greatly benefit from
> this every couple of months.

Perhaps, but most of the time "supersede" (or "prepend" or "append")
will solve their problems fine.  At least, that's my experience from
watching this list.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44u06ywfx2.fsf>