All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf <mailinglists@ban-solms.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: How to disable persistent network device names?
Date: Fri, 24 Jul 2009 10:40:27 +0000	[thread overview]
Message-ID: <4A698F9B.2020402@ban-solms.de> (raw)
In-Reply-To: <4A684053.5070403@bio.ifi.lmu.de>

Hi Frank,

> Olaf wrote
> 
>> OK, in that case you could create your own rule to bypass the net-generator.
>>
>> Put something like this in 69-bypass-persistent-net.rules:
>> SUBSYSTEM="net", ACTION="add", NAME="%k"
> 
> I tried this, with and without removing the 70-persistent-net.rules,
> but still my test host comes up with eth_s2_0 and eth_s2_1, so the
> kernel must tell udev those names.
> 
> But in /var/log/boot.msg I find this (quoting only about eth0 here):
> 
> <6>e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
> ...
> <6>eth0 renamed to eth_s2_0 by udevd [274]
> <6>udev: renamed network interface eth0 to eth_s2_0
> 
> So udev must have some other rule telling it to rename those devices.
> After I have removed 70-persistent-net.rules (and it is not re-created
> when rebooting) I don't know where this could come from :-(
> Do you have any idea?

Could be something from the SLES initramfs?
I don't have/use SLES so I really don't know where the rename to 
eth_s2_* comes from, sorry.



Olaf

  parent reply	other threads:[~2009-07-24 10:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23 10:49 How to disable persistent network device names? Frank Steiner
2009-07-23 15:56 ` Karl O. Pinc
2009-07-24  6:37 ` Frank Steiner
2009-07-24  6:50 ` Olaf
2009-07-24  7:08 ` Frank Steiner
2009-07-24  7:54 ` Olaf
2009-07-24  8:07 ` Frank Steiner
2009-07-24 10:27 ` Frank Steiner
2009-07-24 10:40 ` Olaf [this message]
2009-07-24 10:46 ` Frank Steiner
2009-07-24 11:54 ` Frank Steiner

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=4A698F9B.2020402@ban-solms.de \
    --to=mailinglists@ban-solms.de \
    --cc=linux-hotplug@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.