I created a small scsiorder patch to solve this by fixing the problem
where it originates. For example the kernel parameter
"scsi_scanorder=1,10,6" means to scan the devices in the following
order: 1,10,6,0,2,3,4,5,7,8,9,11,12,13,15. Which means SCSI-id's 1,10,6
and 0 will allways be mapped on sda, sdb, sdc en sdd (if all connected).
More info: http://flits102-126.flits.rug.nl/~rolf/scanorder/index.html
There's a small description of the alternatives like devfs and scsidev
as well.
cheers!
Rolf.
:.˛mkabzwmb˛mbz_^nrzh&zvy杶ii