From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#627931: /etc/udev/rules.d/70-persistent-net.rules not
Date: Thu, 26 May 2011 13:16:43 +0000 [thread overview]
Message-ID: <20110526131643.GA8724@bongo.bofh.it> (raw)
In-Reply-To: <20110525180115.GA15695@bongo.bofh.it>
On May 25, Kay Sievers <kay.sievers@vrfy.org> wrote:
> We can not rename network devices in the kernel namespace (ethX)
> reliably. It's impossible to get right to rename in a conflicting
> namespace while kernel modules are loaded.
Can you tell me more about this? Because it worked well enough for the
last last 5 years.
> The whole thing does not scale with a lot of interfaces or on boxes
> with many changes. The rules file just gets full of garbage over time.
True, but these are corner cases.
> Only one thing seems sure for now, that udev must stop renaming things
> in the kernel namespace. The details for the rest we will need to find
> out. :)
Maybe you can get away with removing features, but I need to support the
ones used by my users so I am strongly opposed to removing this code
until other software will support all current use cases.
As you showed, distributions which do not feel like supporting it can
just disable it.
--
ciao,
Marco
next prev parent reply other threads:[~2011-05-26 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 18:01 Bug#627931: /etc/udev/rules.d/70-persistent-net.rules not generated Marco d'Itri
2011-05-25 18:42 ` Bug#627931: /etc/udev/rules.d/70-persistent-net.rules not Kay Sievers
2011-05-26 7:12 ` Greg KH
2011-05-26 11:59 ` Kay Sievers
2011-05-26 13:16 ` Marco d'Itri [this message]
2011-05-26 14:44 ` Kay Sievers
2011-05-27 1:26 ` Marco d'Itri
2011-05-27 1:52 ` Kay Sievers
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=20110526131643.GA8724@bongo.bofh.it \
--to=md@linux.it \
--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).