On 11/10/09 12:19 PM, Steven Acres wrote:
I didn't clobber my SXCE and migrated to OpenSolaris using the method I blogged about here: http://blog.swatteksystems.com/whats-that/archive/2009/10/20/sxce-to-opensolaris-migration-on-sparc( the references/blogs I utilized are noted within that entry ).
Been doing this for a while on SPARC, but there doesn't seem to be any reason why it shouldn't work on X86. You could even manually edit the menu.lst files on both images. You can even do an image -update from sxce of the OSol installation. Of course, you do need a separately bootable disk which could be a show stopper. It could perhaps be simpler if you do have such a disk to simply install OSol from a CD on it if your system has a bootable CD drive.... There are a couple of caveats. One you mentioned is that you have to be careful to make sure the BEs have different names. The other is the propensity at reboot time for beadm to gratuitously update every boot archive it can find (Bug 11358) which may or may not be disastrous. One workaround is to make sure you export the other root pool if you have it imported before rebooting. Also, AFAIK, building pkg from hg isn't quite so easy any more. It is much easier to build the slim-source - see Matt Keenan's blog entry http://blogs.sun.com/mattman/entry/iso_creation_with_distro_constructor which includes SUNWipkg. Depending on your sxce version you might have to fix up some links in sxce /usr/lib. Otherwise it builds quite cleanly using SUNWspro. There's probably no incentive to do this any more because of the imminent demise of sxce, but it would be nice on Solaris: AFAIK it is possible to run sxce in a OSol zone (is this true?). Is there any possibility of running OSol in an sxce zone? I imagine this might be another solution to the OP's question and might be useful in a number of shops... HTH -- Frank _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
