| 1 |
On Monday 05 Aug 2013 15:41:09 Bruce Hill wrote: |
| 2 |
> On Mon, Aug 05, 2013 at 04:31:44PM +0200, Marc Joliet wrote: |
| 3 |
> > Am Mon, 5 Aug 2013 07:59:09 -0500 |
| 4 |
> > |
| 5 |
> > schrieb Bruce Hill <daddy@×××××××××××××××××××××.com>: |
| 6 |
> > > If this is "the new kernel naming scheme of NICs", why this in dmesg: |
| 7 |
> > > |
| 8 |
> > > [ 4.725902] systemd-udevd[1176]: renamed network interface wlan0 to |
| 9 |
> > > enp0s18f2u2 |
| 10 |
> > > |
| 11 |
> > > It looks as if systemd-udev renamed the NIC to me. Can you explain? |
| 12 |
> > |
| 13 |
> > It already has been explained in the previous NIC renaming discussion: |
| 14 |
> > what's broken is renaming a device within the kernels internal |
| 15 |
> > namespace, which contains eth*, wlan* (and maybe others). The problem is |
| 16 |
> > that there is a race condition with the kernel when renaming ethX to |
| 17 |
> > ethY. What you *can* do is rename ethX to somethingelseX or |
| 18 |
> > somethingelseY, because then you are not racing against the kernel to |
| 19 |
> > hand out device names. |
| 20 |
> > |
| 21 |
> > This is explained on the website that also explains the new default |
| 22 |
> > renaming scheme used by udev. I (and IIRC others, too) already linked to |
| 23 |
> > it in in the old |
| 24 |
> > |
| 25 |
> > thread, and the relevant news item also referenced it, but here it is |
| 26 |
again: |
| 27 |
> > http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInte |
| 28 |
> > rfaceNames/ |
| 29 |
> |
| 30 |
> The fact is that udev renamed the NIC. For the average Joe with one NIC |
| 31 |
> (very large percentage of users) this is a non sequitur. For those of us |
| 32 |
> with 2 or more NICs, myself included, we have already setup our systems to |
| 33 |
> use multiple NICs for a purpose and configured the system so that nothing |
| 34 |
> can/will/needs to rename subsequent NICs. |
| 35 |
> |
| 36 |
> My point is don't say "the new kernel naming scheme of NICs", say "the new |
| 37 |
> systemd naming scheme of NICs". |
| 38 |
|
| 39 |
Indeed! Thanks for bringing this to my attention. Here's my eth0: |
| 40 |
|
| 41 |
[ 6.437527] systemd-udevd[1407]: starting version 204 |
| 42 |
[ 7.457924] systemd-udevd[1428]: renamed network interface eth0 to enp11s0 |
| 43 |
|
| 44 |
while my wireless NIC stays named as always was (wlan0): |
| 45 |
|
| 46 |
[ 7.822350] b43-phy0: Broadcom 4312 WLAN found (core revision 15) |
| 47 |
[ 7.838741] b43-phy0: Found PHY: Analog 6, Type 5 (LP), Revision 1 |
| 48 |
[ 7.838760] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, |
| 49 |
Revision 2 |
| 50 |
[ 15.771370] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07) |
| 51 |
[ 15.775217] b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz. |
| 52 |
[ 17.157109] b43-phy0 debug: Chip initialized |
| 53 |
[ 17.157427] b43-phy0 debug: 64-bit DMA initialized |
| 54 |
[ 17.157888] b43-phy0 debug: QoS disabled |
| 55 |
[ 17.167424] b43-phy0 debug: Wireless interface started |
| 56 |
[ 17.172410] b43-phy0 debug: Adding Interface type 2 |
| 57 |
[ 17.173097] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready |
| 58 |
|
| 59 |
|
| 60 |
BTW, I have no systemd installed, only udev-204 and udev-init-scripts-26. |
| 61 |
-- |
| 62 |
Regards, |
| 63 |
Mick |
Archives