Hello Edgar. The attachment order on PCI busses is generally driven by
the order in which
the devices appear on the various busses. Historically, as I remember, PCI
slots are iterated
over starting with the slot nearest the power supply in most PC machines and
working toward the
far side of the mother board.
If you build a custom kernel, you can nail the sd indexes to the specific
scsibusses they
attach to. for example: sd0 at scsibus1 target 0.
Then, the disks that are probed before sd0 will start numbering at sd1. for
example, sd1 at
scsibus0 target 0.
However, because this can get messy very quickly, especially if you
need to boot a
non-custom kernel for some reason, I'd suggest building partitions as wedges
and using the
named partitions as identifiers in your /etc/fstab file. If you're running a
version of NetBSD
that doesn't support that, I'd suggest building raidframe raid sets which
automatically hide
all those attachment details once you enable auto-configuration. Both of those
options are
very nice when disks start appearing and disappearing on systems that have been
in use for a
while.
Hope that helps.
-Brian
