not to belabor the obvious, but there are a lot of issues with this
for those who advocate writing some form of signature into an NVM
space on each device that can support it (and using this signature
to appropriately configure the right device), there are obvious
solutions: (1) use a "motherboard serial number" or (2) the infamous
CPU serial number pre-pended to whatever tag for disk/cdrw/etc.
thus, it's easy to know when a device has just been moved within the
same machine, or has been relocated to a new machine. no conflict
will be found.
for those who are willing to take a step back and look at the big
picture, (a) not every device on the planet has a unique key
associated with it as many people keep pointing out; (b) not every
device has some area of "user" (eg, not hardware manufacturer) space
that can be programmed that is NVM. if you have a situation of
BOTH (a) and (b) then you are screwed, period. use an arbitrary
ordering, as there's no other possible choice - and no way to
preserve anything. note that "arbitrary" can just be "sequential
scan of bus + assign based on sequence # found" to get pseudo-logical
ordering *just as easily* as doing "scan bus + randomly assign"
if however you can do either (a) or (b), then the problem is solved.
the more interesting question is: for what class of devices does
neither unique-key or storage-NVM exist? and are they important?
serial ports, for example, are important. if i am monitoring a UPS
on ttyS0 and it suddenly gets remapped on the next boot to ttyS9,
that would be bad. likewise printers and such. but is there any
kind of unique key or trigger that can be found for them?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/