Commentary

Serdar Yegulalp
 

Xandros and Linspire: The Real Value Of The Deal

The Linux world's been abuzz the last couple of days with the news that Xandros has acquired Linspire, with future plans for the latter still rather sketchy. One particular technology stands out in Linspire's portfolio, though: CNR, a "one-click delivery system" for software.

The Linux world's been abuzz the last couple of days with the news that Xandros has acquired Linspire, with future plans for the latter still rather sketchy. One particular technology stands out in Linspire's portfolio, though: CNR, a "one-click delivery system" for software.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

CNR -- short for Click'N'Run -- packages Linux software in a standardized way to make it easier for programs to be installed and used in Linux. Granted, most of the way we get our software for a given distro is through that distro's repository, but installing apps not in the repository can be a crapshoot. I've tangled, and lost, with this particular gremlin a couple of times. So anything to make that process a little less ornery is welcome, even if programs have to be repackaged through CNR to work in the first place.

In a statement released Tuesday, Xandros CEO Andreas Typaldos stated, "Integration of CNR and the Xandros Networks on Xandros and other platforms will be launched shortly," which to me sounds like CNR eventually will be available for products like the Asus Eee PC (which runs a variant of Xandros out of the box) -- and, presumably, any other future installations of Xandros as well. CNR clients exist for many major Linux distributions, so this isn't something limited to Xandros and Linspire, either.

So maybe this is the real value of the Xandros/Linspire deal: a humane package manager, a way to install external software in Linux that doesn't scare off the uninitiated. I still like the idea of everything-in-the-repository for the sake of consistency, but the more possibilities we have on the table, the better.


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