From: Frank Steiner <fsteiner-mail1@bio.ifi.lmu.de>
To: linux-hotplug@vger.kernel.org
Subject: How to disable persistent network device names?
Date: Thu, 23 Jul 2009 10:49:55 +0000 [thread overview]
Message-ID: <4A684053.5070403@bio.ifi.lmu.de> (raw)
Hi,
after switching from SLES 10 to 11 I saw that I couldn't use
FORCE_PERSISTENT_NAMES=no anymore.
How can we prevent persistent network device names? There are some
problems with this:
1) If 70-persistent-net.rules is removed, it is recreated with totally
strange values. E.g. I have file with
SUBSYSTEM="net", ACTION="add", DRIVERS="?*", ATTR{address}="00:1b:21:0e:3e:68", ATTR{type}="1", KERNEL="eth*", NAME="eth0"
Now I remove the file (we have a diskless environment where those files
can get removed due to a local disk change) and call "udevadm trigger".
The new 70-persistent-net.rules now contains:
SUBSYSTEM="net", ACTION="add", DRIVERS="?*", ATTR{address}="00:1b:21:0e:3e:68", ATTR{type}="1", KERNEL="eth*", NAME="eth_s6_0"
Different on every host, sometimes eth_s1_0 etc.
So on the next reboot I have no network, because our config files
are always ifcfg-eth0 (and additionally sometimes ifcfg-eth1).
2) When a mainboard is exchanged, the MACs change. But on the next boot
I still want the new NICs to be eth0 and eth1, in the order
in which they are recognized by the bios.
It doesn't make sense if those new cards become eth2 and eth3
because the old, non-existing NICs are listed in the rules file with
their MACs.
So how can we prevent this? Why was the FORCE_PERSISTENT_NAMES option removed?
Persistent device names might be nice for laptops with wlan or usb network devices.
For our site with 120 PCs and Servers with it's bad because I can't care about 120
rules file to make sure they all are always ok before the next boot. I just want to
get rid of the feature :-)
cu,
Frank
--
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
next reply other threads:[~2009-07-23 10:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 10:49 Frank Steiner [this message]
2009-07-23 15:56 ` How to disable persistent network device names? Karl O. Pinc
2009-07-24 6:37 ` Frank Steiner
2009-07-24 6:50 ` Olaf
2009-07-24 7:08 ` Frank Steiner
2009-07-24 7:54 ` Olaf
2009-07-24 8:07 ` Frank Steiner
2009-07-24 10:27 ` Frank Steiner
2009-07-24 10:40 ` Olaf
2009-07-24 10:46 ` Frank Steiner
2009-07-24 11:54 ` Frank Steiner
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=4A684053.5070403@bio.ifi.lmu.de \
--to=fsteiner-mail1@bio.ifi.lmu.de \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).