We've found that on any box (x86 for now) we network install opensolaris on (osol 2008.11) its boot disk is named different to that from s10updates and Nevada.
For example, a Ultra-20 goes from c0t0d0 to c4t0d0 and a x4500 (thumper)
from c3t0d0 to c6t0d0.
- makes life difficult in our lab for automation since its now unknown
what the boot disk will be named as.
Anyone seen this ?
--
Sean.
.
