Makoto:
> Brad>        /pci@80000000/@d/@2/@1:2
> (1)
> My mind is kind of out of control such that asking 
> irrevalent things. Device name while booting is no use for 
> Open Firmware boot. Sorry, Brad.

No problems :-). I really just need someone to chat with about my
problem and things to try to help free up my block, and I do really
appreciate you helping me with it.

> (2)
> Then I was suspicious the part of ':2'.
> What happens if just
> boot-file /pci@80000000/@d/@2/@1:
> set ?
> I assume :2 is the partion number or SCSI id ?

2 is the partition and 1 is the scsi id (in @1:2). It turns out after
thinking more about the disklabel stuff that 0 was the correct
partition, since root gets sd2a.

> OK. I now recoverd, what if
> at Open Firmware,
>    dev /
>    dev /pci@80000000/@d/@2/
>    ls
> typed ? use the string you find there. If you got
> sd@2:0, use
> boot-file /pci@80000000/@d/@2/@sd2:

This gives me /disk and /tape, which really didn't help,
but... thinking about this more helped me figure out my problem. I
looked again at the configuration inside my machine and the dev / ls
output, and the problem was that I was using the wrong id number for
the pci device. Doh! Both scsi drives were hooked up to the same
device (I guess, I don't really understand PCI). So, for completeness
in case someone finds this problem, my final setup which boots great
is:

boot-device /pci@80000000/@d/@4/@0:5,ofwboot.xcf (booting on my MacOS)
boot-file /pci@80000000/@d/@4/@1:0/netbsd (the NetBSD drive)

Whew! So now I can boot (and get stuck at a different place :-<, but
I'll cover that in a separate mail).

Thanks much for you help talking me through this!
Brad