Commentary

Serdar Yegulalp
 

ReiserFS Without Hans Reiser, Continued

In my post the other day about whether or not work in the ReiserFS file system would continue after Hans Reiser's murder conviction, I mentioned that this being an open source project, it wouldn't be hard for someone else to pick up where others leave off.  And as it turns out, that's precisely what's happening: according to folks on the ReiserFS team, work on ReiserFS will continue.

In my post the other day about whether or not work in the ReiserFS file system would continue after Hans Reiser's murder conviction, I mentioned that this being an open source project, it wouldn't be hard for someone else to pick up where others leave off.  And as it turns out, that's precisely what's happening: according to folks on the ReiserFS team, work on ReiserFS will continue.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Earlier today I was contacted by Alexander Lymin and Edward Shishkin, two of the developers on the ReiserFS team.  Alex wanted to make it clear that "there is no need for drama" -- that work on ReiserFS hasn't stopped, even if they don't have the kind of resources they would like right now.

Alex echoed my point about picking up where others left off in his own words: "Perhaps the single strongest property of open source software is 'distributed reliability'; i.e., if one company/person fails, there are 10 others to pick up the banner."  I'll add that while such a thing is not guaranteed, it's made that much easier, which is itself sometimes half the battle.

From what I've seen, ReiserFS (specifically, the newest iteration named Reiser4) is too good a project to abandon.  Many people use the earlier ReiserFS in a daily context and swear by it, and many improvements to the system are planned for version 4.  It's good to hear that work will continue, even if not at the pace it was happening before -- and perhaps in time one of the more aggressive Linux development outfits (IBM, Red Hat) can help out, too.


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