From: Kay Sievers <kay@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: How to avoid renaming of network devices (eth5 to eth0, eth6 to eth1, and so on)
Date: Sun, 16 Sep 2012 16:12:15 +0000 [thread overview]
Message-ID: <CAPXgP11aF=Qpkj-ba8o10SPyK4iOxjQJNGuV3L7-DxE0HurKyQ@mail.gmail.com> (raw)
On Sat, Aug 25, 2012 at 12:33 PM, Kevin Wilson <wkevils@gmail.com> wrote:
> I am using Ubuntu with udev on a Linux machine
>
> From time to time it happens that network devices are renamed after boot,
> and this is due to udev (I know for sure that the reason for this is
> uboot, because if I delete the udev
> network rules file from /etc/udev/rules.d/, and reboot again, this
> renaming does not occur).
>
> What I mean more specifically is this:
> I boot and I have (when running "ifconfig -a") eth0, eth1, eth2, eth3
> (I have 4 network cards).
> sometimes after reboot I get with ""ifconfig -a" " the following :
> eth6, eth7, eth8, eth9
The udev version in systemd does not do any of the automatic the
network rename rules creation in /etc anymore. It creates far more
problems than it solves, so it is all gone in current releases.
In older versions, the rule generator can be "masked" by creating an
empty rules file in /etc/udev/rules.d/ that disables the rules file
/lib/udev/rules.d/ which calls the network rules generator.
Kay
next reply other threads:[~2012-09-16 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-16 16:12 Kay Sievers [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-25 10:33 How to avoid renaming of network devices (eth5 to eth0, eth6 to eth1, and so on) Kevin Wilson
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='CAPXgP11aF=Qpkj-ba8o10SPyK4iOxjQJNGuV3L7-DxE0HurKyQ@mail.gmail.com' \
--to=kay@vrfy.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).