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 06:50:40 +0000 [thread overview]
Message-ID: <4A6959C0.3010508@ban-solms.de> (raw)
In-Reply-To: <4A684053.5070403@bio.ifi.lmu.de>
Frank Steiner wrote:
> Hi,
> after switching from SLES 10 to 11 I saw that I couldn't use
> FORCE_PERSISTENT_NAMES=no anymore.
>
> How can we prevent persistent network device names? There are some
> problems with this:
>
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
Olaf
next prev parent reply other threads:[~2009-07-24 6:50 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 [this message]
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
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=4A6959C0.3010508@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).