Mark Fenwick wrote: > I have a system with two disk drives, one has a late build of Nevada, > the other was going to be used for the OpenSolaris install. To make > sure I installed the new OS on my scratch disk, so I could switch > back to Nevada is required I made a careful note of the device names > for the disks: > > c0d0 c2t0d0 > > When I booted the OpenSolaris installer, the names are now: > > c3t0d0 C5d0 > > Why have they changed ? Its not a big deal, but I'm curious to know > why they are different. >
We're building a new devfs tree from scratch, and enumeration is not deterministic in my experience. You'll see this happen sometimes even between different boots of the live CD in the same hardware (or virtual machine). > Another little install problem, the disk with Nevada on was the boot > disk. After installing OpenSolaris, it added a new boot block on the > same disk physical disk as the new install. I was hoping it would > update the GRUB menu on the boot disk. Is this a bug ? > Nope, the installer doesn't concern itself with multiple drive situations at this time. File an RFE if you'd like. Dave _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
