> >cCbBtTdDsS
> >
> ><C> == controller
> ><B> == bus/channel on controller
> ><T> == target (ID)
> ><D> == LUN
> ><S> == slice/partition
>
> An would happen to work perfectly well with things like the way I do device
> error messages in my aic7xxx patch. The prefix for messages is:
>
> (scsi%d:%d:%d:%d) where the four values are host # (controller), channel #,
> target #, and lun #. Then you only add the slice to that to know exactly
> which dev file points to that device.
Well, I do not like to be devices called like c0b0t0d0s1.
I think that scsi0.0.0.0.1 would be much more acceptable. Really,
those letters are for nothing, just one more thing to remember. If you
maintain logical order (and this is logical), you do not need ugly
letters in between.
-- I'm really pavel@atrey.karlin.mff.cuni.cz. Pavel Look at http://atrey.karlin.mff.cuni.cz/~pavel/ ;-).