From: "Walter Dnes" <waltdnes@waltdnes.org>
To: eudev list <eudev@lists.gentoo.org>
Subject: [eudev] Can 70-persistent-net.rules be optional?
Date: Sun, 16 Dec 2012 16:04:33 -0500 [thread overview]
Message-ID: <20121216210433.GA10672@waltdnes.org> (raw)
I'm not a C programmer, but I do have a laptop I can use for beta
testing.
Regarding Richard Yao's statement about 70-persistent-net.rules; I can
see both sides of the issue, and some people are better off with and
some are better off without.
* In the Gentoo user forum, one item that achieved FAQ-level notoriety
was people who had installed a new network card complaining that it
didn't work in Gentoo when it worked fine in Windows. The smarter ones
would run ifconfig and notice that they had eth0 and eth1. They were
told to delete 70-persistent-net.rules, and they got their eth0 back.
Since the machines came up fine without 70-persistent-net.rules, and
70-persistent-net.rules seemed to be the cause of a lot of traffic on
the forum, many people probably submitted feature requests asking for
the removal of 70-persistent-net.rules, leading to its removal.
* The other side of the issue has people who have multi-card setups and
need things to come up in the same configuration the same every time.
Here's a compromise idea that should satisfy both groups... have eudev
read and implement 70-persistent-net.rules, if it exists, just like it
did in the past. But turn off the ability to *CREATE* a
70-persistent-net.rules file. Have a separate script or binary run
manually by the admin to create it. This way, the admins with
multi-card machines get their persistent rules, and users who don't
want/need it won't trip over it.
--
Walter Dnes <waltdnes@waltdnes.org>
next reply other threads:[~2012-12-16 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 21:04 Walter Dnes [this message]
2012-12-17 2:06 ` [eudev] Can 70-persistent-net.rules be optional? Ian Stakenvicius
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=20121216210433.GA10672@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=eudev@lists.gentoo.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