Jim Laurent - SE Sun McLean VA wrote: > I am in the process of installing Nevada build 46. Because of my > existing disk layout, I want to install it in the primary partition > where JDS-Linux used to be. (Who needs JDS-Linux anymore?) > > My current partitioning looks like this: > > Part 0 Windows 0-7805 Primary > Part 1 JDS-Linux 7806-14048 Primary > Part 2 Solaris 10 currently installed 14049-26240 Primary > Extended FAT32 data 26241-end Extended partition. > > I want to install NV46 in the JDS-Linux partition. Solaris installer > does not like have two Solaris primary partitions on the same disk. > When using Solaris partitioning the GUI, I can change the current > "Solaris" partion to "PriDOS" and then change the JDS partition to > "Solaris" and set the proper size. > > At the final "Ready to Install" screen, the installer reports that it > will delete my current partition and create a PRIDOS partition in its > place. This leads to my questions. > > 1. Will this action actually smash my data or simply re-label the > existing Solaris partition to PRIDOS (assuming the start and end > cylinders are identical) >
It should just relabel. > 2. If my data is preserved, will GRUB be able to boot the solaris in > Partition 1 as well as the Solaris in partition 2? > It won't be recognized automatically. You can probably hack around with the GRUB menu and make it work, but I haven't done so. > 3. Will I need to re-label partition 2 with the "Solaris 2" label? If > so, with which tool? fdisk? > You can re-label, but I don't believe it makes any actual difference in the results. > I'm dying to hit the "Install Now" button, but terrified of re-building > my currently installed (and working) OS. > I'd recommend getting a raw dump of the disk before doing any of this, because you're outside the configs we support and fdisk geometry disagreements are not unknown. I know a number of people have used g4u for this purpose, and there are of course commercial products. > (PS: as a result of this exersize, I learned that if you delete part 1 > and recreate it in the same place, it gets a higher number and part 2 > becomes part 1. This tends to upset grub as well as vfstab mount entries. > Yeah, there are some oddities in the way fdisk does things. Dave
