Re: Attachment order of scsibus*

[mlelstv%serpens.de@localhost (Michael van Elst)]

ef%math.uni-bonn.de@localhost (Edgar =?iso-8859-1?B?RnXf?=) writes:

>Is there a way to steer the order of attachments?

You can create a custom kernel with a fixed set of attachments,
but it's not that versatile.

On the other hand, you rarely require "known" disk names.

For mounting, it's easier to name your partitions and use
wedges. If you cannot use GPT for some reason, you can
use a custom kernel that enables wedges for BSD labels
which is less intrusive than fixed attachments.

If you want to simplify access in userland, you can use
devpubd. There is already a hook distributed that
creates symlinks in /dev/wedges and I have another one
that maps drives from their identification information
like:

lrwxr-xr-x  1 root  wheel  8 Jan  1 11:04 naa-3000000005e60b7a@ -> /dev/sd4
lrwxr-xr-x  1 root  wheel  8 Jan  1 11:04 naa-300000006b0a5fa0@ -> /dev/sd2
lrwxr-xr-x  1 root  wheel  8 Jan  1 11:04 naa-300000009961dca3@ -> /dev/sd1
lrwxr-xr-x  1 root  wheel  8 Jan  1 11:04 naa-30000000a0a79904@ -> /dev/sd3
lrwxr-xr-x  1 root  wheel  8 Apr  5 11:29 wwn-5002538E40CCB943@ -> /dev/wd0

The sd1..4 use iSCSI identifiers, wd0 is a SATA drive. For USB drives
I check for a serial number. That method is not possible for every
hardware.