public inbox for eudev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Stakenvicius <axs@gentoo.org>
To: eudev@lists.gentoo.org
Subject: Re: [eudev] Can 70-persistent-net.rules be optional?
Date: Sun, 16 Dec 2012 21:06:32 -0500	[thread overview]
Message-ID: <50CE7E28.1080602@gentoo.org> (raw)
In-Reply-To: <20121216210433.GA10672@waltdnes.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 16/12/12 04:04 PM, Walter Dnes wrote:
> 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.

Yes, it will be optional.  Udev-171 had:

(A) persistent-net-generator.rules (and their helpers) installed only
via USE='rule-generator' (ie, --with-rule-generator), which is how I
plan to manage it in eudev as well; and

(B) there was a way in udev.conf to disable (or actually skip)
generation of persistent-net.rules -- this was handled in the init
scripts and so I am unsure if it will be put back, but if the
sys-fs/udev maintainers see no issues with this code being put back
into the init scripts then we will ensure that works as well.

Since the USE flag will be off by default I expect the majority of
users will end up with the functionality they seem to want, which is
that nothing will create the persistent-net.rules but they can do so
by hand.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlDOfigACgkQ2ugaI38ACPC1owD/ZdhdqRXThl9RKZORhFtpyqCt
2h9/kV6TNHCTZ0jGd3gBAKocEC4xCds0Pit1+XB9yJh2zI50NIrKq0ahiLwhleMp
=cTyP
-----END PGP SIGNATURE-----


      reply	other threads:[~2012-12-17  2:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-16 21:04 [eudev] Can 70-persistent-net.rules be optional? Walter Dnes
2012-12-17  2:06 ` Ian Stakenvicius [this message]

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=50CE7E28.1080602@gentoo.org \
    --to=axs@gentoo.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