Illumos Makes OpenSolaris Board Threat Moot
On August 3 Nexenta hosted a conference call to announce a new open source project called "Illumos." Illumos is an open source alternative to a critical part of the OpenSolaris distribution free from the binds of Oracle. Still several days short of the deadline set by the OpenSolaris governing board to Oracle, perhaps this announcement makes it all moot.
The effort is headed up by former Sun and Oracle Solaris developer Garrett D'Amore. He said that Illumos is not a fork of OpenSolaris, but more of a code base that perhaps Nexenta, Belenix, and SchilliX can be built on one day. Most important to D'Amore and Illumos supporters is that the code base will live on and be free from the control of any corporate entity.
There is proprietary code in OpenSolaris that still needs to be replaced. D'Amore hopes to eliminate that by the end of the year, but it's a large task even with the talented developers already committed to the project. The goal is to be 100% open source and perhaps to eventually release Illumos under the Apache2 license.
Since Oracle is ignoring community developers and their code as much as the board, the community has all but dissolved. Illumos could give developers a place to innovate. D'Amore is hoping to recreate the community development phenomena found with Linux and the resulting distributions.
With the days counting down to the probable disbanding of the board and the constant threat of losing access to the source, Illumos might be all that remains of OpenSolaris sooner or later. Several distributions are based on OpenSolaris now, and its loss could have spelled disaster for those systems. That's why most of them as well as several current and former OpenSolaris developers have committed to Illumos. Other community partners include Joyent, berliOS, Greenviolet, and Everycity.
D'Amore said that if Oracle shuts down OpenSolaris, then time would be right for a fork, but for now they have invited Oracle to collaborate. As one might expect, Oracle has yet to respond. While Illumos is being developed in case of shut out or as an alternative, it may turn out to be the savior of the code. In fact, with enough interest from the right people, Illumos could replace OpenSolaris in the hearts and minds of all concerned.
Susan Linton is a Linux writer and the owner of tuxmachines.org.
|Speed Up Your Web Site with Varnish||Jun 19, 2013|
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
- Speed Up Your Web Site with Varnish
- Containers—Not Virtual Machines—Are the Future Cloud
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Linux Systems Administrator
- Non-Linux FOSS: libnotify, OS X Style
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- Android's Limits
- Reply to comment | Linux Journal
1 hour 9 min ago
- Yeah, user namespaces are
2 hours 26 min ago
- Cari Uang
5 hours 57 min ago
- user namespaces
8 hours 51 min ago
9 hours 16 min ago
- One advantage with VMs
11 hours 45 min ago
- about info
12 hours 18 min ago
12 hours 19 min ago
12 hours 20 min ago
12 hours 22 min ago
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?