Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
Problem is, from reading other posts, the system won't boot until after the order is fixed ... the *install* CD needs to know which port is which so the box can find the screen/keyboard to let the administrator in.
Domsch: Consistent Network Device Naming coming to Fedora 15
Posted Jan 28, 2011 1:46 UTC (Fri) by hmh (subscriber, #3838)
When changing a NIC requires updating a config file for a given operating system, this IS known beforehand, and it IS written in the hardware config change checklist. It may be annoying, but it doesn't result on servers that don't boot.
So no, whatever this is about, it is certainly not about datacenters, and certainly not about first boot (when keying to MAC doesn't hurt).
Keying to PCI slots is actually less troublesome when a NIC needs to be replaced, but that does assume the user will not shuffle PCI boards around. Datacenters don't, but they don't actually need this whole stuff, anyway. Desktop users do shuffle boards around, and I am not sure what happens in a small shop with a few servers, and a single junior sysadmin.
It will also subject people to the usual negligence and incompetence found on desktop BIOS teams. You *WILL* get desktop boards with "To Be Filled By OEM" in the slot names, or with repeated slot names, or with control characters inside of ASCII in the slot names, etc. I sure hope that biosdevname tool is extremely paranoid and has a fallback to do something smart when it comes across such insanity.
Posted Jan 28, 2011 12:57 UTC (Fri) by nix (subscriber, #2304)
It is generally a mistake to trust system assemblers to get *anything* right that isn't needed to boot Windows with the absolute minimum set of drivers installed. Half the time they can't even get the right amount of RAM installed: what's the likelihood that they'll name network interfaces correctly in obscure BIOS tables?
(Some BIOSes aren't that bad, if the BIOS is something that comes *with* a specific peripheral and is made by the manufacturer of that peripheral. e.g. AtomBIOS on ATI cards. For anything else, the BIOS is liable to be rife with bugs, but even then less rife than the parts of BIOSes meant to be filled out by system assemblers.)
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds