> Perhaps so. It certainly makes sense to do it for metadevices drives,
> since it pretty much eliminates the risk of assembling them in the wrong
> order. But for regular disks it's just an extra hassle, an extra level of
> indirection which buys me very little. Disks tend to move between
> machines, *not* to change scsi id's or controllers on the same machine.
You should work here :-). Anyway, the original point was that the
controller order had changed between 2.0 and 2.1 - so if you boot
between them your disks do move...
> > (I did, however, change scsidev to handle backslashed end of lines
> > and to have an option to generate an initial scsi.alias. I'll dig
> > the changes out and release them sometime if someone reminds me
> > at frequent intervals :-) )
>
> Do you have a fix for the serial number stuff too? :-) I haven't looked
> into it, since I don't use it, but I tried it just now on a couple of
> machines (both 2.0 and 2.1) and scsidev -s prints "(null)" for every
> device. Another thing I fixed a while ago was support for more than 8
> disks -- the stock version wasn't scanning minors > 127.
The serial number stuff works here. I can't remember if I fixed
it or not (it rings a faint bell).
Mike
-- .----------------------------------------------------------------------. | Mike Jagdis | Internet: mailto:mike@roan.co.uk | | Roan Technology Ltd. | | | 54A Peach Street, Wokingham | Telephone: +44 118 989 0403 | | RG40 1XG, ENGLAND | Fax: +44 118 989 1195 | `----------------------------------------------------------------------'
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html