From: Florian Weimer <fweimer@bfk.de>
To: "Loke\, Chetan" <Chetan.Loke@netscout.com>
Cc: "Matt Domsch" <Matt_Domsch@dell.com>,
"Michael Di Domenico" <mdidomenico4@gmail.com>,
<linux-net@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: nic enumeration
Date: Fri, 09 Jul 2010 07:18:25 +0000 [thread overview]
Message-ID: <82tyo9i0n2.fsf@mid.bfk.de> (raw)
In-Reply-To: <D3F292ADF945FB49B35E96C94C2061B90C317EA2@nsmail.netscout.com> (Chetan Loke's message of "Thu\, 8 Jul 2010 16\:36\:18 -0400")
* Chetan Loke:
>> And on a system where you can use udev rules, the
>> 70-persistent-net.rules file can be used to make them constant, by
>> using the MAC address to force the names to be what you want.
>>
>
> Ok, but can we achieve the renaming w/o a reboot?
"udev-trigger" or "udevadm trigger" works for renaming network
interfaces. The kernel has some restrictions on renaming interfaces
which are in use, so this might not work in your case.
--
Florian Weimer <fweimer@bfk.de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
next prev parent reply other threads:[~2010-07-09 7:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 22:25 nic enumeration Michael Di Domenico
2010-07-07 22:39 ` Brian Kroth
2010-07-07 23:15 ` Steve Fink
2010-07-08 1:21 ` Matt Domsch
2010-07-08 20:36 ` Loke, Chetan
2010-07-08 20:47 ` Andrew Fong
2010-07-08 21:27 ` Kay Sievers
2010-07-08 22:07 ` Loke, Chetan
2010-07-08 21:24 ` Charlie Brady
2010-07-09 7:18 ` Florian Weimer [this message]
2010-07-09 7:57 ` Kay Sievers
2010-07-09 8:13 ` Florian Weimer
2010-07-09 16:27 ` Loke, Chetan
2010-07-09 17:10 ` Steve Fink
2010-07-09 18:23 ` Loke, Chetan
2010-07-09 21:26 ` Steve Fink
2010-07-12 16:56 ` Loke, Chetan
2010-07-12 18:27 ` Steve Fink
2010-07-09 17:15 ` Matt Domsch
2010-07-09 18:55 ` Loke, Chetan
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=82tyo9i0n2.fsf@mid.bfk.de \
--to=fweimer@bfk.de \
--cc=Chetan.Loke@netscout.com \
--cc=Matt_Domsch@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=mdidomenico4@gmail.com \
/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.