On Apr 7, 2013 3:56 PM, "Stroller" <[email protected]> wrote: > > > On 7 April 2013, at 07:00, Joseph wrote: > > ... > > Are these new udev rules going across all Linux distros or this is something specific to Gentoo? > > I would assume across all distros. > > Gentoo generally makes a policy of just packaging whatever upstream offers. In fact, the origins of the ebuild is that it does little more than automating the `configure && make && make install` of compiling upsteam's source. > > I don't see why the Gentoo devs would impose this on us, unless it came from upstream. > > AIUI the motive for these changes are so that you can unpack an enterprise-type server, the ones with two NICs on the motherboard, and always know which NIC is which. You can then unpack a pallet load of them, and deploy them without any need for determining which is which or for any manual intervention. This is actually pretty important and useful, but I'm not sure this has all been done the best way. > > Stroller. >
AFAICT, on-board NICs have sequential MAC Adresses, with the one labeled "Port 1" has the smallest MAC Address. So far, *all* Linux distros I've used on a server will reliably name "Port X" as "eth$((X-1))". So it's never a puzzle as to which port bears which "ethX" moniker. The new naming scheme, however, is much less intuitive. Where originally I just immediately use eth0, now I have to enumerate the monikers first, because even between servers of the same model (let's say, HP's DL360 G7), the PCI attachment point might differ. Granted, Linux SysAdmins *are* expected to understand the vagaries of Linux, but it's still a great inconvenience. Rgds, --
