[OmniOS-discuss] Install issues

[Josef 'Jeff' Sipek]

On Sun, Aug 24, 2014 at 01:59:43PM -0400, Dan McDonald wrote:
> 
> On Aug 24, 2014, at 11:25 AM, Scott LeFevre <slefevre at indy.rr.com> wrote:
> 
> > Dan,
> > 
> > That did the trick.  I'm up on r151010. Thanks!
> 
> That's how I bootstrap new bloody releases (e.g. 151011 from 151010).
> Never done it officially moving 006/008 up to 010.
> 
> > BTW, can this approach (with some modification) be used to move to
> > OmniOS from a running install of OpenIndiana for example?
> 
> I don't think so, because:
> 
> 	1.) OI uses a different package name, numbering, and possibly even
> 	contents in some corner cases.
> 
> 	2.) I've never tried anything even close to it.

The closest to anything like that I've done was going from OpenIndiana to
OpenIndiana Hipster in a clean-slate way.

It basically consisted of:

(1) create a new be

(2) zfs destroy it

(3) zfs create the same-named dataset and set org.opensolaris.libbe:uuid to
    the same value as before

(4) beadm mount hipster

(5) pkg -R /tmp/XYZ image-create

(6) pkg -R /tmp/XYZ install slim_install

(7) bootadm update-archive -R /tmp/XYZ

(8) modify a bunch of config files in /tmp/XYZ/etc  (hostname, passwd,
    shadow, etc.)

(9) do a symlink dance in /tmp/XYZ/etc/svc

(10) reboot

Ok, I actually had to boot into the old BE a couple of times because I kept
forgetting to set some things (like root password - oops!).  If you dig up
the omnios install scripts, you can get enough of an idea how to make smf
happy enough to start.

I did this instead of a plain ol' reinstall because I didn't want to lose a
working system.  With this complicated way, I could always go back to my OI
BE.  I did not have to repartition or recreate the rpool - that was the
other goal.

Jeff

-- 
Computer Science is no more about computers than astronomy is about
telescopes.
		- Edsger Dijkstra