From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mail.openembedded.org (Postfix) with ESMTP id 14285725CD for ; Tue, 16 Dec 2014 17:18:10 +0000 (UTC) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga103.jf.intel.com with ESMTP; 16 Dec 2014 09:04:54 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.04,691,1406617200"; d="scan'208";a="499636843" Received: from unknown (HELO [10.255.13.137]) ([10.255.13.137]) by orsmga003.jf.intel.com with ESMTP; 16 Dec 2014 09:02:40 -0800 Message-ID: <549066AB.30909@linux.intel.com> Date: Tue, 16 Dec 2014 09:06:51 -0800 From: Saul Wold User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Philip Balister , Khem Raj References: <54904BDA.1080005@balister.org> <7CC1BDD4-170B-422B-BC51-33EC0B07E64A@gmail.com> <549063E9.4070403@balister.org> In-Reply-To: <549063E9.4070403@balister.org> Cc: openembedded-core Subject: Re: Setting a a fixed resolv.conf file in OE built image X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Dec 2014 17:18:19 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 12/16/2014 08:55 AM, Philip Balister wrote: > On 12/16/2014 11:40 AM, Khem Raj wrote: >> >>> On Dec 16, 2014, at 7:12 AM, Philip Balister wrote: >>> >>> Any tips on how to do this the right way? It seems like fixed >>> resolv.conf's are no longer fashionable and the volatile.cache script >>> goes to great lengths to reset it. >>> >>> Adding a dns-nameserver entry in the interfaces file never makes it to >>> resolv.conf. I tried installing the resolvconf package and played with >>> it, but no joy. This package also appears to have some issues with >>> missing pieces. >> >> depends a lot on what package combination you are using. If its systemd and you >> are using systemd-resolved then it generates resolve.conf in /run/ and symlink >> in /etc/ gets the job done. if its udhcpc then it will populate the one in /etc >> and it will take interfaces file in /etc into consideration > > Yeah, but this is an image built by adding packages to core-image. No > systemd or other network managers. It feels like just adding the > dns-nameserver line to interfaces should work, but something appears to > not re-populate resolv.conf after it is wiped at boot. > I recently sent some patches to this area, dealing with all the dhcp clients and resolvconf package. Can you enumerate which networking tools you have installed, if you are not using any network manager or dhcp client and relying on a static dns-nameserver entry, you might need resolvconf if you are not using it. Also which version of oe-core meta-data are you using? Sau! > Philip > >> >>> >>> I'll file bugs, but until I can figure out how it is suposed to work, >>> any bug I file is going to be pretty vague. >>> >>> This really should be easier. >>> >>> Philip >>> -- >>> _______________________________________________ >>> Openembedded-core mailing list >>> Openembedded-core@lists.openembedded.org >>> http://lists.openembedded.org/mailman/listinfo/openembedded-core >> >> >>