>A new SPARC binary snapshot is available.  This will probably be the last one
>before release, so please test it carefully.
>
>It also contains only one kernel.  The kernel now chooses the disk numbers
>dynamically.  Be careful if you have multiple disks, or build your own kernel
>after installing.

"Be careful" - very true ... I have an IPC with two disks (sd0 was on target 3,
sd1 was on target 1).  The new kernel decided that my target 3 disk is now sd1,
and the target 0 disk is sd0, so it wouldn't boot:

...
esp0 at sbus0 slot 0 offset 0x800000 pri 3: ESP100A, clock = 25 MHz, ID = 7
tg0 at esp0 target 1
sd0 at tg0 unit 0: IMPRIMIS 94601-15 4614, 2032500 512 byte blocks
sd0: <Seagate (CDC) Wren VII 94601-1.2G cyl 1703 alt 2 hd 15 sec 79>
tg1 at esp0 target 3
sd1 at tg1 unit 0: MAXTOR LXT-213S SUN0207 4.20, 415436 512 byte blocks
sd1: <SUN0207 cyl 1254 alt 2 hd 9 sec 36>
tg2 at esp0 target 4
unit 0 at tg2 (tape (removable) qual=0x0 version=<iso 2, ecma 0, ansi 0>) not
configured
le0 at sbus0 slot 0 offset 0xc00000 pri 5: hardware address 08:00:20:0e:8b:f1
cgthree0 at sbus0 slot 2 offset 0x0: SUNW,501-1718, 1152 x 900 (console)
bwtwo0 at sbus0 slot 3 offset 0x0: SUNW,501-1561, 1152 x 900
auxreg0 at mainbus0 ioaddr 0xf7400000
Found boot device sd1
panic: cannot mount root
syncing disks... done
rebooting

Given the prevalence of internal disks that are SCSI target 3, I wonder why the
new kernel was set up to (seemingly) assign sd disk numbers in increasing SCSI
target i.d. order?  (I realize I could change "sd-targets" in the PROM, but I
am hoping to change this machine to an SS2 w/ Weitek u-Power chip soon, and
that machine thinks "sd(0,0,0)" == SCSI target i.d. 3, no ifs ands or buts.)

Especially since this behavior contradicts the "sd-targets" PROM setting (i.e.,
if the PROM is set up to think that "sd0" == the first entry in "sd-targets",
namely "3...", then I'd like the kernel to do the same).

I can't boot the machine with this kernel doing this; a default boot gets me
the above, and if I try a "boot sd(0,0,0)netbsd -as" and tell it to use "sd1a"
as the root device, it goes and says "Found boot device sd0" (I don't know why,
as there's no root filesystem on the Wren VII) and that fails as well.  I had
to resort to turning off the external sd1 disk to get up and running to the
point where I could un-tar the snapshot binaries.  I had to resort to setting
the target i.d. of the external disk to 5 (i.e., higher than 3) in order to
get it recognized as "sd1" - which I needed, because my kernel source tree
(/sys -> /usr/src/sys) is mounted from the external disk, so I couldn't build a
new custom kernel unless I got it recognized at boot time as "sd1".

FYI,

	- Greg


------------------------------------------------------------------------------