Re: [OmniOS-discuss] OmniOS r151022 is now out!

[Dominik Hassler]

On 05/16/2017 09:12 PM, Paul B. Henson wrote:

From: Dominik Hassler
Sent: Tuesday, May 16, 2017 8:50 AM

This system has a different mainboard, so I wonder if it is BIOS related
and a BIOS upgrade on system 1 could help?


Perhaps a silly question, but had you tested booting from both drives before
the upgrade :)?



Not a silly question at all. Yes I did, and the device that fails was 
the primary boot device before; so when the initial boot after enabling 
loader failed I tried the second and since that one worked I changed 
primary and secondary now.

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151022 is now out!

[Dominik Hassler]

Addendum:

Just upgraded another system and there booting from both rpool devices 
works.


This system has a different mainboard, so I wonder if it is BIOS related 
and a BIOS upgrade on system 1 could help?


Another difference:

System 1 has been set-up in summer 2013, so it went r06 -> r08 -> ... -> r22
System 2 has been set-up in end of 2014, so it went r12 -> R14 -> ... -> r22

Not sure if that might have an impact, when OmniOS was set-up first 
(e.g. how partitions are created by installer)


On 05/16/2017 03:53 PM, Dominik Hassler wrote:

Ok, I did an installboot -mFf on both disks again (-v is not available
for installboot)

$ sudo installboot -mFf /boot/pmbr /boot/gptzfsboot
/dev/rdsk/c9t5000CCA04103E0B5d0s0
bootblock written for /dev/rdsk/c9t5000CCA04103E0B5d0s0, 223 sectors
starting at 1024 (abs 33154)
stage1 written to slice 1 sector 0 (abs 16065)
stage1 written to master boot sector

$ sudo installboot -mFf /boot/pmbr /boot/gptzfsboot
/dev/rdsk/c10t5000CCA04103E095d0s0
bootblock written for /dev/rdsk/c10t5000CCA04103E095d0s0, 223 sectors
starting at 1024 (abs 33154)
stage1 written to slice 1 sector 0 (abs 16065)
stage1 written to master boot sector

checked the version:

$ installboot -i /boot/gptzfsboot
Extended version string: 1.1-2017.4.23.2
MD5 hash: 766b5059c45796f049bb38b80e1a1c4d

and compared it to the version of both disks:

$ sudo installboot -i /dev/rdsk/c9t5000CCA04103E0B5d0s0
Extended version string: 1.1-2017.4.23.2
MD5 hash: 766b5059c45796f049bb38b80e1a1c4d

$ sudo installboot -i /dev/rdsk/c10t5000CCA04103E095d0s0
Extended version string: 1.1-2017.4.23.2
MD5 hash: 766b5059c45796f049bb38b80e1a1c4d


everything matches, but still the system boots only from one disk and
not the other. Since it is not the latest version you mentioned I'll
just wait until it is updated I guess. I can at least boot from one disk
so I am not too worried about it at the moment. Still I would prefer to
be able to boot from both.

On 05/16/2017 03:18 PM, Toomas Soome wrote:



On 16. mai 2017, at 15:58, Dominik Hassler  wrote:

Toomas,

using a (forced) installboot on both rpool mirror devices did the
trick. Loader is now being used.

However there is another problem. I can boot w/o problems from the
first device. But booting fails from the second device w/ the
following message:

Can't find /boot/zfsloader

illumos/x86 boot
Default: disk-1:/boot/zfsloader


Somehow the MBR on second disk is not properly updated and I think it
has wrong size recorded for stage2.

The initial installboot was implemented based on installgrub source
and we record the LBA with gptzfsboot start sector, and size (in
sectors) into MBR.

Now the copy of the MBR (the /boot/pmbr file) is also installed into
partition start sector 0), and when the beadm activate is run, the
boot blocks are updates, but with same logic, that with MBR+VTOC case,
the MBR itself is not updated (to keep multi boot setups safe), and
only partition sector 0 and stage 2 are updated. The oversight is that
the MBR is loading stage2 directly, and if the gptzfsboot size was
changed, the result is that not the entire gptzfsboot is read into the
memory and resulting with just the output as you can see.

later we did create the fix for installboot - the fixed installboot
will only record the location and size (1 sector) of the partition
boot recors (partition relative sector 0), and after that the MBR code
will read in the partition block, the partition block will read the
stage2, and so the MBR+VTOC case is not an issue any more.

to fix this, run installboot -mFfv against that second disk to ensure
the MBR block is properly updated - note the -v again, so you can
confirm the MBR and partition block and stage2 are all updated.

With installgrub we actually have the same issue, except, the grub
stage2 size virtually did not change and thats why the problem was
never revealed.

note, if your installboot command does allow to read the version from
/boot/gptzfsboot like that:

$ installboot -i /boot/gptzfsboot
Extended version string: 1.1-2017.5.6.2
MD5 hash: 2907581de9ca6bd4d2c12695a32cb749

then it has the bug fixed, and after installing MBR with such binary,
the MBR is always reading the sector 0 from partition start, and the
future updates are ok.

also note that MBR is always updated with GPT, and hence there the
issue does not appear (which why it took some time to notice it - my
own test systems were all using GPT:)

rgds,
toomas


boot:


Debug info below:

$ sudo installboot -i /dev/rdsk/c10t5000CCA04103E095d0s0
Extended version string: 1.1-2017.4.23.2
MD5 hash: 766b5059c45796f049bb38b80e1a1c4d

same on both devices


$ sudo format -> select disk -> fdisk
Total disk size is 36481 cylinders
Cylinder size is 16065 (512 byte) blocks

  Cylinders
 Partition   StatusType  Start   End   Length%
 =   ==  =   ===   ==   

Re: [OmniOS-discuss] OmniOS r151022 is now out!

[Dominik Hassler]

Toomas,

using a (forced) installboot on both rpool mirror devices did the trick. 
Loader is now being used.


However there is another problem. I can boot w/o problems from the first 
device. But booting fails from the second device w/ the following message:


Can't find /boot/zfsloader

illumos/x86 boot
Default: disk-1:/boot/zfsloader
boot:


Debug info below:

$ sudo installboot -i /dev/rdsk/c10t5000CCA04103E095d0s0
Extended version string: 1.1-2017.4.23.2
MD5 hash: 766b5059c45796f049bb38b80e1a1c4d

same on both devices


$ sudo format -> select disk -> fdisk
 Total disk size is 36481 cylinders
 Cylinder size is 16065 (512 byte) blocks

   Cylinders
  Partition   StatusType  Start   End   Length%
  =   ==  =   ===   ==   ===
  1   ActiveSolaris2  1  3648036480100

same on both devices


$ sudo prtvtoc /dev/rdsk/c10t5000CCA04103E095d0s2
* /dev/rdsk/c10t5000CCA04103E095d0s2 partition map
*
* Dimensions:
* 512 bytes/sector
*  63 sectors/track
* 255 tracks/cylinder
*   16065 sectors/cylinder
*   36480 cylinders
*   36478 accessible cylinders
*
* Flags:
*   1: unmountable
*  10: read-only
*
* Unallocated space:
*   First SectorLast
*   Sector CountSector
*   0 16065 16064
*
*  First SectorLast
* Partition  Tag  FlagsSector CountSector  Mount Directory
   0  200  16065 586003005 586019069
   2  501  0 586051200 586051199
   8  101  0 16065 16064


same on both devices


boot: status
Default: disk-1:/boot/zfsloader
boot: statusdisk devices:
disk0:   BIOS drive C ...
  disk0a: root
  disk0i: boot
disk1:   BIOS drive D ...
  disk1s1: Solaris 2
disk1s1a: root
disk1s1i: boot

zfs devices:
  pool: rpool
bootfs: rpool/ROOT/omnios-r151022
config:

NAME STATE
rpool DEGRADED
  mirror DEGRADED
c9t5000CCA04103E0B5d0s2 ONLINE
c10t5000CCA04103E095d0s0 OFFLINE

illumos/x86 boot
Default: disk-1:/boot/zfsloader
boot:


Any hints on how to get the system boot from both rpool devices are 
highly appreciated.



Kind regards,
Dominik

On 05/15/2017 08:40 PM, Toomas Soome wrote:



On 15. mai 2017, at 21:06, Dan McDonald  wrote:



On May 15, 2017, at 12:49 PM, Dominik Hassler  wrote:

Hey,

after the upgrade, the boot loader is still GRUB.

I did the upgrade according to the upgrade notes. Rebooted once, did a:

$ sudo beadm activate omnios-r151022
WARNING: menu.lst file /rpool/boot/menu.lst does not exist,
   generating a new menu.lst file
Activated successfully

checked for a /etc/default/be file. there is none. Still the boot loader is 
GRUB instead of loader.


Are you on a mirrored root pool?  It's possible the libbe code that installs 
loader doesn't do it to all disks in a mirrored pool...

Worst-case scenario is to explicitly install it:

foreach (drive)
installboot -m /boot/pmbr /boot/gptzfsboot /dev/rdsk/

Dan



The problem you have is that beadm activate does not enforce MBR update in case 
of MBR+VTOC partitioning; you need to either run bootadm install-bootloader 
-Mfv or installboot -mv.

Note that installboot and bootadm install-bootloader have slightly different 
flags; -v is good to have there, so you will see if the MBR was updated or not.

The beadm activate and bootadm use the same mechanism to update the bootblocks 
on all pool member disks, bootadm does have extra flag to allow MBR update. 
installboot does only update specified disk.

rgds,
toomas


___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151022 is now out!

[Philip Cristiano]

It looks like https://omnios.omniti.com/wiki.php/Installation should be
updated to point to the latest release. Currently it lists `r151020` as
the current stable and `r151014` as the current LTS. 

-- 
  Philip Cristiano
  philipcristi...@philipcristiano.com

On Fri, May 12, 2017, at 10:50 AM, Dan McDonald wrote:
> As always, please start with the release notes:
> 
>   https://omnios.omniti.com/wiki.php/ReleaseNotes/r151022
> 
> And for this release, there are upgrade notes:
> 
>   https://omnios.omniti.com/wiki.php/Upgrade_to_r151022
> 
> This is an LTS and Stable update.  Highlights include:
> 
> - BSD Loader is now available.  This has its own wiki page, including how
> to stick with GRUB if you think you need to.
> 
> - Kayak Interactive Installer --> No more Caiman, no more F-keys &
> curses, and no-more hacking timezone names.  Also, one less repo to
> maintain for OmniOS. Kayak does it all now.
> 
> - Python is now 2.7. This means an IPS/pkg(5) update too. There's a
> subtle, but noteworthy, update to linked-image semantics ("pkg update
> -r") AND upgrading non-linked-image "ipkg" zones is a bit more difficult
> due to the transition (chicken & egg problem with ipkg brand "attach").
> 
> - Perl is now 5.24.1.
> 
> - USB 3.0 support.
> 
> With OmniTI withdrawing funding for OmniOS-as-product, this will be the
> last OmniTI-pushed "release" of OmniOS. It contains all of the most
> recent (as of May) illumos-gate changes, AND illumos-joyent LX brand
> changes.
> 
> This release broke the 6-month cadence, due to Loader, Python2.7, and the
> need for Kayak to take over ALL installation duties.  I'm sorry for it
> being 1-2 months late, but I wanted to make sure these changes were
> comfortably in place during the 021 bloody.
> 
> Because of the sheer volume of change in this release, I had to update
> many OmniOS wiki pages.  Here's a list of all of those I changed
> nontrivially due to r151022.  Please check them out to make sure I'm not
> missing anything...
> 
>   https://omnios.omniti.com/wiki.php/ReleaseNotes/r151022
> 
>   https://omnios.omniti.com/wiki.php/Installation
> 
>   https://omnios.omniti.com/wiki.php/LXZones
> 
>   https://omnios.omniti.com/wiki.php/Upgrade_to_r151022
> 
>   https://omnios.omniti.com/wiki.php/NewLinkedImages
> 
>   https://omnios.omniti.com/wiki.php/linked_images
> 
>   https://omnios.omniti.com/wiki.php/KayakInteractive
> 
>   https://omnios.omniti.com/wiki.php/BSDLoader
> 
>   https://omnios.omniti.com/wiki.php/ReleaseCycle
> 
>   https://omnios.omniti.com/wiki.php/Packaging
> 
>   https://omnios.omniti.com/wiki.php/ReleaseNotes/
> 
>   https://omnios.omniti.com/wiki.php/WikiStart
> 
>   https://omnios.omniti.com/wiki.php/BuildInstructions
> 
>   https://omnios.omniti.com/wiki.php/Maintainers
> 
>   https://omnios.omniti.com/wiki.php/illumos-tools
> 
>   https://omnios.omniti.com/wiki.php/buildctl
> 
>   https://omnios.omniti.com/wiki.php/ReleaseMedia
> 
> I'll have more to say about my departure from OmniTI in a distinct
> e-mail.
> 
> Thanks, and happy upgrading!
> Dan
> 
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151022 is now out!

[Michael Rasmussen]

On Mon, 15 May 2017 15:40:36 -0500 (CDT)
Bob Friesenhahn  wrote:

> This is what I get on both of my systems running r151020 (014->016->018->022 
> on one and perhaps 018->022 on the other):
> 
> 13cbcd8decbec24324e283d875da433946d6af91
> 
> Doing a diff, I see only this difference:
> 
> % diff /boot/solaris/bootenv.rc bootenv.rc
> 42d41
> < setprop console text
> 
> Does this meant that the configuration has been somehow modified, or is the 
> difference benign?
> 
What you should do before rebooting after converting from grub to bsd
loader is to ensure that /boot/solaris/bootenv.rc.new does not exist
and if it exists copy it to /boot/solaris/bootenv.rc after you have
made a backup of the old /boot/solaris/bootenv.rc. The reason is that
the grub boot loader wants options to be included in '' while the bsd
boot loader considers '' around options a syntax error causing a boot
to fail.

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
--
/usr/games/fortune -es says:
"I once witnessed a long-winded, month-long flamewar over the use of
mice vs. trackballs...It was very silly."
(By Matt Welsh)


pgpW0rppyqVDo.pgp
Description: OpenPGP digital signature
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151022 is now out!

[Michael Rasmussen]

On Mon, 15 May 2017 14:06:45 -0400
Dan McDonald  wrote:

> 
> Are you on a mirrored root pool?  It's possible the libbe code that installs 
> loader doesn't do it to all disks in a mirrored pool...
> 
Seems to have done it here:
zpool status rpool
  pool: rpool
 state: ONLINE
  scan: scrub repaired 0 in 1h2m with 0 errors on Sun May  7 07:17:06 2017
config:

NAME  STATE READ WRITE CKSUM
rpool ONLINE   0 0 0
  mirror-0ONLINE   0 0 0
c8t3d0s0  ONLINE   0 0 0
c8t2d0s0  ONLINE   0 0 0

installboot -m /boot/pmbr /boot/gptzfsboot /dev/rdsk/c8t2d0s0
Updating master boot sector destroys existing boot managers (if any).
continue (y/n)? y
bootblock version installed on /dev/rdsk/c8t2d0s0 is more recent or identical
Use -F to override or install without the -u option

installboot -m /boot/pmbr /boot/gptzfsboot /dev/rdsk/c8t3d0s0
Updating master boot sector destroys existing boot managers (if any).
continue (y/n)? y
bootblock version installed on /dev/rdsk/c8t3d0s0 is more recent or identical
Use -F to override or install without the -u option


-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
--
/usr/games/fortune -es says:
If I had to live my life again, I'd make the same mistakes, only sooner.
-- Tallulah Bankhead


pgpT0FgJnl4wr.pgp
Description: OpenPGP digital signature
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151022 is now out!

[Michael Rasmussen]

On Fri, 12 May 2017 16:12:09 -0400
Dan McDonald  wrote:

> 
> You did say you were on KVM.  I wonder if blkdev or something else is being 
> problematic?
> 
> Try booting, but selecting the new BE using grub specifically.  (And if you 
> still want grub, put BE_HAS_GRUB=true into /etc/default/be on the 022 one 
> post-boot, or the next beadm will scribble loader.)
> 
Rebooted an chose 151022 from the grub menu did boot as expected.
Rebooted again to activate the new boot loader succeeded;-) Maybe this
should be added to the upgrade notes?

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
--
/usr/games/fortune -es says:
Linux: Because a PC is a terrible thing to waste.
(By komar...@craft.camp.clarkson.edu, Mark Komarinski)


pgpddHX8Y0jf5.pgp
Description: OpenPGP digital signature
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151022 is now out!

[Ian Kaufman]

Hmmm, having trouble going from 14 to 22. I cannot migrate to OpenSSH -

root@hiperq-data:/root# /usr/bin/pkg install --no-backup-be --reject
pkg:/network/ssh --reject pkg:/network/ssh/ssh-key --reject
pkg:/service/network/ssh --reject pkg:/service/network/ssh-common
pkg:/network/openssh pkg:/network/openssh-server
Creating Plan (Solver setup): \
pkg install: No matching version of network/openssh can be installed:
  Reject:  pkg://omnios/network/openssh@7.4.1,5.11-0.151022:20170511T001844Z
  Reason:  All versions matching 'require' dependency pkg:/library/security/
openssl@1.0.2.11,5.11-0.151022 are rejected
Reject:  pkg://omnios/library/security/openssl@1.0.2.11
,5.11-0.151022:20170510T232316Z
Reason:  This version is excluded by installed incorporation
pkg://omnios/incorporation/jeos/omnios-userland@11
,5.11-0.151014:20161221T194806Z
No matching version of network/openssh-server can be installed:
  Reject:  pkg://omnios/network/openssh-server@7.4.1
,5.11-0.151022:20170511T001853Z
  Reason:  All versions matching 'require' dependency
pkg:/SUNWcs@0.5.11,5.11-0.151022
are rejected
Reject:  pkg://omnios/SUNWcs@0.5.11,5.11-0.151022:20170510T212740Z
Reason:  This version is excluded by installed incorporation
pkg://omnios/consolidation/osnet/osnet-incorporation@0.5.11
,5.11-0.151014:20170301T162824Z
 This version is excluded by installed incorporation
pkg://omnios/incorporation/jeos/illumos-gate@11
,5.11-0.151014:20160804T060038Z


On Fri, May 12, 2017 at 7:50 AM, Dan McDonald  wrote:

> As always, please start with the release notes:
>
> https://omnios.omniti.com/wiki.php/ReleaseNotes/r151022
>
> And for this release, there are upgrade notes:
>
> https://omnios.omniti.com/wiki.php/Upgrade_to_r151022
>
> This is an LTS and Stable update.  Highlights include:
>
> - BSD Loader is now available.  This has its own wiki page, including how
> to stick with GRUB if you think you need to.
>
> - Kayak Interactive Installer --> No more Caiman, no more F-keys & curses,
> and no-more hacking timezone names.  Also, one less repo to maintain for
> OmniOS. Kayak does it all now.
>
> - Python is now 2.7. This means an IPS/pkg(5) update too. There's a
> subtle, but noteworthy, update to linked-image semantics ("pkg update -r")
> AND upgrading non-linked-image "ipkg" zones is a bit more difficult due to
> the transition (chicken & egg problem with ipkg brand "attach").
>
> - Perl is now 5.24.1.
>
> - USB 3.0 support.
>
> With OmniTI withdrawing funding for OmniOS-as-product, this will be the
> last OmniTI-pushed "release" of OmniOS. It contains all of the most recent
> (as of May) illumos-gate changes, AND illumos-joyent LX brand changes.
>
> This release broke the 6-month cadence, due to Loader, Python2.7, and the
> need for Kayak to take over ALL installation duties.  I'm sorry for it
> being 1-2 months late, but I wanted to make sure these changes were
> comfortably in place during the 021 bloody.
>
> Because of the sheer volume of change in this release, I had to update
> many OmniOS wiki pages.  Here's a list of all of those I changed
> nontrivially due to r151022.  Please check them out to make sure I'm not
> missing anything...
>
> https://omnios.omniti.com/wiki.php/ReleaseNotes/r151022
>
> https://omnios.omniti.com/wiki.php/Installation
>
> https://omnios.omniti.com/wiki.php/LXZones
>
> https://omnios.omniti.com/wiki.php/Upgrade_to_r151022
>
> https://omnios.omniti.com/wiki.php/NewLinkedImages
>
> https://omnios.omniti.com/wiki.php/linked_images
>
> https://omnios.omniti.com/wiki.php/KayakInteractive
>
> https://omnios.omniti.com/wiki.php/BSDLoader
>
> https://omnios.omniti.com/wiki.php/ReleaseCycle
>
> https://omnios.omniti.com/wiki.php/Packaging
>
> https://omnios.omniti.com/wiki.php/ReleaseNotes/
>
> https://omnios.omniti.com/wiki.php/WikiStart
>
> https://omnios.omniti.com/wiki.php/BuildInstructions
>
> https://omnios.omniti.com/wiki.php/Maintainers
>
> https://omnios.omniti.com/wiki.php/illumos-tools
>
> https://omnios.omniti.com/wiki.php/buildctl
>
> https://omnios.omniti.com/wiki.php/ReleaseMedia
>
> I'll have more to say about my departure from OmniTI in a distinct e-mail.
>
> Thanks, and happy upgrading!
> Dan
>
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>



-- 
Ian Kaufman
Research Systems Administrator
UC San Diego, Jacobs School of Engineering ikaufman AT ucsd DOT edu
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151022 is now out!

[Floris van Essen ..:: House of Ancients Amstafs ::..]

Thanks Dan,

Also for past help and all your very hard work, it really is a shame that 
OmniTI just pulled the plug, and you leaving them.
I certainly wish you the very best for the future, and do hope you will 
continue working on solarish OS'es

flrois

-Oorspronkelijk bericht-
Van: OmniOS-discuss [mailto:omnios-discuss-boun...@lists.omniti.com] Namens Dan 
McDonald
Verzonden: vrijdag 12 mei 2017 16:51
Aan: OmniOS-discuss 
Onderwerp: [OmniOS-discuss] OmniOS r151022 is now out!

As always, please start with the release notes:

https://omnios.omniti.com/wiki.php/ReleaseNotes/r151022

And for this release, there are upgrade notes:

https://omnios.omniti.com/wiki.php/Upgrade_to_r151022

This is an LTS and Stable update.  Highlights include:

- BSD Loader is now available.  This has its own wiki page, including how to 
stick with GRUB if you think you need to.

- Kayak Interactive Installer --> No more Caiman, no more F-keys & curses, and 
no-more hacking timezone names.  Also, one less repo to maintain for OmniOS. 
Kayak does it all now.

- Python is now 2.7. This means an IPS/pkg(5) update too. There's a subtle, but 
noteworthy, update to linked-image semantics ("pkg update -r") AND upgrading 
non-linked-image "ipkg" zones is a bit more difficult due to the transition 
(chicken & egg problem with ipkg brand "attach").

- Perl is now 5.24.1.

- USB 3.0 support.

With OmniTI withdrawing funding for OmniOS-as-product, this will be the last 
OmniTI-pushed "release" of OmniOS. It contains all of the most recent (as of 
May) illumos-gate changes, AND illumos-joyent LX brand changes.

This release broke the 6-month cadence, due to Loader, Python2.7, and the need 
for Kayak to take over ALL installation duties.  I'm sorry for it being 1-2 
months late, but I wanted to make sure these changes were comfortably in place 
during the 021 bloody.

Because of the sheer volume of change in this release, I had to update many 
OmniOS wiki pages.  Here's a list of all of those I changed nontrivially due to 
r151022.  Please check them out to make sure I'm not missing anything...

https://omnios.omniti.com/wiki.php/ReleaseNotes/r151022

https://omnios.omniti.com/wiki.php/Installation

https://omnios.omniti.com/wiki.php/LXZones

https://omnios.omniti.com/wiki.php/Upgrade_to_r151022

https://omnios.omniti.com/wiki.php/NewLinkedImages

https://omnios.omniti.com/wiki.php/linked_images

https://omnios.omniti.com/wiki.php/KayakInteractive

https://omnios.omniti.com/wiki.php/BSDLoader

https://omnios.omniti.com/wiki.php/ReleaseCycle

https://omnios.omniti.com/wiki.php/Packaging

https://omnios.omniti.com/wiki.php/ReleaseNotes/

https://omnios.omniti.com/wiki.php/WikiStart

https://omnios.omniti.com/wiki.php/BuildInstructions

https://omnios.omniti.com/wiki.php/Maintainers

https://omnios.omniti.com/wiki.php/illumos-tools

https://omnios.omniti.com/wiki.php/buildctl

https://omnios.omniti.com/wiki.php/ReleaseMedia

I'll have more to say about my departure from OmniTI in a distinct e-mail.

Thanks, and happy upgrading!
Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
...:: House of Ancients ::...
American Staffordshire Terriers

+31-628-161-350
+31-614-198-389
Het Perk 48
4903 RB
Oosterhout
Netherlands
www.houseofancients.nl
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151022 is now out!

[Volker A. Brandt]

Congratulations, and thank you for all the work you did.


Best regards -- Volker
-- 

Volker A. Brandt   Consulting and Support for Oracle Solaris
Brandt & Brandt Computer GmbH   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANYEmail: v...@bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513  Schuhgröße: 46
Geschäftsführer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss