public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Todd Goodman <tsg@bonedaddy.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Ethernet Machination
Date: Wed, 2 Jan 2013 16:18:51 -0500	[thread overview]
Message-ID: <20130102211851.GV6950@ns1.bonedaddy.net> (raw)
In-Reply-To: <loom.20130102T214951-919@post.gmane.org>

* james <wireless@tampabay.rr.com> [130102 16:02]:
[..]
> 
> Well is all works automatically, but udev did not create the
> files I thought it would upon reboot:
> 
> 
> rules.d # ls -alg
> total 12
> drwxr-xr-x 2 root  192 Jan  2 14:37 .
> drwxr-xr-x 4 root  152 Dec  9 23:26 ..
> -rw-r--r-- 1 root 1896 Sep 30 08:13 70-persistent-cd.rules
> -rw-r--r-- 1 root 2652 Aug 20  2010 70-persistent-cd.rules.old
> -rw-r--r-- 1 root  948 Dec  3 03:52 70-persistent-net.rules.31dec2012.old
> 
> After deleting the 70-persistent-net.rule file
> 
> udev does not re-create it. All is now fine with rc-status
> only showing net.eth0 which is set up how I like it
> per /etc/conf.d/net. All services are fine
> 
> 
> Move on, or hand edit the '70-persistent-net.rules' file?
> 
> TIA,
> James

I don't know what version of udev you're running (sorry if I missed it,)
but the udev-186 elog says:

        "Upstream has removed the persistent-net and persistent-cd rules
         generator. If you need persistent names for these devices,
         place udev rules for them in /etc/udev/rules.d."

That doesn't explain why you got the 70-persistent-cd.rules re-created
and not 70-persistent-net.rules, but maybe one of the udev releases I
didn't install and that you're running just stopped recreating the
70-persistent-net.rules file but still re-created the
70-persistent-cd.rules file?

I went from udev-182-r3 to udev-186 it looks like.

Personally if it works without the 70-persistent-net.rules file and you
don't plug and unplug Ethernet interfaces (like with USB dongles) then I
wouldn't create one myself.

Regards,

Todd


  parent reply	other threads:[~2013-01-02 21:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-02  0:50 [gentoo-user] Ethernet Machination James
2013-01-02  0:55 ` Canek Peláez Valdés
2013-01-02 12:53   ` Tanstaafl
2013-01-02 15:24     ` Michael Mol
2013-01-02 15:35       ` Tanstaafl
2013-01-02 15:47         ` Michael Mol
2013-01-02  0:56 ` Mark Knecht
2013-01-02 20:57   ` [gentoo-user] " james
2013-01-02 21:03     ` Bruce Hill
2013-01-02 21:12     ` Mark Knecht
2013-01-02 21:18     ` Todd Goodman [this message]
2013-01-02 22:04     ` Canek Peláez Valdés
2013-01-02 23:10       ` William Kenworthy
2013-01-05 16:03     ` Kerin Millar
2013-01-05 17:45       ` Mark Knecht
2013-01-08  1:46         ` Canek Peláez Valdés

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=20130102211851.GV6950@ns1.bonedaddy.net \
    --to=tsg@bonedaddy.net \
    --cc=gentoo-user@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