public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Browsers cannot access WWW while ping and host utilities work as expected.
Date: Mon, 5 Aug 2013 09:41:09 -0500	[thread overview]
Message-ID: <20130805144109.GM25510@server> (raw)
In-Reply-To: <20130805163144.69653f43@marcec>

On Mon, Aug 05, 2013 at 04:31:44PM +0200, Marc Joliet wrote:
> Am Mon, 5 Aug 2013 07:59:09 -0500
> schrieb Bruce Hill <daddy@happypenguincomputers.com>:
> 
> > If this is "the new kernel naming scheme of NICs", why this in dmesg:
> > 
> > [    4.725902] systemd-udevd[1176]: renamed network interface wlan0 to enp0s18f2u2
> > 
> > It looks as if systemd-udev renamed the NIC to me. Can you explain?
> 
> It already has been explained in the previous NIC renaming discussion: what's
> broken is renaming a device within the kernels internal namespace, which
> contains eth*, wlan* (and maybe others). The problem is that there is a race
> condition with the kernel when renaming ethX to ethY. What you *can* do is
> rename ethX to somethingelseX or somethingelseY, because then you are not racing
> against the kernel to hand out device names.
> 
> This is explained on the website that also explains the new default renaming
> scheme used by udev. I (and IIRC others, too) already linked to it in in the old
> thread, and the relevant news item also referenced it, but here it is again:
> 
>   http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

The fact is that udev renamed the NIC. For the average Joe with one NIC (very
large percentage of users) this is a non sequitur. For those of us with 2 or
more NICs, myself included, we have already setup our systems to use multiple
NICs for a purpose and configured the system so that nothing can/will/needs to
rename subsequent NICs.

My point is don't say "the new kernel naming scheme of NICs", say "the new
systemd naming scheme of NICs".
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.                                                                                                                                                          
Q: Why is top-posting such a bad thing?                                                                                                                                                                                        
A: Top-posting.                                                                                                                                                                                                                
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting


  reply	other threads:[~2013-08-05 14:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-04 18:56 [gentoo-user] Browsers cannot access WWW while ping and host utilities work as expected gevisz
2013-08-04 19:21 ` Mark Pariente
2013-08-04 19:57 ` Mick
2013-08-04 20:10   ` Kurian Thayil
2013-08-05  6:06   ` gevisz
2013-08-05 10:06     ` Mick
2013-08-05 12:59       ` Bruce Hill
2013-08-05 14:31         ` Marc Joliet
2013-08-05 14:41           ` Bruce Hill [this message]
2013-08-05 15:21             ` Marc Joliet
2013-08-05 15:37             ` Mick
2013-08-05 16:43             ` Stroller
2013-08-05 17:28             ` Alan McKinnon
2013-08-06 22:57               ` Stroller
2013-08-12  7:13       ` gevisz
2013-08-12  9:10         ` Alan McKinnon
2013-08-13  6:31           ` gevisz
2013-08-13  7:05             ` Alan McKinnon
2013-08-05 18:37   ` [gentoo-user] " Grant Edwards

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=20130805144109.GM25510@server \
    --to=daddy@happypenguincomputers.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