> -----Original Message----- > From: Marco Innocenti [mailto:m.innocenti@xxxxxxxxx] > Sent: Monday, January 18, 2010 10:37 PM > To: K, Narendra > Cc: jengelh@xxxxxxxxxx; Domsch, Matt; john.haxby@xxxxxxxxxx; net- > tools@xxxxxxxxxxxx; be-mail2010@xxxxxxxxxxxx; shemminger@linux- > foundation.org; netfilter-devel@xxxxxxxxxxxxxxx; > jgarzik@xxxxxxxxxxxxxxxxxxxxx; Rose, Charles; Iyer, Shyam; Hargrave, > Jordan; Shandilya, Sandeep K > Subject: Re: [PROPOSAL]: Alias names for network interfaces > > Narendra_K@xxxxxxxx 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" Sure, but this would again introduce state. And that might not help in a heterogeneous environment. With regards, Narendra K -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
