linux-hotplug.vger.kernel.org archive mirror
 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 07:54:15 +0000	[thread overview]
Message-ID: <4A6968A7.80800@ban-solms.de> (raw)
In-Reply-To: <4A684053.5070403@bio.ifi.lmu.de>

Hi Frank,

>> Did you try removing the persistent net generator rule file? (usually 
>> 75-persistent-net-generator.rules)
>> Don't know where that is located in SLES, might be in /etc/udev/rules.d 
>> or /lib/udev/rules.d
> 
> that would work, yes! But with the next udev update that file would be
> back and if I missed that, the rule files could get created by the
> next "udevadm trigger" call (from whereever). So this is a work-around, 
> but not reliable, clean solution, I guess.

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 also though that removing the 70-persistent-* rules on every boot
> before boot.udev runs would help, but I've least one hosts that still
> creates renamed network devices other than eth0 and eth1 (see my other
> email on the list), so this doesn't help either.

The persistent net generator recreates the persistent-net if it does not 
exist.


Olaf

  parent reply	other threads:[~2009-07-24  7:54 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 [this message]
2009-07-24  8:07 ` Frank Steiner
2009-07-24 10:27 ` Frank Steiner
2009-07-24 10:40 ` Olaf
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=4A6968A7.80800@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).