Commentary

Serdar Yegulalp
 

Opening Up To Solaris

OpenSolaris, Sun's open-source version of its Solaris operating system, gets its official kickoff today at Sun's CommunityOne conference in San Francisco.  And it's not Sun's attempt to knock Linux out of the box -- it's something a little subtler than that.

OpenSolaris, Sun's open-source version of its Solaris operating system, gets its official kickoff today at Sun's CommunityOne conference in San Francisco.  And it's not Sun's attempt to knock Linux out of the box -- it's something a little subtler than that.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

OpSol (the abbreviation I'll use since I can't well call it "OS") has been packaged to make it friendly to end users: the default ISO boots right into a live environment with the Gnome 2.20 desktop, and it comes packaged with a slew of other familiar-'n'-friendly FOSS applications.  But the desktop stuff is actually not the big draw, since that can be ported most anywhere.

When I talk to Sun fans about what would be most attractive about using OpSol right now, they all give me the same answer: ZFS, which is about as industrial-strength a file-storage solution as you're likely to get anywhere, open source or not.  What's more, instead of using a version ported to another platform, OpSol lets you use ZFS in its native kernel environment.  (One truly exciting possibility here: creating ZFS-based storage appliances.)

The big downside to OpSol: its licensing, which uses the GPL-incompatible CDDL.  It isn't impossible to mix and match CDDL and GPL software, but it takes some legerdemain -- either by compiling the GPL driver from source on OpSol, or by running binaries of all GPL code in userspace, separate from the kernel.  This latter option means a bit of a performance hit for certain things that would normally run in kernelspace.  That and the mere fact of this incompatibility might mean developers who've habitually used the GPL would be uncomfortable working with a different licensing scheme.

Again, I suspect the goal with OpSol is not to unseat Linux, but to provide a complementary development platform for many of the same things that can be built there.  The one analogy which comes to mind, much as I hate to make it, is how Microsoft is trying to push Windows Server 2008 as a great place to run open source software -- although WS08 and OpSol are poles apart, natch.

Sun's current strategy for monetizing OpSol is about what you'd expect: selling services and support.  The cost of the support isn't cheap -- it starts at several hundred dollars and goes up to a few thousand per system per year -- which sounds like a reflection of the kinds of professional customers Sun has in mind for OpSol.  Desktop and "just plain folks" users can always snag one of the derivative community-oriented distributions of OpSol that have already sprung up -- like Nexenta, a very nice bundling of GNU GPL software with an OpSol foundation.  I've snapped up .ISOs of Nexenta and OpenSolaris and plan on giving them a closer look.

The big question in my mind is whether Sun can natively cultivate the kind of community-development cultures that have surrounded other open source projects, both OSes and otherwise.  If they can't develop it natively, then there's a good chance it'll spring up around one of the derivative OpSol distros -- but I'd rather see Sun approach its prospective communities directly, instead of leaving that vital job to others.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links