Solaris 11 has been in the making since 2005, when Solaris 10 was launched. In fact, every major Solaris release is just a fork of the ongoing Solaris development train, so the very first uber-pre-release of Solaris 11 was actually generated only weeks after Solaris 10 hit the shelves.

Since then, Solaris 11 (or: Project Nevada as it was called) has seen a lot of OS history: An open source adolescence called OpenSolaris, growing adoption and community work, a broad range of ground-braking new features, long overdue re-writes, brand new concepts, controversial discussions, a major acquisition, rules changed and rules kept, siblings and offsprings, lots of investments, entire companies built on top of its source code, generations of processors and hardware, lots of systems in production, the Cloud and what not.

Assuming that Solaris 11 will be based on IPS just like OpenSolaris, it is certain that sysadmins will have to change a lot in how they create and manage packages, because IPS is fundamentally different from the good old System V packaging system.

So let's explore the lack of scripting hooks in IPS and see if we can find some ways of working around them:

Lots of speculation about Solaris and OpenSolaris is happening right now, with an allegedly leaked email being the latest generator of buzz, rumors and troll-ism.

But is that any useful? No.

So let's cut through the shiitake, do some due diligence and focus on some real facts instead.

In this article, we'll check out some real and authoritative sources of Solaris direction, mainly John Fowler's recent webcast about Solaris 11. Then we'll see what our future opportunities as members of the Solaris community are, and close with some pointers to other opinions on Solaris 11.

Tiny Thinking

Copyright (C) 2010 Constantin Gonzalez, some rights reserved.
This site uses Piwik, Google Analytics, Feedburner, Amazon Affiliate and possibly other web tracking code. This site also uses Facebook "Like", Flattr and other plugins that can send private data to their websites. See Imprint for details and our information policy.
By using this site you agree to not hold the author responsible for anything related to this site.