`<div>Thanks Dan. Have the LX zone patches been added in?</div><div><br><div class="gmail_quote"><div>On Wed, Feb 1, 2017 at 6:58 AM Dominik Hassler <<a href="mailto:hasslerd@gmx.li">hasslerd@gmx.li</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dan,<br class="gmail_msg">
<br class="gmail_msg">
updated according to your instructions and switched to loader<br class="gmail_msg">
afterwards. Everything went smooth.<br class="gmail_msg">
<br class="gmail_msg">
Thanks!<br class="gmail_msg">
Dominik<br class="gmail_msg">
<br class="gmail_msg">
On 02/01/2017 01:34 AM, Dan McDonald wrote:<br class="gmail_msg">
> Hello!<br class="gmail_msg">
><br class="gmail_msg">
> PLEASE READ THIS CAREFULLY BEFORE UPDATING!!! (And pardon any shouting, there are important things to read here.)<br class="gmail_msg">
><br class="gmail_msg">
> 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 <a href="http://pkg.omniti.com/omnios/bloody/" rel="noreferrer" class="gmail_msg" target="_blank">http://pkg.omniti.com/omnios/bloody/</a> 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.<br class="gmail_msg">
><br class="gmail_msg">
> 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.<br class="gmail_msg">
><br class="gmail_msg">
> 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.<br class="gmail_msg">
><br class="gmail_msg">
> 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.<br class="gmail_msg">
><br class="gmail_msg">
> I WANT TO MOVE TO LOADER<br class="gmail_msg">
><br class="gmail_msg">
> - 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.<br class="gmail_msg">
><br class="gmail_msg">
> - 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.<br class="gmail_msg">
><br class="gmail_msg">
> - If you have a pre-2017 bloody BE, or an older OmniOS release BE, you can not "beadm activate" it, beadm(1M) will fail.<br class="gmail_msg">
><br class="gmail_msg">
> - 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.<br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
> I WANT TO STICK WITH GRUB<br class="gmail_msg">
><br class="gmail_msg">
> - Put "BE_HAS_GRUB=true" into /etc/default/be. This will instruct beadm(1M) and libbe that you wish to continue with GRUB.<br class="gmail_msg">
><br class="gmail_msg">
> - 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.<br class="gmail_msg">
><br class="gmail_msg">
> - Old BEs will work fine, and you can "beadm activate" between all of them.<br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
> I WANT TO MOVE FROM GRUB TO LOADER NOW (after sticking with GRUB)<br class="gmail_msg">
><br class="gmail_msg">
> - Remove /etc/default/be on an active 2017 bloody BE.<br class="gmail_msg">
><br class="gmail_msg">
> - "beadm activate <current-BE>" -- you should see a message about /rpool/boot/menu.lst being created.<br class="gmail_msg">
><br class="gmail_msg">
> - You are now on loader.<br class="gmail_msg">
><br class="gmail_msg">
> - If the "beadm activate" fails, or you still are booting with GRUB afterwards, explicitly install loader by:<br class="gmail_msg">
><br class="gmail_msg">
> rm /etc/default/be (or at least remove the BE_HAS_GRUB line if you have multiple lines for some reason)<br class="gmail_msg">
> installboot -m /boot/pmbr /boot/gptzfsboot /dev/rdsk/<rpool-drive><br class="gmail_msg">
> rm /rpool/boot/menu.lst<br class="gmail_msg">
> beadm activate <current-BE> (should reconstruct /rpool/boot/menu.lst)<br class="gmail_msg">
><br class="gmail_msg">
> If you have mirrored roots, do the above installboot for each <rpool-drive>.<br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
> I WANT TO MOVE FROM LOADER BACK TO GRUB (after being on Loader)<br class="gmail_msg">
><br class="gmail_msg">
> - You will need to be in an active 2017 bloody BE.<br class="gmail_msg">
><br class="gmail_msg">
> - Invoke the following:<br class="gmail_msg">
><br class="gmail_msg">
> rm /rpool/boot/menu.lst<br class="gmail_msg">
> echo "BE_HAS_GRUB=true" > /etc/default/be<br class="gmail_msg">
> installgrub -m /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/<rpool-drive><br class="gmail_msg">
><br class="gmail_msg">
> If you have mirrored roots, use "installgrub -M /dev/rdsk/<installed-drive> /dev/rdsk/<mirror-drive><br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
> 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.<br class="gmail_msg">
><br class="gmail_msg">
> The repo will be updated within 24 hours of the sending of this mail. The Kayak bits, 24 hours after that.<br class="gmail_msg">
><br class="gmail_msg">
> Thanks for your patience as we move forward during this bloody cycle.<br class="gmail_msg">
><br class="gmail_msg">
> Dan<br class="gmail_msg">
><br class="gmail_msg">
> _______________________________________________<br class="gmail_msg">
> OmniOS-discuss mailing list<br class="gmail_msg">
> <a href="mailto:OmniOS-discuss@lists.omniti.com" class="gmail_msg" target="_blank">OmniOS-discuss@lists.omniti.com</a><br class="gmail_msg">
> <a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.omniti.com/mailman/listinfo/omnios-discuss</a><br class="gmail_msg">
><br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
OmniOS-discuss mailing list<br class="gmail_msg">
<a href="mailto:OmniOS-discuss@lists.omniti.com" class="gmail_msg" target="_blank">OmniOS-discuss@lists.omniti.com</a><br class="gmail_msg">
<a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.omniti.com/mailman/listinfo/omnios-discuss</a><br class="gmail_msg">
</blockquote></div></div>
`