From: Marco Innocenti <m.innocenti@cineca.it>
To: Narendra_K@Dell.com
Cc: jengelh@medozas.de, Matt_Domsch@Dell.com, john.haxby@oracle.com,
net-tools@lina.inka.de, be-mail2010@lina.inka.de,
shemminger@linux-foundation.org, netfilter-devel@vger.kernel.org,
jgarzik@users.sourceforge.net, Charles_Rose@Dell.com,
Shyam_Iyer@Dell.com, Jordan_Hargrave@Dell.com,
Sandeep_K_Shandilya@Dell.com
Subject: Re: [PROPOSAL]: Alias names for network interfaces
Date: Mon, 18 Jan 2010 18:07:21 +0100 (MET) [thread overview]
Message-ID: <4B54953D.5030005@cineca.it> (raw)
In-Reply-To: <EDA0A4495861324DA2618B4C45DCB3EE5899F1@blrx3m08.blr.amer.dell.com>
Narendra_K@Dell.com wrote:
> Also, in case of large scale image based deployment scenarios embedding
> HWADDR in config files or udev rules is not an option. Though HWADDR
> helps in
> ensuring persistency in naming, it doesn't help in achieving expected
> naming.
HWADDR is not the only way to use udev to name a network interface. You
can do something like:
SUBSYSTEM=="net", SUBSYSTEMS=="pci", KERNELS=="0000:04:00.0", NAME="eth0"
SUBSYSTEM=="net", SUBSYSTEMS=="pci", KERNELS=="0000:06:00.0", NAME="eth1"
>
--
**********************************************************************
Marco Innocenti Dipartimento Sistemi E Tecnologie
CINECA phone:+39 0516171553 / fax:+39 0516132198
Via Magnanelli 6/3 e-mail: innocenti@cineca.it
40033 Casalecchio di Reno Bologna (Italia)
**********************************************************************
next prev parent reply other threads:[~2010-01-18 17:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EDA0A4495861324DA2618B4C45DCB3EE5899AC@blrx3m08.blr.amer.dell.com>
2010-01-12 19:49 ` Re:[PROPOSAL]: Alias names for network interfaces Narendra K
2010-01-13 0:11 ` Jan Engelhardt
2010-01-13 6:47 ` [PROPOSAL]: " Narendra_K
2010-01-13 11:04 ` Bernd Eckenfels
2010-01-13 17:22 ` John Haxby
2010-01-13 17:46 ` Domsch, Matt
2010-01-13 18:11 ` Bernd Eckenfels
2010-01-13 18:21 ` Jan Engelhardt
2010-01-14 8:44 ` Patrick McHardy
2010-01-14 9:35 ` Jan Engelhardt
2010-01-15 19:14 ` Narendra_K
2010-01-18 17:07 ` Marco Innocenti [this message]
2010-01-19 17:32 ` Narendra_K
2010-01-19 22:31 ` Stephen Hemminger
2010-01-20 1:02 ` Bernd Eckenfels
2010-01-20 16:42 ` Narendra_K
2010-01-13 17:54 ` Stephen Hemminger
2010-01-13 13:24 ` Patrick McHardy
2010-01-13 13:43 ` Jan Engelhardt
2010-01-13 16:27 ` Stephen Hemminger
2010-01-13 17:00 ` Narendra_K
2010-01-14 8:41 ` Patrick McHardy
2009-12-17 13:54 Narendra_K
2009-12-17 14:48 ` Jan Engelhardt
2009-12-18 2:02 ` Bernd Eckenfels
2009-12-18 13:19 ` Narendra_K
2009-12-18 13:42 ` Jan Engelhardt
2009-12-18 14:02 ` Domsch, Matt
2009-12-18 14:08 ` Domsch, Matt
2009-12-18 14:15 ` Jan Engelhardt
2009-12-20 0:12 ` Jordan_Hargrave
2009-12-18 17:38 ` Stephen Hemminger
2009-12-21 17:28 ` Narendra_K
2009-12-21 17:36 ` Stephen Hemminger
2009-12-23 17:11 ` Narendra_K
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=4B54953D.5030005@cineca.it \
--to=m.innocenti@cineca.it \
--cc=Charles_Rose@Dell.com \
--cc=Jordan_Hargrave@Dell.com \
--cc=Matt_Domsch@Dell.com \
--cc=Narendra_K@Dell.com \
--cc=Sandeep_K_Shandilya@Dell.com \
--cc=Shyam_Iyer@Dell.com \
--cc=be-mail2010@lina.inka.de \
--cc=jengelh@medozas.de \
--cc=jgarzik@users.sourceforge.net \
--cc=john.haxby@oracle.com \
--cc=net-tools@lina.inka.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=shemminger@linux-foundation.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.