From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Ethernet Machination
Date: Wed, 2 Jan 2013 16:04:06 -0600 [thread overview]
Message-ID: <CADPrc80Ah0J-PjooTiGCSkRtscev8iMQaf+zBCjbfeoRugw_Ug@mail.gmail.com> (raw)
In-Reply-To: <loom.20130102T214951-919@post.gmane.org>
On Wed, Jan 2, 2013 at 2: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.
>
> Yep,
> I did this to see if udev would build the new rules..
>
>> mark <at> c2stable ~ $ ls -al /etc/udev/rules.d/
>> total 24
>> drwxr-xr-x 2 root root 4096 Jan 1 14:40 .
>> drwxr-xr-x 3 root root 4096 Nov 26 17:33 ..
>> -rw-r--r-- 1 root root 0 Nov 26 17:31 .keep_sys-fs_udev-0
>> -rw-r--r-- 1 root root 79 Sep 26 06:19 51-android.rules
>> -rw-r--r-- 1 root root 166 Nov 3 2011 60-ipod.rules
>> -rw-r--r-- 1 root root 1196 May 5 2012 70-persistent-cd.rules
>> -rw-r--r-- 1 root root 627 Nov 26 17:33 70-persistent-net.rules
>
> 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?
I would move on. The idea is that everything "just works".
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
next prev parent reply other threads:[~2013-01-02 22:05 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
2013-01-02 22:04 ` Canek Peláez Valdés [this message]
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=CADPrc80Ah0J-PjooTiGCSkRtscev8iMQaf+zBCjbfeoRugw_Ug@mail.gmail.com \
--to=caneko@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