From owner-freebsd-current@FreeBSD.ORG Sat Apr 26 17:48:54 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCA59106564A; Sat, 26 Apr 2008 17:48:54 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id 70F2B8FC19; Sat, 26 Apr 2008 17:48:54 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender:X-Spam-Status:Subject; b=o3Hqw+7X6cH4t2LSOd6yirLI73kZgTcWCpFFJrN6UUNuITuV9kVukZuLMQbcigK5+HZmUs6y4gq6kVn8kD9ElC7KgYCfeGu47PzuVvXZN6ngx9fR/JMlWKniQ6aeU8kWMFQO4MDNVL310u8jX1qDp2ZpUsmaIXpSaXH8sgj/qx4=; Received: from amnesiac.at.no.dns (ppp91-78-116-255.pppoe.mtu-net.ru [91.78.116.255]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1JpoW4-000A7r-Qv; Sat, 26 Apr 2008 21:48:53 +0400 Date: Sat, 26 Apr 2008 21:48:54 +0400 From: Eygene Ryabinkin To: John Baldwin Message-ID: References: <200804240821.40601.jhb@freebsd.org> <200804251607.39798.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <200804251607.39798.jhb@freebsd.org> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-2.3 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_20 Cc: Poul-Henning Kamp , freebsd-current@freebsd.org Subject: Re: [RFC] Automated generation of /etc/resolv.conf from the rc.d script X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Apr 2008 17:48:54 -0000 John, good day. Fri, Apr 25, 2008 at 04:07:39PM -0400, John Baldwin wrote: > > In the case of DHCP -- yes, I can. But sometimes I need to specify > > the static entries for the resolv.conf: I am using it when I am > > working in some places where DHCP isn't available, so I am creating > > branched /etc/rc.conf. And it is useful to have all variables in > > one place. For my usage, dhclient.conf is not relevant, since I > > am happily taking all that was given me via DHCP. > > This was not clear from your earlier e-mails where it seemed that you were > worried primarily about munging dhclient-script (which would be the DHCP > case). May be I was not clear. Sorry for that. > Given that you can already manage the DHCP case > via /etc/dhclient.conf I think adding rc.conf variables to duplicate that > functionality would be superfluous. I think you're not understood what I did. I had added rc.conf variables that will override anything: DHCP, existing resolv.conf, etc. They are not tied to any particular way of obtaining the needed information for the resolv.conf: they just forcing to use the specified values. That was the first patch. The second patch was concerned with the named forwarders. It had also touched /etc/rc.d/resolv making it to recognize kenv variables dhclient.*. It was done to unify the place of management for /etc/resolv.conf: since dhclient-script was also trying to create /etc/resolv.conf, I decided to move this functionality to the standard place (/etc/rc.d/resolv) and to make dhclient-script to call it. So there is no functionality duplication concerned with the new rc.conf variables in the general case. There are (possibly redundant) modifications to the dhclient-script to make it call rc.d script, but this is not what you're talking about. Any views? -- Eygene