From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-146474-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 782C6138010
for <garchives@archives.gentoo.org>; Wed, 3 Apr 2013 19:46:52 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 738A1E09D4;
Wed, 3 Apr 2013 19:46:42 +0000 (UTC)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195])
(using TLSv1 with cipher RC4-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 13882E08F4
for <gentoo-user@lists.gentoo.org>; Wed, 3 Apr 2013 19:46:40 +0000 (UTC)
Received: from localhost (66-208-231-133.ubr01a.rte20201.pa.hfc.comcastbusiness.net [66.208.231.133])
by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis)
id 0M6B3i-1UYywR46WY-00yIpw; Wed, 03 Apr 2013 15:46:39 -0400
Date: Wed, 3 Apr 2013 14:46:37 -0500
From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Udev update and persistent net rules changes
Message-ID: <20130403194637.GE9673@server>
References: <CAEH5T2PTjSx7Gd_y4g03vvqwFKFgNxia2t7ai5uG0Km=DPfEbg@mail.gmail.com>
<515B2FA1.9090805@gmail.com>
<515B3461.7080603@libertytrek.org>
<515B387A.4020002@gmail.com>
<kjff6e$akg$1@ger.gmane.org>
<20130402223624.71e26ab0@digimed.co.uk>
<kjhgu7$aqv$1@ger.gmane.org>
<20130403163529.07d97a07@digimed.co.uk>
<kjhlu4$p11$1@ger.gmane.org>
<kjhr2p$34l$1@ger.gmane.org>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <kjhr2p$34l$1@ger.gmane.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Provags-ID: V02:K0:a1KShbh3/ePjzRS1l55Y87Lv2HlO0rgYip2cEcCZBg9
w3sFjmYT9zMdtbVTSygsuUOrTf4qG4aw91Le4SBLRVWCsFRPN/
VBBbTGXmQLaqNBk0v/C7zlLidK/+mF4utLnpimXFQG72GR0xUE
hcuGTSK0DmkKISkNtVW7eq32C9AUjLI1qv+rRTn7XmD3pw1OZl
0xDhjNgy31vXXrANJmvKMheYlAw0oTN5/xoCRA7psDc3ijqhgV
Oqtih3uhp6hU/w9Q3jH26WweV7r5uxCQUvlAAxg8KiLwcFDMJE
9CrtR5ZsKXJqpS1A6erB+6fbOzi+eH9xgHRep+mSz/bsy4dE6E
yDCkKRrU1dAzmOgp/8dk=
X-Archives-Salt: 0aeccef9-5092-4850-81a0-17ea1c3fb5f1
X-Archives-Hash: bf79aef1009c76febe74442e17103bcd
On Wed, Apr 03, 2013 at 08:06:20PM +0200, Jörg Schaible wrote:
> Hi,
>
> Grant Edwards wrote:
>
> > On 2013-04-03, Neil Bothwick <neil@digimed.co.uk> wrote:
> >
> >> Have you read the news item?
> >
> > Yes. I found it rather confusing.
> >
> > It refers to a "new format" for rules, but the examples use the exact
> > same format as the old rules.
> >
> > It talks about how 80-net-name-slot.rules needs to be either an empty
> > file or a synmlink to /dev/null if you want to disable the new naming
> > scheme -- but that doesn't seem to be right. After the upgrade my
> > 80-net-name-slot.rules file was neither an empty file nor a symlink to
> > /dev/null, but I'm still getting the same old names.
>
> same for me. I followed the upgrade guide and removed any 70-* files,
> renamed the net.eth0 link to the new scheme net.enp0s1 just to to find out
> that the kernel could not bring up a network with the such a device. The
> machine booted fine after using eth0 instead again. One a second machine I
> kept eth0 immediately and it booted without problems afterwards.
>
> >> It explains why the file should be renamed and also why you should
> >> change the names in the rules to not use ethN.
> >
> > The only explanation I found was "the old way is now deprecated".
>
> And the new name simply did not work.
>
> - Jörg
When the news item is too convoluted to understand without writing it on
paper, and doing a diagram of my LAN, I just get out the USB SystemRescueCD
and have it ready on first reboot. So far I've just sailed along as it's been
since before last March or so when WilliamH first put out the news item about
udev about to fubar the universe. I'd not wanted to go to or past udev-181,
but kerframil told me to stop being scared and upgrade to stable, so I did.
And here are the results, just upgrading, not changing ANY file:
mingdao@router ~ $ less /etc/udev/rules.d/80-net-name-slot.rules
/etc/udev/rules.d/80-net-name-slot.rules: No such file or directory
mingdao@router ~ $ eix sys-fs/udev
[I] sys-fs/udev
Available versions: [M]171-r10 197-r8^t ~198-r6^t ~199-r1^t 200^t **9999^t {{acl action_modeswitch build debug doc edd extras +firmware-loader floppy gudev hwdb introspection keymap +kmod +openrc +rule_generator selinux static-libs test}}
Installed versions: 200^t(05:01:58 PM 04/02/2013)(acl firmware-loader kmod openrc -doc -gudev -hwdb -introspection -keymap -selinux -static-libs)
Homepage: http://www.freedesktop.org/wiki/Software/systemd
Description: Linux dynamic and persistent device naming support (aka userspace devfs)
[I] sys-fs/udev-init-scripts
Available versions: 23^t ~24^t 25^t **9999^t
Installed versions: 25^t(05:02:08 PM 04/02/2013)
Homepage: http://www.gentoo.org
Description: udev startup scripts for openrc
Found 2 matches.
mingdao@router ~ $ cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x8086:0x10d3 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="68:05:ca:03:05:5d", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x8086:0x10d3 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="68:05:ca:03:05:50", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="f4:6d:04:e8:1d:d9", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
mingdao@server ~ $ less /etc/udev/rules.d/80-net-name-slot.rules
/etc/udev/rules.d/80-net-name-slot.rules: No such file or directory
mingdao@server ~ $ eix sys-fs/udev
[I] sys-fs/udev
Available versions: [M]171-r10 197-r8^t ~198-r6^t ~199-r1^t 200^t **9999^t {{acl action_modeswitch build debug doc edd extras +firmware-loader floppy gudev hwdb introspection keymap +kmod +openrc +rule_generator selinux static-libs test}}
Installed versions: 200^t(06:01:45 PM 04/02/2013)(acl firmware-loader kmod openrc -doc -gudev -hwdb -introspection -keymap -selinux -static-libs)
Homepage: http://www.freedesktop.org/wiki/Software/systemd
Description: Linux dynamic and persistent device naming support (aka userspace devfs)
[I] sys-fs/udev-init-scripts
Available versions: 23^t ~24^t 25^t **9999^t
Installed versions: 25^t(06:01:58 PM 04/02/2013)
Homepage: http://www.gentoo.org
Description: udev startup scripts for openrc
Found 2 matches.
mingdao@server ~ $ cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x14e4:0x1659 (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:d0:68:0b:87:66", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
# PCI device 0x14e4:0x1659 (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:d0:68:0b:87:67", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
mingdao@workstation ~ $ less /etc/udev/rules.d/80-net-name-slot.rules
/etc/udev/rules.d/80-net-name-slot.rules: No such file or directory
mingdao@workstation ~ $ eix sys-fs/udev
[I] sys-fs/udev
Available versions: [M]171-r10 197-r8^t ~198-r6^t ~199-r1^t 200^t **9999^t {{acl action_modeswitch build debug doc edd extras +firmware-loader floppy gudev hwdb introspection keymap +kmod +openrc +rule_generator selinux static-libs test}}
Installed versions: 200^t(05:35:34 PM 04/02/2013)(firmware-loader gudev kmod openrc -acl -doc -hwdb -introspection -keymap -selinux -static-libs)
Homepage: http://www.freedesktop.org/wiki/Software/systemd
Description: Linux dynamic and persistent device naming support (aka userspace devfs)
[I] sys-fs/udev-init-scripts
Available versions: 23^t ~24^t 25^t **9999^t
Installed versions: 25^t(05:35:12 PM 04/02/2013)
Homepage: http://www.gentoo.org
Description: udev startup scripts for openrc
Found 2 matches.
mingdao@workstation ~ $ cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x8086:0x10d3 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:21:b8:e2:f8", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="f4:6d:04:d2:6b:be", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
mingdao@router ~ $ less /etc/udev/rules.d/80-net-name-slot.rules
/etc/udev/rules.d/80-net-name-slot.rules: No such file or directory
mingdao@router ~ $ eix sys-fs/udev
[I] sys-fs/udev
Available versions: [M]171-r10 197-r8^t ~198-r6^t ~199-r1^t 200^t **9999^t {{acl action_modeswitch build debug doc edd extras +firmware-loader floppy gudev hwdb introspection keymap +kmod +openrc +rule_generator selinux static-libs test}}
Installed versions: 200^t(05:01:58 PM 04/02/2013)(acl firmware-loader kmod openrc -doc -gudev -hwdb -introspection -keymap -selinux -static-libs)
Homepage: http://www.freedesktop.org/wiki/Software/systemd
Description: Linux dynamic and persistent device naming support (aka userspace devfs)
[I] sys-fs/udev-init-scripts
Available versions: 23^t ~24^t 25^t **9999^t
Installed versions: 25^t(05:02:08 PM 04/02/2013)
Homepage: http://www.gentoo.org
Description: udev startup scripts for openrc
Found 2 matches.
mingdao@router ~ $ cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x8086:0x10d3 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="68:05:ca:03:05:5d", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x8086:0x10d3 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="68:05:ca:03:05:50", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="f4:6d:04:e8:1d:d9", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
mingdao@peter ~ $ less /etc/udev/rules.d/80-net-name-slot.rules
/etc/udev/rules.d/80-net-name-slot.rules: No such file or directory
mingdao@peter ~ $ eix sys-fs/udev
[I] sys-fs/udev
Available versions: [M]171-r10 197-r8^t ~198-r6^t ~199-r1^t 200^t **9999^t {{acl action_modeswitch build debug doc edd extras +firmware-loader floppy gudev hwdb introspection keymap +kmod +openrc +rule_generator selinux static-libs test}}
Installed versions: 200^t(11:35:07 AM 04/01/2013)(firmware-loader kmod openrc -acl -doc -gudev -hwdb -introspection -keymap -selinux -static-libs)
Homepage: http://www.freedesktop.org/wiki/Software/systemd
Description: Linux dynamic and persistent device naming support (aka userspace devfs)
[I] sys-fs/udev-init-scripts
Available versions: 23^t ~24^t 25^t **9999^t
Installed versions: 25^t(11:34:23 AM 04/01/2013)
Homepage: http://www.gentoo.org
Description: udev startup scripts for openrc
Found 2 matches.
mingdao@peter ~ $ cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="bc:ae:c5:6c:3c:97", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
Therefore, all's well that's still working! And AFAIR, on at least 2 of those
machines, the 70-persistent-net.rules was never something I did manually.
I've grown weary of the poor Linux desktop(s), so these are the only 5
computers left on the LAN running Gentoo. Two laptops and two PCs that were
for desktop type computers only have been migrated to Windows 7. I really hate
it, but at least now everything desktop environment wise just works, and does
not either (a) get messed up by updates, or (b) require a lot of work to get
it to work properly to start with, or keep it working.
Cheers,
Bruce
--
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