Language Selection

English French German Italian Portuguese Spanish

Reiser FS: The open source file system fallout

Filed under
Reiser

Yesterday, the Open Source community took an emotional hit when veteran Linux programmer Hans Reiser was convicted of first degree murder in the suspicious disappearing of his wife, Nina. While I won’t go into the details of the case, as this has been covered extensively in the press, I would like to talk a little bit about how this verdict will impact the technology in play for file system dominance in our favorite Open Source operating system, Linux.

While Namesys’ ReiserFS, of which Hans Reiser (right) was the primary programmer and lead designer was not the pre-dominant journaled file system used on Linux systems, it was praised for its stability and performance, and was and still is the default file system on the second most popular enterprise Linux distribution, SuSE Linux Enterprise Server (SLES). ReiserFS was also included in the “upstream” Linux kernel maintained by Linus Torvalds because it shares the same license, GPL version 2. ReiserFS is also popular on Debian-based systems as well.

SuSE and Debian use ReiserFS version 3, a stable and proven version of the code that has been sitting mostly fallow for some time, and is maintained with bug and security fixes on a best effort basis. Prior to the whirlwind and highly publicized trial, Hans Reiser and his small team were working on Reiser4, but much of this development ground to a halt due to his legal woes, and the project is more than likely to die an unfortunate death by virtue of its lead programmer having to serve a minimum 25 year life sentence in prison.

From the SuSE and Debian perspective, this is an obviously unacceptable state of affairs.

More Here




Also:

  • For now, the future of ReiserFS, and its parent company Namesys, remain in jeopardy. Reiser put the company up for sale in December 2006, and as of yet the company is unsold. Namesys employee Alexander Lyamin, writing in the Linux Kernel Mailing List in December 2006, said his company will continue its work absent of Reiser’s leadership, and attempt to appoint a “proxy” to run operations until a better solution could be found. At this time, Namesys’ website is current inaccessible.

    "Misunderstood" programmer receives 25-to-life

  • The few prominent Linux distributions that were still shipping the stable version of ReiserFS by default have shifted to the more common Ext3 for various technical reasons. Reiser4, his next-generation filesystem, has been under active development for some time, but has not been streamlined into the Linux kernel because Linux developers claim that it fails to adhere to coding conventions and has several technical problems.

    Hans Reiser is fscked: jury delivers guilty verdict

  • I don’t know if Hans Reiser, creator of the well-regarded, open-source ReiserFS (Reiser File System), is actually guilty of the murder of his estranged wife, Nina Reiser. We can’t actually even be sure that Nina Reiser was murdered. Her body was never found and Reiser’s attorney argued that she may have returned to her native Russia.

    Never-the-less, as Wired reported, “with no body, no crime scene, no reliable eyewitness and virtually no physical evidence” Hans Reiser was found guilty of first-degree murder. In California, first-degree murder must be “willful, deliberate, and premeditated.”

    I don’t see it.

    Was Reiser really found Guilty of being a Hacker?

  • Computer programmer Hans Reiser was arrogant while testifying in his murder trial and never showed any compassion for his estranged wife, one of many factors that led to his conviction on first-degree murder, a member of the jury said today.

    Reiser juror: "Never showed sympathy" for Nina

ReiserFS

Isn't one of the PRIMARY arguments for OPEN SOURCE suposed to be that it's "Open"?

Since ALL of the source is available, why does the fact that one programmer will no longer be working on it, doom the project?

So much for the great benefit of having ALL the source to prevent being burned by orphaned/abandoned/obsolete projects.

Re: ReiserFS

If you look up the history of ReiserFS, you'll indirectly notice the politics goes a lot into those things.
Even if Hans never got convicted or if reiserfs development continues, Reiser4 will never get integrated into the mainline kernel.

Re: Understanding ReiserFS is easy ? Sql, logs compressed files

atang1 wrote:
So, Hans will have 25 years perhaps in prison with nothing to do but to perfect Reiser4 or v5. However, the problem is that Reiser file system is reaching a dead end. Only defragmentation technology can be picked up to be added in ReiserFS v5.

I doubt they will give him a Linux desktop in jail lol.

A ReiserFS Without Hans Reiser

When an open source project loses one of its core people, it can be tough to pick up the pieces -- not just in terms of replacing that person's programming expertise or insight, but also to restore lost morale. On the plus side, the nature of an open source project does balance things out, if only in an opportunistic fashion.

Patches for the file system are still being submitted, as evinced by the traffic on the reiserfs-devel mailing list, and the folks at kernel.org have offered space to host the ReiserFS sources, giving it that much more of a lease on life. But without Reiser, I suspect ReiserFS itself is doomed -- or is at least due for a name change.

More Here

And: Reiser to be sentenced in July

ReiserFS project death

Does the survival and development of the Reiser FS really matter? With the stability of ext3, XFS, and JFS, and the promised scalability of the developing ext4 and Btrfs, neither Reiser3 or Reiser4 seem needed.

I'm certainly no expert on file systems, but I found a filesystem partitioning combo years ago that has been extremely reliable for me, which does not include a Reiser FS partition.

Reiser4 might have become a great Linux filesystem, but so might others.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Security Leftovers

  • Security updates for Monday
  • Recursive DNS Server Fingerprint Problem

    Our goal is to identify hijacked resolvers by analyzing their fingerprints, in order to increase safety of Internet users. To do that, we utilize data collected via RIPE Atlas (atlas.ripe.net).

  • Online developer tutorials are spreading XSS and SQL injection flaws

    The researchers, from across three universities in Germany and Trend Micro, checked the PHP code bases of more than 64,000 projects on Github and uncovered more than 100 vulnerabilities that they believe might have been introduced as a result of developers picking up the code that they used from online tutorials.

  • BrickerBot, the permanent denial-of-service botnet, is back with a vengeance

    BrickerBot, the botnet that permanently incapacitates poorly secured Internet of Things devices before they can be conscripted into Internet-crippling denial-of-service armies, is back with a new squadron of foot soldiers armed with a meaner arsenal of weapons.

  • Reproducible Builds: week 104 in Stretch cycle
  • Webroot antivirus goes bananas, starts trashing Windows system files
    Webroot's security tools went berserk today, mislabeling key Microsoft Windows system files as malicious and temporarily removing them – knackering PCs in the process. Not only were people's individual copies of the antivirus suite going haywire, but also business editions and installations run by managed service providers (MSPs), meaning companies and organizations relying on the software were hit by the cockup. Between 1200 and 1500 MST (1800 and 2100 UTC) today, Webroot's gear labeled Windows operating system data as W32.Trojan.Gen – generic-Trojan-infected files, in other words – and moved them into quarantine, rendering affected computers unstable. Files digitally signed by Microsoft were whisked away – but, luckily, not all of them, leaving enough of the OS behind to reboot and restore the quarantined resources.
  • How The Update Framework Improves Security of Software Updates
    Updating software is one of the most important ways to keep users and organizations secure. But how can software be updated securely? That's the challenge that The Update Framework (TUF) aims to solve. Justin Cappos, assistant professor at New York University, detailed how TUF works and what's coming to further improve the secure updating approach in a session at last week's DockerCon 17 conference in Austin, Texas. Simply using HTTPS and Transport Layer Security (TLS) to secure a download isn't enough as there have been many publicly reported instances of software repositories that have been tampered with, Cappos said.
  • Security Updates for Ubuntu Phone to End in June
    Security updates for Ubuntu phone and tablet will end this June, Canonical has confirmed. Current OTA updates are currently limited to critical fixes and security updates — a decision we were first to tell you back in January. But after June 2017 Canonical “will no longer deliver any further updates”.
  • Canonical to stop supporting Ubuntu Phone in June
    Canonical had already announced development of its Ubuntu Phone software was ending. Now we know when the final nail goes in the coffin: June.
  • Malware Hunts And Kills Poorly Secured Internet Of Things Devices Before They Can Be Integrated Into Botnets
    Researchers say they've discovered a new wave of malware with one purpose: to disable poorly secured routers and internet of things devices before they can be compromised and integrated into botnets. We've often noted how internet-of-broken-things devices ("smart" doorbells, fridges, video cameras, etc.) have such flimsy security that they're often hacked and integrated into botnets in just a matter of seconds after being connected to the internet. These devices are then quickly integrated into botnets that have been responsible for some of the worst DDoS attacks we've ever seen (including last October's attack on DYN).

GNOME/GTK News

  • The Way GNOME Handles Wallpapers Really Annoys Me
    I love GNOME Shell — and no, not just because I’ve little choice now that is Ubuntu’s default desktop! But the more I use GNOME the more I learn that the desktop environment, like every other, has its own share of quirks, bugs and inconsistencies. Like the following appreciably niche niggle in the the way GNOME handles desktop wallpapers.
  • Drag-and-drop in lists
    I’ve recently had an occasion to implement reordering of a GtkListBox via drag-and-drop (DND). It was not that complicated. Since I haven’t seen drag-and-drop used much with list boxes, here is a quick summary of what is needed to get the basics working.

Containers News

  • How Kubernetes is making contributing easy
    As the program manager of the Kubernetes community at Google, Sarah Novotny has years of experience in open source communities including MySQL and NGINX. Sarah sat down with me at CloudNativeCon in Berlin at the end of March to discuss both the Kubernetes community and open source communities more broadly. Among the topics we covered in the podcast were the challenges inherent in shifting from a company-led project to a community-led one, principles that can lead to more successful communities, and how to structure decision-making.
  • How Microsoft helped Docker with LinuxKit and Moby Project [Ed: Microsoft 'helped'... embrace, extend, coerce; haven't Docker employees learned from history?]
    Today, supporting Linux is as critical to Microsoft as it is to Red Hat and SUSE.
  • How to make branding decisions in an open community
    On April 18, Docker founder Solomon Hykes made a big announcement via a pull request in the main Docker repo: "Docker is transitioning all of its open source collaborations to the Moby project going forward." The docker/docker repo now redirects to moby/moby, and Solomon's pull request updates the README and logo for the project to match. Reaction from the Docker community has been overwhelmingly negative. As of this writing, the Moby pull request has garnered 7 upvotes and 110 downvotes on GitHub. The Docker community is understandably frustrated by this opaque announcement of a fait accompli, an important decision that a hidden inner circle made behind closed doors. It's a textbook case of "Why wasn't I consulted?"

Ubuntu 17.04: Unity's swan song?

For the most part, not much has changed on Ubuntu's Desktop edition in the past year. Unity 7 has more or less remained the same while work was progressing on the next version of the desktop, Unity 8. However, now that both desktops are being retired in favour of the GNOME desktop, running Ubuntu 17.04 feels a bit strange. This week I was running software that has probably reached the end of its life and this version of Ubuntu will only be supported for nine months. I could probably get the same desktop experience and most of the same hardware support running Ubuntu 16.04 and get security updates through to 2021 in the bargain. In short, I don't think Ubuntu 17.04 offers users anything significant over last year's 16.04 LTS release and it will be retired sooner. That being said, I could not help but be a little wistful about using Unity 7 again. Even though it has been about a year since I last used Unity, I quickly fell back into the routine and I was once more reminded how pleasant it can be to use Unity. The desktop is geared almost perfectly to my workflow and the controls are set up in a way that reduces my mouse usage to almost nothing. I find Unity a very comfortable desktop to use, especially when application menus have been moved from the top panel to inside their own windows. While there are some projects trying to carry on development of Unity, this release of Ubuntu feels like Unity's swan song and I have greatly enjoyed using the desktop this week. While there is not much new in Ubuntu 17.04, the release is pretty solid. Apart from the confusion that may arise from having three different package managers, I found Ubuntu to be capable, fairly newcomer friendly and stable. Everything worked well for me, at least on physical hardware. Unity is a bit slow to use in a virtual machine, but the distribution worked smoothly on my desktop computer. Read more