You are here

OpenIndiana Announcements

Subscribe to OpenIndiana Announcements feed OpenIndiana Announcements
Community-driven illumos Distribution
Updated: 1 month 2 weeks ago

OpenIndiana Hipster 2018.10 is here

Wed, 10/24/2018 - 08:23

We have released a new OpenIndiana Hipster snapshot 2018.10. The noticeable changes:

  • Mate desktop was updated to 1.20.
  • Python 3.5 was added, a lot of Python modules are now delivered for 3.5 Python version in addition to 2.7 and 3.4.
  • Image Packaging System has received a lot of updates from OmniOS CE IPS and Solaris IPS.
  • KVM zone brand now allows you to manage your KVM VMs as illumos zones.
  • Several new compilers were added, including GCC 8 (with patches necessary to build illumos) and Rust 1.29.
  • A lot of components were migrated to 64-bit-only, most newly added software defaults to 64-bit.
  • Due to recent security fixes compatibilty with some Solaris applications was broken. Important one is VirtualBox
  • .

More information can be found in 2018.10 Release notes and new medias can be downloaded from

Categories: OpenIndiana

OpenIndiana Hipster 2018.04 is here

Sat, 04/28/2018 - 15:37

We have released a new OpenIndiana Hipster snapshot 2018.04. The noticeable changes:

  • Userland software is rebuilt with GCC 6.
  • KPTI was enabled to mitigate recent security issues in Intel CPUs.
  • Support of Gnome 2 desktop was removed.
  • Linked images now support zoneproxy service.
  • Mate desktop applications are delivered as 64-bit-only.
  • Upower support was integrated.
  • IIIM was removed.

More information can be found in 2018.04 Release notes and new medias can be downloaded from

Categories: OpenIndiana

Call For Testing: KPTI images and repository available

Mon, 03/05/2018 - 17:07

In a joint announcement with SmartOS and OmniOSce, we are pleased to call for testing the illumos KPTI implementation by Alex Wilson, John Levon, and Robert Mustacchi at Joyent; read the full story at

Our contribution to this testing phase consists of Live Install images (GUI and Minimal Text) as well as an IPS repository containing a KPTI-enabled build of illumos-gate.

The GIT branch used for building illumos-gate is located at:

It contains:

  1. Pre-KPTI patches from illumos-joyent for 9209, 9210, 9211, and 9215:
  2. Joyent’s KPTI patches from the kpti-squash branch at:

applied on top of illumos-gate as of 20180301.

The resources are available at

Install Images

The Live Media and Minimal Text Install images contained in this directory were generated on 20180302 from the KPTI branch and the main OpenIndiana Hipster repository.

They are available as ISO and USB images.


Additionally, the repository located at:

can be used to update the kernel to a new Boot Environment (BE) of an existing installation:

# beadm create kpti
# beadm mount kpti

Now assuming that the mountpoint is /path/to/be, the publisher should be added and set as preferred prior to the update:

# pkg -R /path/to/be set-publisher -P -O illumos-kpti
# pkg -R /path/to/be set-publisher --non-sticky
# pkg -R /path/to/be update -v

Finally, activate the BE and reboot:

# beadm activate kpti
# init 6

The repository is also provided as a p5p archive in the same directory.


For any feedback regarding this material, reach us at openindiana-discuss AT openindiana DOT org.

Happy testing!

Find below the message posted by John Levon to the developer mailing-lists of illumos and of the distributions:

Hi all, please see below for test images for the various distributions.
These images include the KPTI (and PCID) work done by Joyent up to the current kpti-squash branch.
They are non-DEBUG except as noted. As before, any and all testing is useful, especially with “weird” things like LDT-using code, older machines, etc.

Thanks to Aurélien Larcher and Andy Fiddaman for building the OI and OmniOS images below.




OmniOSce (bloody):

# pkg update pkg
# pkg apply-hot-fix –be-name=kpti
# init 6

or for DEBUG bits:

# pkg apply-hot-fix –be-name=kpti



Categories: OpenIndiana

Migration to GCC 6.4 as userland compiler

Mon, 02/12/2018 - 23:34

Modulo some minor details, the transition of our userland to GCC 6 is complete.

What does it mean in practice?

  1. All the packages in the main and encumbered repositories were rebuilt then republished.
  2. The component developer/gcc-6 provides now the default oi-userland compiler, GCC 6.4. The previous compiler GCC 4.9 is used only to compile developer/gcc-49 (self) and illumos-gcc.
  3. Any component submitted to oi-userland should now build with GCC 6.4.
  4. The reference compiler for illumos-gate and gfx-drm remains illumos-gcc 4.4.4. Compilation with developer/gcc-6 is possible but not officially supported (for development purposes only). The candidate for the next reference illumos-gate compiler is GCC 7.3.0.
  5. Recompilation of software installed manually is recommended, especially for C++ programs due to ABI incompatibilities.

