OpenIndiana

OpenIndiana is a free and open-source Unix operating system derived from OpenSolaris and based on illumos. Forked from OpenSolaris after OpenSolaris was discontinued by Oracle Corporation, OpenIndiana takes its name from Project Indiana, the internal codename for OpenSolaris at Sun Microsystems before Oracle’s acquisition of Sun in 2010.
Created by a development team led by Alasdair Lumsden, the OpenIndiana project is now stewarded by the illumos Foundation, which develops and maintains the illumos operating system. The project aims to make OpenIndiana “the "de facto" OpenSolaris distribution installed on production servers where security and bug fixes are provided free of charge.”
History.
Origins.
Project Indiana was originally conceived by Sun Microsystems, to construct a binary distribution around the OpenSolaris source code base. Project Indiana was led by Ian Murdock, founder of the Debian Linux distribution.
OpenIndiana was conceived after negotiations of a takeover of Sun Microsystems by Oracle were proceeding, in order to ensure continued availability and further development of an OpenSolaris-based OS, as it is widely used. Uncertainty among the OpenSolaris development community led some developers to form tentative plans for a fork of the existing codebase.
These plans came to fruition following the announcement of discontinuation of support for the OpenSolaris project by Oracle.
Initial reaction.
The formal announcement of the OpenIndiana project was made on September 14, 2010, at the JISC Centre in London. The first release of the operating system was made available publicly at the same time, despite being untested. The reason for the untested release was that the OpenIndiana team set a launch date ahead of Oracle OpenWorld in order to beat the release of Solaris 11 Express.
The announcement of OpenIndiana was met with a mainly positive response; over 350 people viewed the online announcement, the ISO image was downloaded over 2000 times, the Twitter account obtained over 500 followers, and numerous notable IT press websites wrote about the release. The broadcast bandwidth of the announcement was substantial, noted to top 350Mbit/second. The network package depot server experienced 20x as much traffic interested in their distribution than they originally planned for, resulting in more threads later being provisioned.
Not all reporting was positive, though, as some online articles questioned the relevance of Solaris given the market penetration of Linux. One article was critical of the OpenIndiana launch, citing a lack of professionalism with regard to releasing an untested build, and the project's lack of commitment to a release schedule. The initial OpenIndiana release was advertised as experimental and directly based on the latest OpenSolaris development build, preliminary to the OpenSolaris 2010 release.
Community building.
With the OpenSolaris binary distribution moved to SolarisExpress and the real-time feed of OpenSolaris updates discontinued, concerns abounded over what would happen to OpenIndiana if Oracle decided to stop feeding source code back into the community. The OpenIndiana team mitigated these concerns when they announced their intention to move the source code feed to the illumos Foundation.
Concerns were raised about possible discontinuation of free access to the Oracle-owned compiler being used to produce OpenIndiana. In response, OpenIndiana was modified to be able to compile under the open source GNU Compiler Collection.
The Hardware Compatibility List (HCL) remains somewhat informal, fragmented and uncentralized, requiring much end-user research for hardware selection. The lack of a comprehensive centralized HCL follows from the fact that the OpenSolaris HCL was hosted on Oracle server infrastructure and the server-side code for the Device Driver Utility submission was not made available.
In August 2012, founding project lead Alasdair Lumsden stepped down from the project, citing personal reasons and frustration with the lack of progress made on the project. Among the reasons for lack of progress were lack of developers and resources. In his resignation, Lumsden wrote, "For many of us this was the first open source project we had ever contributed to, myself included. The task at hand was vast, and we were ill equipped to deal with it."
Since Lumsden's resignation, the project is developed by a team of volunteers and is a completely horizontal and participative community effort.
Media reception.
A September 2013 DistroWatch review stated that the OpenIndiana project has "seemingly been in steady decline for the last couple of years." The same review concluded that OpenIndiana had not progressed significantly from the state of OpenSolaris five years before:
A May 2015 DistroWatch review of OpenIndiana similarly concluded that little major progress had been made to the system over the years. The review stated that the package selection and hardware support seemed to lag behind other systems, while many of the system administration features have either replicated or ported to Linux and BSD. The review concludes that:
Claims about lack of package support may be mitigated by the fact that the 3500+ software packages provided by OpenIndiana Hipster are not split into several packages, which would artificially increase the package count (e.g. like in Linux distributions): the Image Packaging System is a file-based package management providing incremental updates and package facets, making such splitting an unnecessary burden. In the course of the first two years of its existence, the Hipster project has migrated and updated over 1500 packages: it maintains a collection of selected software packages while relying on third-party repositories like SFE for add-ons. For extended selection, the pkgsrc system supported by Joyent readily provides 20000+ packages for illumos systems.
Relation to other Operating Systems.
OpenIndiana is a fork in the technical sense but it is a continuation of OpenSolaris in spirit. The project intends to deliver a System V family operating system which is binary-compatible with the Oracle products Solaris 11 and Solaris 11 Express. However, rather than being based on the OS/Net consolidation like OpenSolaris was, OpenIndiana is based on illumos. The project does use the same Image Packaging System (IPS) package management system as OpenSolaris.
While the OpenIndiana codebase was initially based on the majority of publicly available code from Oracle, this is not the case since the oi_151a Development Builds which are based on illumos from September 2011 onwards. The project has effectively moved away from Oracle-owned tools such as Sun Studio: all builds since 2013, including the active Hipster branch, use the GNU Compiler Collection (GCC) as sole compiler. The illumos project itself is built with GCC since June 15, 2012.
Release schedule.
Experimental Builds.
The first experimental release of OpenIndiana, Build 147, was released on September 14, 2010; the second experimental release, Build 148, was released on December 17, 2010.
Development Builds.
A first development release, Build 151 was released on September 14, 2011. This is the first release to be based upon illumos. MartUX 151a0 was released as the first SPARC build for OpenIndiana. Build 151a7 for Intel/AMD architectures was released on October 6, 2012. Build 151a8 was released August 10, 2013. OpenSXCE 2013.01 SPARC Build 151a, formerly MartUX, was released through OpenIndiana on February 1, 2013, as the second and possibly last OpenIndiana SPARC build, with subsequent releases based upon DilOS.
Hipster.
Since the development model inherited from the OpenSolaris project was unsuitable for a community project, the Hipster initiative was created late 2013 to reboot and modernize OpenIndiana.
The Hipster project is a fast development branch of OpenIndiana based on a rolling-release model and a horizontal contribution scheme through the oi-userland build system and the use of continuous integration.
Hipster is actively maintained: the repository receives software updates as well as security fixes, and installation images are published twice a year.
Every snapshot release is announced via mailing list and Twitter.
The first snapshot release was delivered on February 14, 2014, and subsequent snapshots were based on a six-month development cycle.
Some notable features of Hipster:
The list of features is updated for each development cycle on the Roadmap page of the issue tracker.