Re: Accessing disks via their serial numbers.

Quoting "M. Warner Losh" <imp@xxxxxxxxxx> (from Sun, 25 Jun 2006 17:48:38 -0600 (MDT)):

In message: <20060624174331.GB2134@xxxxxxxxxxxxxxxxx>
Pawel Jakub Dawidek <pjd@xxxxxxxxxxx> writes:
: I'd like to extend glabel(8) to create providers related to disks based
: on their serial numbers and everntually driver name.
: For example disk ad0 could also be accessed via /dev/disk/ata/3JX0LMGA
: (/dev/disk/<driver>/<serial> or /dev/disk/<serial>).

/dev/disk/ad/3JX0LMGA or /dev/disk/da/3JX0LMGA is the only thing
you'll be able to do. There's no mapping from the dev_t -> device_t,
so you have no way of knowing what the parent of the disk's dev_t.
All the I/O in the system is done with dev_t's.

Also, the cam system doesn't hook into the newbus system due to when
it was authored. There's been some resistance to moving the scsi
devices into the device_t tree, like all other storage devices. This
is part of the problem indoing thinging completely generically.

Should we add an entry to the ideas list about refactoring CAM to hook into newbus? If yes, could you please write a suitable plain text version?

Bye,
Alexander.

--
If voting could change the system, it would be illegal.
If not voting could change the system, it would be illegal.

http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137

_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"