All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Setting a a fixed resolv.conf file in OE built image
Date: Tue, 16 Dec 2014 11:55:05 -0500	[thread overview]
Message-ID: <549063E9.4070403@balister.org> (raw)
In-Reply-To: <7CC1BDD4-170B-422B-BC51-33EC0B07E64A@gmail.com>

On 12/16/2014 11:40 AM, Khem Raj wrote:
> 
>> On Dec 16, 2014, at 7:12 AM, Philip Balister <philip@balister.org> 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.

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
> 
> 
> 


  reply	other threads:[~2014-12-16 16:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16 15:12 Setting a a fixed resolv.conf file in OE built image Philip Balister
2014-12-16 16:40 ` Khem Raj
2014-12-16 16:55   ` Philip Balister [this message]
2014-12-16 17:06     ` Saul Wold
2014-12-17  0:54       ` Philip Balister

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=549063E9.4070403@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.