Heads Up !
Just successfully installed Solaris Express Developer Edition 9/07 snv_70b X86
as multi-boot.
The FAQs (Solaris Express Developer Edition Technical FAQs, e.g.) were scary
and misleading (and wrong).
I ran the [b]new[/b] installer, despite of the warnings, (x86: Solaris Express
Developer Edition 9/07 Getting Started), on my hard drive, principally looking
like
hda1 linux
hda2 solaris (bf)
hda3 solaris (bf)
(I guess, some will vomit here ;) )
under Linux.
hda1 is Debian, hda2 is Nexenta, hda3 the to-be nv70.
I set the type of hda2 to 40 (Venix 80286) and ran the new installer, which
offered hda3 as Solaris for install.
In the end, it wrote the MBR to c0d0 and the bootblock to c0d0s0. It came up
very properly after reboot. I tried a grub-boot-CD, and could as well boot to
Linux from there; as well as to nv70. Then I set up ('setup (hd0)') my previous
boot loader from Debian, and still can boot to Debian as well as nv70. Zero
problem.
Next, I changed back hda2 to bf (Solaris), and can now boot to Nexenta from
Debian's grub boot menu. I can as well boot to nv70, get the nv70-grub-boot.
Only at loading the kernel, nv70 crashes. But again, everything is fine when I
'hide' hda2 as type 40.
Probably, some 'hide' or 'map' in grub can help, and make two Solaris
partitions nicely bootable with standard grub. Or a minor change in Solaris, so
that the kernel load doesn't crash when another bf partition is around.
(Actually, it shouldn't. Once grub within that partition has come up, there is
no reason for the kernel to look outside that partition any longer.)
This message posted from opensolaris.org
