[OmniOS-discuss] New OmniOS bloody very soon -- READ CAREFULLY!!!

Mini Trader miniflowtrader at gmail.com
Wed Feb 1 20:05:03 UTC 2017


Has the bug we found been fixed?

On Wed, Feb 1, 2017 at 11:04 AM Dan McDonald <danmcd at omniti.com> wrote:

> We do try to keep up with LX from Joyent.  The README.OmniOS file tracks
> this:
>
> https://github.com/omniti-labs/illumos-omnios/blob/master/README.OmniOS
>
> By recording the last illumos-Joyent commit we inspected.
>
> Dan
>
> Sent from my iPhone (typos, autocorrect, and all)
>
> On Feb 1, 2017, at 7:02 AM, Mini Trader <miniflowtrader at gmail.com> wrote:
>
> Thanks Dan. Have the LX zone patches been added in?
>
> On Wed, Feb 1, 2017 at 6:58 AM Dominik Hassler <hasslerd at gmx.li> wrote:
>
> Dan,
>
> updated according to your instructions and switched to loader
> afterwards. Everything went smooth.
>
> Thanks!
> Dominik
>
> On 02/01/2017 01:34 AM, Dan McDonald wrote:
> > Hello!
> >
> > PLEASE READ THIS CAREFULLY BEFORE UPDATING!!!  (And pardon any shouting,
> there are important things to read here.)
> >
> > Progress on our work for this bloody is going smoother than expected,
> thanks to the good work others have been doing upstream in illumos-gate.
> The Python2.7 switch has gone well (I'm seeing no complaints from bloody
> users).  The new bits we're about to push on to
> http://pkg.omniti.com/omnios/bloody/ will enable another upstream
> innovation:  BSD Loader.  Unlike previous updates, I want this mail on the
> list before I push packages out to the repo server.
> >
> > The BSD Loader provides a replacement for GRUB.  Its biggest upfront
> improvements over GRUB 0.97 are that it's an active Open Source project
> (GRUB went to 2.0), and that it eliminates the number-of-boot-environment
> limits that GRUB had.  Furthermore, BSD Loader provides a more stable
> foundation for future improvements such as EFI boot (vs. BIOS boot) and the
> possibility of booting off of raidZ pools.
> >
> > The official arrival of BSD Loader constitutes an operational flag day
> for bloody users.  This is a substantial enough change to merit its own new
> wiki page to accompany r151022's release.  Current users of bloody may
> notice the presence of this file:  /etc/default/be.  This file has been in
> place to PREVENT the use of loader.  As of this upcoming update, that file
> disappears, but it can be reconstituted.
> >
> > Before updating, you, the administrator, must make a decision:  Stick
> with GRUB, or move to loader.  The /etc/default/be file, specifically the
> "BE_HAS_GRUB=true" line, tells beadm(1M) what boot loader you wish to use
> going forward.
> >
> > I WANT TO MOVE TO LOADER
> >
> > - This is the default after updating, but Loader does not get installed
> until you "beadm activate" a loader-friendly BE (including the current
> one). Reboots after an update without the invocation of "beadm activate" or
> "installboot" will mean your machine stays with grub.  You should notice an
> extra message about /rpool/boot/menu.lst being created.
> >
> > - If you have bloody BE from 2017, it is loader-friendly, so long as you
> remove /etc/default/be from that BE's root filesystem.
> >
> > - If you have a pre-2017 bloody BE, or an older OmniOS release BE, you
> can not "beadm activate" it, beadm(1M) will fail.
> >
> > - An old BE CAN be booted from the new Loader menu, but beadm will not
> work properly in that pre-Loader boot environment once booted.
> >
> >
> > I WANT TO STICK WITH GRUB
> >
> > - Put "BE_HAS_GRUB=true" into /etc/default/be.  This will instruct
> beadm(1M) and libbe that you wish to continue with GRUB.
> >
> > - Technically this has been happening since the first bloody release of
> 2017. The difference now is that "pkg update" removes this file from a
> system-installed image.
> >
> > - Old BEs will work fine, and you can "beadm activate" between all of
> them.
> >
> >
> > I WANT TO MOVE FROM GRUB TO LOADER NOW (after sticking with GRUB)
> >
> > - Remove /etc/default/be on an active 2017 bloody BE.
> >
> > - "beadm activate <current-BE>" -- you should see a message about
> /rpool/boot/menu.lst being created.
> >
> > - You are now on loader.
> >
> > - If the "beadm activate" fails, or you still are booting with GRUB
> afterwards, explicitly install loader by:
> >
> >   rm /etc/default/be  (or at least remove the BE_HAS_GRUB line if you
> have multiple lines for some reason)
> >   installboot -m /boot/pmbr /boot/gptzfsboot /dev/rdsk/<rpool-drive>
> >   rm /rpool/boot/menu.lst
> >   beadm activate <current-BE>  (should reconstruct /rpool/boot/menu.lst)
> >
> > If you have mirrored roots, do the above installboot for each
> <rpool-drive>.
> >
> >
> > I WANT TO MOVE FROM LOADER BACK TO GRUB (after being on Loader)
> >
> > - You will need to be in an active 2017 bloody BE.
> >
> > - Invoke the following:
> >
> >   rm /rpool/boot/menu.lst
> >   echo "BE_HAS_GRUB=true" > /etc/default/be
> >   installgrub -m /boot/grub/stage1 /boot/grub/stage2
> /dev/rdsk/<rpool-drive>
> >
> > If you have mirrored roots, use "installgrub -M
> /dev/rdsk/<installed-drive> /dev/rdsk/<mirror-drive>
> >
> >
> > This update does NOT include an update to the ISO or USB install media
> yet (that's a problem we're still solving).  It WILL, however, include an
> update to kayak software a day or two after, and the Kayak .zfs.bz2 media.
> With this update, Kayak will now install both Loader AND use whole-disk GPT
> partitioning for rpools.  We'd appreciate additional feedback on the Kayak
> changes.
> >
> > The repo will be updated within 24 hours of the sending of this mail.
> The Kayak bits, 24 hours after that.
> >
> > Thanks for your patience as we move forward during this bloody cycle.
> >
> > Dan
> >
> > _______________________________________________
> > OmniOS-discuss mailing list
> > OmniOS-discuss at lists.omniti.com
> > http://lists.omniti.com/mailman/listinfo/omnios-discuss
> >
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omniosce.org/ml-archive/attachments/20170201/a43adb36/attachment-0001.html>


More information about the OmniOS-discuss mailing list