public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: resolv.conf is different after every reboot
Date: Sun, 27 Jul 2014 16:33:17 +0000 (UTC)	[thread overview]
Message-ID: <loom.20140727T182409-418@post.gmane.org> (raw)
In-Reply-To: CACE6sHnsd6Y+WMkGf=Jh=0VHsGK9J8CvV3uFZe8+EOvM=dE=oA@mail.gmail.com

Grand Duet <grand.duet <at> gmail.com> writes:


> >> In short: the contents of the file /etc/resolv.conf
> >> is unpredictably different from one reboot to another.
> >> It is either
> >>   # Generated by net-scripts for interface lo
> >>   domain mynetwork or
> >>   # Generated by net-scripts for interface "eth0"
> >>   nameserver My.First.DNS-Server.IP
> >>   nameserver My.Second.DNS-Server.IP
> >>   nameserver 8.8.8.8


I set my nameservers all manually in this file and they do
not every change. I do not run systemd. I'm not sure
of your issue(s) but, historically, resolv.conf should not
be displaying this behavior.

> > and also the output of the "rc-update show" command?
> 
> # rc-update show

>                      mtab | boot
>                net.eth0 |      default
>                     net.lo | boot
>              netmount |      default


> Everywhere above eth0 has been put instead of its udev "predictable" name.
> Do you think that I need
>     carrier_timeout_eth0=20
> somewhere in /etc/conf.d/net ?

I do not try and force the "eth' names onto an interface
I have these in rc-status:

mtab | boot                          
net.enp5s0 |      default
netmount |      default

I just look at the dmesg output and use the new, default
funky names. You can read up on these evolving interface
names by googling.

Here is one link (often posted to this user group) to get you started:

   
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/


hth,
James



  parent reply	other threads:[~2014-07-27 16:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-27  9:21 [gentoo-user] resolv.conf is different after every reboot Grand Duet
2014-07-27  9:29 ` Neil Bothwick
2014-07-27 10:33   ` Grand Duet
2014-07-27 11:13     ` Dale
2014-07-27 13:10     ` Matti Nykyri
2014-07-27 13:39       ` Grand Duet
2014-07-27 15:36         ` Matti Nykyri
2014-07-27 19:13     ` Neil Bothwick
2014-07-27 20:38       ` Grand Duet
2014-07-27 22:00         ` Kerin Millar
2014-07-28 15:34           ` Grand Duet
2014-07-30 22:22             ` Kerin Millar
2014-07-27 10:39 ` Walter Dnes
2014-07-27 11:30   ` Grand Duet
2014-07-27 14:50     ` Daniel Frey
2014-07-27 15:08       ` Grand Duet
2014-07-27 20:28         ` Daniel Frey
2014-07-27 20:53           ` Grand Duet
2014-07-27 16:33     ` James [this message]
2014-07-27 17:23       ` [gentoo-user] " Grand Duet
2014-07-27 23:00       ` Rich Freeman
2014-07-27 18:14     ` [gentoo-user] " Kerin Millar
2014-07-27 20:26       ` Grand Duet

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=loom.20140727T182409-418@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox