> Release Notes

Important: 32-bit support.

Milestone 20 update 5, x86

This is a micro release. It uses the same upgrade mechanism as a regular upgrade, but is Milestone 20 with the illumos components updated.

New this release is a minimal ISO (for both regular and LX/omnitribblix variants). This is just over one fifth the size of the regular iso image. Ideal for server, custom builds, or if you're intending to use pkgsrc.

Milestone 20 update 4, x86

This is a micro release. It uses the same upgrade mechanism as a regular upgrade, but is Milestone 20 with the illumos components updated.

Also available at this time is an LX variant, with the illumos components being built from illumos-omnios (hence the nickname omnitribblix) rather than vanilla illumos-gate.

As of m20.4, the 32-bit kernel is no longer supplied. Use the original m20 release if you need 32-bit hardware support.

Milestone 20 update 3, x86

This is a micro release. It uses the same upgrade mechanism as a regular upgrade, but is Milestone 20 with the illumos components updated.

Also available at this time is an LX variant, with the illumos components being built from illumos-omnios (hence the nickname omnitribblix) rather than vanilla illumos-gate.

If you have problems with gcc being unable to find crt1.o, then doing a zap refresh and updating the develop overlay should fix it; or explicitly zap install TRIBsys-lib-c-runtime.

Milestone 20 update 2, x86

This is a micro release. It uses the same upgrade mechanism as a regular upgrade, but is Milestone 20 with the illumos components updated.

Also available at this time is an LX variant, with the illumos components being built from illumos-omnios (hence the nickname omnitribblix) rather than vanilla illumos-gate.

Milestone 20 update 1, x86

This is a micro release. It uses the same upgrade mechanism as a regular upgrade, but is Milestone 20 with the illumos components updated.

Also available at this time is an LX variant, with the illumos components being built from illumos-omnios (hence the nickname omnitribblix) rather than vanilla illumos-gate.

Milestone 20, x86

You should be able to upgrade to the m20 release from the m19 and m18 releases.

At this time, upgrading with zones is not supported. The upgrade will work, but the zones won't. You should save any data, destroy any zones, and recreate them after the upgrade.

The ISO is constructed slightly differently. This makes a number of installation scenarios much easier, but may impact on the ability to install on systems with very little memory. (More on memory requirements.)

There is a new bootloader in illumos. New installations of m19 and later will use the new bootloader. Upgrades from older releases will retain grub as the bootloader. [More]

Milestone 19, x86

You should be able to upgrade to the m19 release from the m18 release. Upgrades from m17 and m16 might work, but haven't been properly tested.

At this time, upgrading with zones is not supported. The upgrade will work, but the zones won't. You should save any data, destroy any zones, and recreate them after the upgrade.

There is a new bootloader in illumos. New installations of m19 and later will use the new bootloader. Upgrades from older releases will retain grub as the bootloader. [More]

Drive enumeration has changed because of changes to illumos. On fresh installs, you will no longer see drives on controller 0. For example, in VirtualBox the first drive will be c1t0d0 instead of c0t0d0 as in the past.

If you do a fresh install of the kitchen-sink, the slim login manager is now enabled by default. To enable slim on upgrades (or on older releases) use 'svcadm enable slim'.

Milestone 18, x86

If installing from the iso, you should zap update evince to fix a tiff dependency issue.

You should be able to upgrade to the m18 release from the m17 release. Upgrades from m16 might work, but haven't been properly tested.

At this time, upgrading with zones is not supported. The upgrade will work, but the zones won't. You should save any data, destroy any zones, and recreate them after the upgrade.

Milestone 17, x86

You should be able to upgrade to the m17 release from the m16 release. Upgrades from earlier releases are not supported, although the new over_install.sh script will allow you to install a new version into an existing pool.

At this time, upgrading with zones is not supported. The upgrade will work, but the zones won't. You should save any data, destroy any zones, and recreate them after the upgrade.

Milestone 16, x86

You should be able to upgrade to the m16 release from the m15 release. Upgrades from earlier releases are not supported.

At this time, upgrading with zones is not supported. The upgrade will work, but the zones won't. You should save any data, destroy any zones, and recreate them after the upgrade.

It is vital that you at least zap refresh followed by zap update TRIBlib-zlib after installation. The zlib package was incorrectly constructed and you will be unable to build software against it.

Milestone 20, SPARC

The m20 release on SPARC is built from the same illumos commit as the x86 version, so matches at that level, despite being created many months later.

Before installing additional software, run zap refresh to ensure the package catalog is up to date.

The m20 ISO for SPARC is known to boot properly. It has not yet been extensively tested, as I don't have enough spare hardware that I can afford to wipe clean.

You may see errors from mpt_sas about misc/sata not being found. The mpt_sas driver on SPARC is currently broken.

There are issues with libidn2 compatibility affecting various releases on SPARC. If you have a broken curl, uninstall it (zap uninstall TRIBcurl), and zap should be able to use wget as an alternative, allowing you to 'zap refresh' and install a fixed curl for the repo. If you have a broken wget, you may have to install libidn2 by hand. This problem also appears to affect the m16-m18-m20 upgrade route.

Milestone 18, SPARC

The m18 release on SPARC is built from the same illumos commit as the x86 version, so matches at that level, despite being created many months later.

There is currently no ISO image for this release, but you should be able to upgrade. More notes on this update.

Milestone 16, SPARC

The m16 release on SPARC is built from the same illumos commit as the x86 version, so matches at that level, despite being created many months later.

Many fewer additional packages are available for SPARC.

I know of multiple problems with graphics cards, and have had trouble with the bge driver (as used, for example, on the Sun Blade 1500).


tribblix@gmail.com