My experience managing large Solaris systems (which use
controller-target-LUN device naming) has led me to believe this sort
of stuff is fundamentally bogus, *especially* when there are multiple
cards involved. You will simply tend to move the stuff around too
often. The resulting problem is similar to the problem with DOS drive
letters.
My belief is that the only reasonable solution is to permit the user
to control the scanning order (including allowing gaps). The *ideal*
would be to let the user afiliate arbitrary device names which
arbitrary controller-target-LUN tuplets, but if at least the
controller scanning order is determined we're remotely OK.
I do *not* agree that the ISA/EISA/PnP/PCI bus identifier should be
encoded -- it is simply too hardware dependent.
That being said, as the Linux Device Registrar I strongly advice that
2.1 *must* be the time to increase the size of dev_t to a mininum of
32 bit; I personally advocate 64 bit with support for sparse
allocation of major numbers.
-hpa
--=20
PGP public key available - finger hpa@zytor.com
I don't work for Yggdrasil, but they sponsor the linux.* hierarchy.
"The earth is but one country, and mankind its citizens." -- Bah=E1'u=
'll=E1h
Just Say No to Morden * Save Babylon 5: http://www.babylon5.com/cmp/sup=
port/