Headline: Solaris 10/07 is just a litle dangerous

I had set up my t42p notebook to have about 100G disk free, then /dev/hda3 as my Debian root partition, and /dev/hda4 as my home partition.

So I then deleted my rarely used Windows partition (/dev/hda1), and proceeded to install Solaris SDE. The new GUI installer failed, unable to detect the existing partion scheme, so i gave up on that

Instead I went to use the older Solaris 10 installer, which completed after an hour or more, seemingly using primary /dev/hda1 that I had made, an then making sub-partitions inside, as though it were an extended partition. Odd, but OK, they're supposed to be professionals

One Solaris working, I figured I'd wasted procrastinated enough for today, and rebooted back to linux to get some work done.

OOoops. Firstly, without asking me, Solaris decided to change the active boot partion to itself how rude.

Fix that.

Mmm, no grub boot menu, thats odd. Some further messing about, and I find my linux root disk... in (hd0,1), not (hd0,2) where is was this morning... and for the last 14 months!

ok, load the conffile from there, and boot my last known good kernel........ mmmm, it boots, and then panics, unable to find /sbin/init on /dev/hda3.... Yep, makes sense if we're booting from (hd0,1), then the root also moved to /dev/hda2

Grrrrrrrr

reboot, mess with grub menu , and boot - all ok so far...

nope. can't log in, my /home doesn't exist - there's another oddity. although grub mounted /dev/hda2 as root, linux userspace thinks /dev/hda3 is mounted as root, believing whats in the /etc/fstab? bizzare

so, one more edit, and we're rebooting to a working system.

Rather a messy this Solaris thing.