Known issues:

  1. illumos-gate: As GCC 6 runtime libraries reside in /usr/gcc/6/lib and /usr/gcc/6/lib/$(MACH64), the runpath is embedded in many libraries. If the variable NIGHTLY_OPTIONS contains the flag ‘-r’, the check_rtime stage will fail. Until a fix is agreed upon with illumos-gate developers, the ‘-r’ flag should be removed from NIGHTLY_OPTIONS.
  2. tmux: The latest build cannot handle ‘CTRL^C’ properly, probably because it links to /usr/lib/values-xpg6.o, and libraries suddenly become XPG6-aware.
  3. repository size:  Due to the compiler migration, oi-userland was completely rebuilt, so that the main repository has grown significantly in size. We are likely going to clean it up from old packages this week.


  1. oi-userland dependencies tracking: With pull-request , the way the package dependencies resolution is handled has changed. There are two consequences: the time spent in the pkgdepend resolve phase has drastically decreased, but it also means that the build system is more sensitive to the list of dependencies defined by REQUIRED_PACKAGES. Any dependency found by pkgdepend should be present in REQUIRED_PACKAGES; resolve will fail otherwise. Note that on the build server the whole world is installed: be sure to disable unused options explicitly or to test components with all possible dependencies from oi-userland (and add them to REQUIRED_PACKAGES).
  2. build-essential: Due to the previous change we added REQUIRED_PACKAGES to many components and in theory we could shrink build-essential to ‘strictly required’ components (‘gmake env-prep’ is your friend). Some components were already removed from the meta-package.
  3. IIM: The component was finally removed as it was deprecated some time ago; ibus or xkbd should now be preferred.
  4. OpenJDK 8: The component was updated to 1.8.152 as it contains GCC 6 friendly fixes.
  5. JRuby: The component was updated to
  6. LUAJIT: The component was updated to 2.0.5 but may still exhibit linking failures due to portability issues.

Please do not hesitate to raise any issue related to package dependencies during the update phase, or to package regressions that could have unfortunately slipped through testing.

Categories: OpenIndiana

Call for testing: gcc 6.4.0-built repository available

Thu, 02/08/2018 - 16:00
Hi everyone,

we are happy to announce that a repository containing all the oi-userland packages built with gcc 6.4.0 is now available for testing.

The repository is located at:

It is synchronized with the latest oi-userland bits and contains some minor updates.

While these packages have been tested for a few weeks now, be aware that the repository should be used for evaluation only (not in production).

Note that illumos-gate is still built with illumos-gcc 4.4.4.   To test this repository we recommend that you create a new Boot Environment (BE), then update manually this newly created BE.

Assume the right credentials using sudo, or pfexec if you have ‘Software Installation’ profile: you need to add sudo or pfexec before each of the following command lines.

$ beadm create 20180207-gcc6 with ‘20180207-gcc6’ an arbitrary BE name.

$ beadm mount 20180207-gcc6
Mounted successfully on: '/tmp/tmp.7mayXC' with ‘/tmp/tmp.7mayXC’ the mountpoint of the new BE.

Add the gcc-6 repository to the list of publishers and set as preferred:   $ pkg -R /tmp/tmp.7mayXC set-publisher -P -O userland

$ pkg -R /tmp/tmp.7mayXC set-publisher --non-sticky

$ pkg -R /tmp/tmp.7mayXC publisher
userland                    origin   online F (non-sticky, disabled) origin   online F Finally you can update the new BE:   $ pkg -R /tmp/tmp.7mayXC update -v Be aware that the update can make up to 3GB of data.

The created BE can be chosen manually at the next reboot, or activated using:

$ beadm activate 20180207-gcc6 As usual you can always rollback to the previous BE if anything were to malfunction.   Please report any package dependency issue that may arise.

Happy testing!
Categories: OpenIndiana

OpenIndiana Hipster 2017.10 is here

Tue, 10/31/2017 - 13:45

We have released a new OpenIndiana Hipster snapshot 2017.10.

The noticeable changes:

  • Xorg server was updated to 1.19.5.
  • Mate was updated to 1.18.
  • Text installer now can perform basic OpenIndiana installation to existing ZFS pool (for example, in parallel to another OpenIndiana installation).
  • Cluster suite was updated.
  • ABI compatibility for Solaris 10u10 binaries was added.
  • We’ve started to remove Gnome 2 applications and libraries. Be warned if (by some strange reason) you still haven’t switched to Mate.

More information can be found in 2017.10 Release notes and new medias can be downloaded from

Categories: OpenIndiana

OpenIndiana Hipster 2017.04 is here

Wed, 05/03/2017 - 11:48

We have released a new OpenIndiana Hipster snapshot 2017.04. The noticeable changes:

  • Support for USB 3.0 devices was integrated.
  • Intel KMS port was reworked and should work on most Intel GPUs.
  • Xorg server was updated to 1.18.4.
  • Mate was updated to 1.16.
  • A lot of end user applications are delivered now as 64-bit only.
  • We introduced ca-certificates service to regenerate the CA bundle.

More informations can be found in 2017.04 Release notes and new medias can be downloaded from

Categories: OpenIndiana

Issues with loader leading to unbootable systems

Mon, 02/27/2017 - 09:52

