[oi-dev] New Hipster ISOs are available

[Nikola M.]

On 10/16/14 12:40 AM, Jim Klimov wrote:
> On 2014-10-13 16:37, Alexander Pyhalov wrote:
>> I've just upgraded FreeBSD to OI Hipster :) zpool split, detach,
>> reinstall, send|recv...
>
>
> In a proper systematic approach that would have been "beadm create",
> install, "beadm activate". At most, replace "beadm" parts by manual
> fiddling with "zfs create", "zfs set" and such.

I think this is not the case here,
we are actually facing calls to actually destroy continuity of 
Openindiana upgrades until now,
because of gold rush for Hipster.
It is almost the same problem Oracle did when they discontinued 
upgrading from Opensolaris and Solaris Express to Solaris 11 and 
"invented" that they like more to push proprietary changes in new ZFS 
closed revisions as mandatory and vendor lock-in. It is like facing 
"Hipster lock-in" when recommending installing from hipster ISO , that 
is action that is intentionally destroying /dev actually. (And move away 
from OI all current users using /dev around globe).

As I said, it was fun upgrading from OI to Hipster a year ago,
now it is Not fun at all when Hipster is not caring to have nice upgrade 
path and continue with OI releases,  but someone else must do it..
Avoiding any kind of distribution release path and any kind of upgrade 
strategy, discussed and made into the policy and road map, but "do what 
you want if you can" - is the case here.
>
> There is no technical reason to require destruction of the rpool to
> install a new release of OI from scratch.
>
> Even if automated migration (of settings, installed set of software,
> etc.) is too complicated to be practical for scripting or impossible
> at all, there is no good reason to forbid coexistence of several OS
> releases on the same rpool.
Yeah, I even made it installing Ubuntu Linux beside OI on same rpool before.
It was needed to make new BE with beadm create, empty it, install Linux 
in it (it makes ZfsOnLinux kernel module, running from LiveCD before 
install) and only specific settings in GRUB1 boot menu were needed to 
boot it.