[OpenIndiana-discuss] Installing Hipster

[Nikola M]

On 06/ 9/16 04:46 PM, Udo Grabowski (IMK) wrote:
> A seemingly very simple question:
>
>   - How to install a fresh (nonupdate) complete new Hipster
>     instance from an old /dev OI into a new BE ?

There is a manual on wiki for complicated but detailed manual install 
(http://wiki.openindiana.org/oi/Advanced+-+Manual+installation+of+OpenIndiana+from+LiveCD+media).

I used to do fresh install while keeping existing ones by installing OI 
hipster in VirtualBox,
having network between host OS (Older OI) and doing zfs send/receive. (I 
firstly made new BE with beadm create, mounted it with beadm mount /mnt, 
removed everything in it, bedam unmount, and after receiving zfs receive 
from VirtualBox I did beadm activate and was booting in fresh install.

It is true there is no option in installer (both GUI installer and text 
installer) to install fresh into new empty BE on existing system. People 
are invited to make it happen by changing installers with adding that 
option.

I would like it could be done to do fresh install using pkg operations, 
like beadm mount BEname /mnt
pkg image-create /mnt , pkg -R /mnt set-publisher -g 
http://pkg.openindiana.org/hipster/  openindiana.org ,pkg -R /mnt 
refresh , pkg -R /mnt install entire
But couldn't be done (just tried) , at least it is an idea :)
Maybe dissecting installer source and commands can say what it is doing 
when doing fresh install, and that is one step closer to patching it to 
support fresh install on new zfs dataset/BE.

> Tried hard, but it seems that this is impossible to do without
> rebooting into the new BE. 

Every time illumos is updated (osnet-incorporation in OI hipster), new 
BE is created and reboot is needed to start system from the new BE.
Rebootless operation is not supported after Solaris 8/9 (a la ksplice), 
illumos people generally argue it is not needed and regard rebootless 
kernel updates as complication to avoid.

> All attempts end with pkg referring
> to installed packages of the running system (and denying because
> of conflicting packages, etc.pp....). We just want a pristine
> /hipster on its own zfs filesystem without changing or halting
> the running system.

Try that VirtualBox zfs send trick. I installed like that from 20141010, 
then updated to hipster-2015 and now I am on /hipster, still retaining 
/dev install for testing.
Or play with manual install form LiveDVD at Wiki.