> -----Original Message----- > From: Stephen Hemminger [mailto:shemminger@xxxxxxxxxxxxxxxxxxxx] > Sent: Wednesday, January 20, 2010 4:02 AM > To: K, Narendra > Cc: m.innocenti@xxxxxxxxx; jengelh@xxxxxxxxxx; Domsch, Matt; > john.haxby@xxxxxxxxxx; net-tools@xxxxxxxxxxxx; be- > mail2010@xxxxxxxxxxxx; netfilter-devel@xxxxxxxxxxxxxxx; > jgarzik@xxxxxxxxxxxxxxxxxxxxx; Rose, Charles; Iyer, Shyam; Hargrave, > Jordan; Shandilya, Sandeep K > Subject: Re: [PROPOSAL]: Alias names for network interfaces > > On Tue, 19 Jan 2010 23:02:19 +0530 > <Narendra_K@xxxxxxxx> wrote: > > > Sure, but this would again introduce state. And that might not help > in a > > heterogeneous environment. > > Hetrogeneous with what? Other OS's; sorry I don't care what Windows, > Solaris, > HP-UX or anything else uses as a rule. The point is to do the right > thing. Sorry for not being clear. Heterogeneous with different hardware (like Dell, HP etc, I was not referring to OSes, ) and a udev rule like SUBSYSTEM=="net", SUBSYSTEMS=="pci", KERNELS=="0000:04:00.0", NAME="eth0" will not help as 0000:04:00.0 (or any other bus,device,function) might not be a network device in all the systems or it might not exist. A single OS image which has to be installed on multiple systems would have to be more generic than that. 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
