public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: Ethernet Machination
Date: Wed, 2 Jan 2013 13:12:52 -0800	[thread overview]
Message-ID: <CAK2H+ec0Niu8QX-f+8N6J2LJzkcx2kg940QSmW8fAD0V3_EU7Q@mail.gmail.com> (raw)
In-Reply-To: <loom.20130102T214951-919@post.gmane.org>

On Wed, Jan 2, 2013 at 12:57 PM, james <wireless@tampabay.rr.com> wrote:
> Mark Knecht <markknecht <at> gmail.com> writes:
>
>
>> > So now that only one ethernet shows up, how do I prevent
>> > udev from renaming eth0 to eth3?
>
>> Probably remove any net-persistent rules that are hanging around. That
>> should free up udev to do more of what you suspect.
>
<SNIP>
>
> 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
>
>
>

Well, I think I'd hand edit myself. That's what I've done in the past.
As Bruce say, dispatch-conf (or etc-update is what I use) might pick
something up if it's waiting, but looking at the comments in my file I
don't think so:

mark@c2stable ~ $ cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib64/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x11ab:0x4364 (sky2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="e0:cb:4e:97:80:fd", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x11ab:0x4364 (sky2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="e0:cb:4e:97:7a:09", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
mark@c2stable ~ $

Really, as long as you don't mess up the format it's really just a
matter of matching the macID. Save your old file in a copy somewhere
and then edit and make it work. ifconfig will show you the macID.

I, like so many others I think, really don't understand how udev
manages all this stuff. I'm really not sure udev knows how udev
works...

HTH,
Mark


  parent reply	other threads:[~2013-01-02 21:14 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 [this message]
2013-01-02 21:18     ` Todd Goodman
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=CAK2H+ec0Niu8QX-f+8N6J2LJzkcx2kg940QSmW8fAD0V3_EU7Q@mail.gmail.com \
    --to=markknecht@gmail.com \
    --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