A bug was found in the illumos bootloader that resulted in the inability to boot after updating Openindiana Hipster on MBR disk installs. The problem with booting is solved by updating to OI Hipster osnet-incorporation 0.5.11-2017.0.0.16205 (2017-02-25_1202) with system/boot/loader 1.1-2017.0.0.16205 (2017-02-25_1228) and upwards and reinstalling boot blocks. Here are some additional notes and technical information on the issue:

  • The boot programs written into disk boot block areas are read into memory based on recorded boot program sizes, since the MBR boot record is not updated by “pkg update” in case of MBR setups, the boot process will not read the gptzfsboot fully into the memory. This is problem with installboot command.
  • The loader partition reading code was built using optimized data sharing, assuming only one partition is “open” at the time. Unfortunately in case of ZFS this assumption is not true and as an result, the disk read validation checks did invalidate the IO requests.

Both issues are now identified, proper updates are available and the package updates are available in Openindiana Hipster package repository. Instructions below are provided, to perform the update, while avoiding the issues. The second issue is about the implementation specific details inside the loader and updated binaries which implement the fix. Once updated binaries are installed, no other special activities are needed. The installboot problem is more complicated. The installboot command update implements MBR update, to make MBR boot code able to read and load the partition boot record, and only record gptzfsboot location and size in partition boot record. As “pkg update” will always cause partition boot record to be updated, this change means that gptzfsboot will always be read using correct size. The complication is about the fact that we can not enforce MBR update automatically, and the MBR update has to be performed by the operator. The second complication that the patched installboot command is available only in the updated BE, meaning that bootblock update has to be performed twice. Who is affected:

  • Fresh installs with 20161030 OI Hipster snapshot usb/ISO using MBR partition/slice install, using illumos loader.

Who is not affected:

  • Older 20160421 usb/ISO and earlier installs still using GRUB1.
  • Full-disk installs and GPT installs for rpool.

How problem appears: Problem appears by issuing regular ‘pkg update ‘ procedure, which results in having unbootable system after update and restart. Workaround 1 is done right after update, before reboot, so you don’t experience boot failures. Nothing happens if you reinstall loader upon update and BEFORE restart. Workaround 2 is there if you already restarted after update and you have an unbootable system. Workaround 1: Bootblock update has to be performed twice, after regular pkg update and before reboot and after reboot again. Find the name of your new active updated BE:

$ beadm list -- oi-hipster-87 R / 36.8G static 2017-02-25 19:07

Mount new BE into /mnt dir, so we can install new loader into MBR: (assume root privileges by su, sudo or pfexec)

$ pfexec bash # beadm mount oi-hipster-87 /mnt

Install new illumos loader from new BE into MBR to be able to boot from HD again:

# bootadm install-bootloader -MfvR /mnt

The bootadm command above will reinstall boot code, using boot programs from /mnt/boot, using verbose mode, so you can see the MBR code is also updated. -unmount new BE from /mnt dir:

# beadm unmount oi-hipster-87 # shutdown -y -g 0 -i 6

After reboot, again re-install boot code as priviledged user: (assume root privileges by su, sudo or pfexec)

$ pfexec bash # bootadm install-bootloader -Mfv

Because this bootadm command is run from updated BE and the patched installboot command is used, MBR is updated to read partition boot record, and future “pkg update” command does not need any special workarounds. Workaround 2: If you already experienced the boot failure after update, you need to boot from live USB/DVD media into your new updated BE and reinstall loader: Use bootable USB/ISO disk to boot from media other then HD (by selecting it to be first bootable media in motherboard settings). Hit ‘ESC’ key to get loader “ok” prompt and list Boot Environments(BE) (rpool is name of boot pool):

ok beadm list zfs:rpool BE bootfs oi-hipster-87 rpool/ROOT/oi-hipster-87

Activate new BE to boot from (where beadm_name is the new BE created after update):

ok beadm activate oi-hipster-87 zfs:rpool

Boot into new BE:

ok boot

After booting into updated BE, you would need to issue this command to reinstall loader on HD MBR (so that problem is resolved for the next reboot): Install the new illumos loader from new BE into MBR to be able to boot from HD again (as the privileged user):

$ pfexec bash # bootadm install-bootloader -Mfv

After that you can safely update and restart. Thank you for your patience understanding. The loader is a part of the illumos which is still a work in progress. MBR booting problem slipped in testing, but is now safely overcomed. Send your appreciation to Toomas Soome (tsoome) for both creating and fixing the illumos loader and for providing larger a large part of this article.

Categories: OpenIndiana

Updated Intel DRM support for OpenIndiana

Wed, 12/07/2016 - 16:46

We’ve prepared ISO images with updated DRM drivers.

They can be found here.

New drivers should support some older hardware, which is currently not supported in OI.

There are currently 2 known issues with this code:

  • it still doesn’t restore VGA text mode on Xorg exit;
  • users reported seeing ‘WARNING: [drm:ivybridge_irq_handler:1150] Unclaimed register before interrupt’ warning in /var/adm/messages .

If you find more, please, report.

Categories: OpenIndiana