Commentary

Serdar Yegulalp
 

SkyOS's Linux Experiment

I've been writing on and off about using the Linux kernel as a base for OS projects with closed but stable and centrally architected designs. Here's such an experiment already in progress: SkyOS.

I've been writing on and off about using the Linux kernel as a base for OS projects with closed but stable and centrally architected designs. Here's such an experiment already in progress: SkyOS.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

SkyOS -- a desktop OS platform, albeit a closed-source one -- had been under development for a while now. It looked quite nice, although it was only available to a limited selection of alpha-testers. Then as of January, things ground to a halt. "The speed at which new hardware and technology gets developed has increased dramatically in the last few years," wrote SkyOS's main developer, Robert Szeleney. "Trying to catch up with development of frameworks, drivers, applications, test, etc. got way more complicated than years ago."

As of early this week though, Robert started experimenting with the possibility of leveraging Linux or BSD as the core for the system, with his proprietary front-end still in place. That would save him the trouble of having to re-develop all of the hardware support needed for a desktop environment, and give him a whole slew of other goodies he'd never had time to develop in the first place.

Good luck to him. Let's see where this heads; it might be an interesting model for others to watch.

InformationWeek Analytics has published an independent analysis of the current state of open source adoption. Download the report here (registration required).

Follow me and the rest of InformationWeek on Twitter.


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