<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Ditto on the outdated libraries&#8230;</title>
	<link>http://www.vmunix.com/mark/blog/archives/2006/05/10/ditto-on-the-outdated-libraries/</link>
	<description>by Mark Mayo</description>
	<pubDate>Tue,  7 Oct 2008 04:40:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: David Comay</title>
		<link>http://www.vmunix.com/mark/blog/archives/2006/05/10/ditto-on-the-outdated-libraries/#comment-30758</link>
		<pubDate>Wed, 21 Jun 2006 00:54:01 +0000</pubDate>
		<guid>http://www.vmunix.com/mark/blog/archives/2006/05/10/ditto-on-the-outdated-libraries/#comment-30758</guid>
					<description>Mark,

Your and Peter's point about outdated libraries is
definitely something that we're aware of and working on
addressing.  In the upcoming Solaris Express release
based on build 42 of OpenSolaris, a whole lot of things have
been upgraded including the libraries associated with GNOME 2.14
and libxml 2.6.23 (yes, I'm aware there are newer versions
beyond this but this is a big improvement).

Longer term, we're working on how to push these out more
quickly but at the same time maintaining stability when its
appropriate.  If there are other libraries of interest that you think
are in need of more regular updates, please let us know.</description>
		<content:encoded><![CDATA[<p>Mark,</p>
<p>Your and Peter&#8217;s point about outdated libraries is<br />
definitely something that we&#8217;re aware of and working on<br />
addressing.  In the upcoming Solaris Express release<br />
based on build 42 of OpenSolaris, a whole lot of things have<br />
been upgraded including the libraries associated with GNOME 2.14<br />
and libxml 2.6.23 (yes, I&#8217;m aware there are newer versions<br />
beyond this but this is a big improvement).</p>
<p>Longer term, we&#8217;re working on how to push these out more<br />
quickly but at the same time maintaining stability when its<br />
appropriate.  If there are other libraries of interest that you think<br />
are in need of more regular updates, please let us know.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: binarycrusader</title>
		<link>http://www.vmunix.com/mark/blog/archives/2006/05/10/ditto-on-the-outdated-libraries/#comment-11832</link>
		<pubDate>Fri, 12 May 2006 00:04:13 +0000</pubDate>
		<guid>http://www.vmunix.com/mark/blog/archives/2006/05/10/ditto-on-the-outdated-libraries/#comment-11832</guid>
					<description>I really don't buy the "outdated" complaints.

If you look at almost any of the recent Enterprise Offerings from vendors such as RedHat, SuSE, etc. you'll find that their libraries are just as outdated.

Case in point, RHEL3 which is still a supported and shipping version of RedHat Enterprise Linux ships with a *broken for three years now* version of XML::DOM. In addition, many of the perl libraries it ships with are also a few years out of date.

Enterprise level systems will always be somewhat behind the bleeding edge distributions. They take a significant amount of time to test before they are even launched, and that means things will be outdated by the time it ships.

Personally, I don't care about outdated libraries, I care about *stable* libraries. If I really need the newest "whoop-tee-do" library I'll package it myself and install it under an alternate tree. I've done it before, and I'll do it again if the need arises (which so far, has only been the case with libraries that didn't already exist).</description>
		<content:encoded><![CDATA[<p>I really don&#8217;t buy the &#8220;outdated&#8221; complaints.</p>
<p>If you look at almost any of the recent Enterprise Offerings from vendors such as RedHat, SuSE, etc. you&#8217;ll find that their libraries are just as outdated.</p>
<p>Case in point, RHEL3 which is still a supported and shipping version of RedHat Enterprise Linux ships with a *broken for three years now* version of XML::DOM. In addition, many of the perl libraries it ships with are also a few years out of date.</p>
<p>Enterprise level systems will always be somewhat behind the bleeding edge distributions. They take a significant amount of time to test before they are even launched, and that means things will be outdated by the time it ships.</p>
<p>Personally, I don&#8217;t care about outdated libraries, I care about *stable* libraries. If I really need the newest &#8220;whoop-tee-do&#8221; library I&#8217;ll package it myself and install it under an alternate tree. I&#8217;ve done it before, and I&#8217;ll do it again if the need arises (which so far, has only been the case with libraries that didn&#8217;t already exist).
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Chris Adams</title>
		<link>http://www.vmunix.com/mark/blog/archives/2006/05/10/ditto-on-the-outdated-libraries/#comment-11826</link>
		<pubDate>Thu, 11 May 2006 17:53:35 +0000</pubDate>
		<guid>http://www.vmunix.com/mark/blog/archives/2006/05/10/ditto-on-the-outdated-libraries/#comment-11826</guid>
					<description>I cannot agree more strongly - this one of the reasons why I've been following the Nexenta project. The Solaris 10 kernel has some very nifty ideas (dtrace, zfs, zones) but the feature-poor userland, bizarre filesystem layout and incredibly inadequate package management (I played around with the Solaris 10 install shipped on our last V20z - just attempting to install security updates brought back a powerful feeling of nostalgia for the Slackware 2.0 days) are a deal-killer. 

So far Nexenta has been making great progress at delivering Solaris with a Debian/Ubuntu userland - even the liveCD has an environment which is embarrassingly better than Sun's shipping S10 install. If Sun has any ambition at recapturing mindshare from Linux they need to put the current Solaris userland on legacy-support and either hire the Nexenta guys or put a full team on producing a modern userland rather than patching the existing one; otherwise they're just going to stay in the increasingly small niche of shops which have already invested the time automating the Solaris warts away.</description>
		<content:encoded><![CDATA[<p>I cannot agree more strongly - this one of the reasons why I&#8217;ve been following the Nexenta project. The Solaris 10 kernel has some very nifty ideas (dtrace, zfs, zones) but the feature-poor userland, bizarre filesystem layout and incredibly inadequate package management (I played around with the Solaris 10 install shipped on our last V20z - just attempting to install security updates brought back a powerful feeling of nostalgia for the Slackware 2.0 days) are a deal-killer. </p>
<p>So far Nexenta has been making great progress at delivering Solaris with a Debian/Ubuntu userland - even the liveCD has an environment which is embarrassingly better than Sun&#8217;s shipping S10 install. If Sun has any ambition at recapturing mindshare from Linux they need to put the current Solaris userland on legacy-support and either hire the Nexenta guys or put a full team on producing a modern userland rather than patching the existing one; otherwise they&#8217;re just going to stay in the increasingly small niche of shops which have already invested the time automating the Solaris warts away.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
