Language Selection

English French German Italian Portuguese Spanish

Death of a filesystem (?)

Filed under
Reiser

Over the last months there were repeating news about the murder on Nina Reiser by her husband Hans Reiser, known in the community for his work on his filesystems ReiserFS and Reiser4.

In this post I don't want to deal with the murder, the process or the conviction, there are lots of news and posts about this all over the net, and in at least some cases written by people who are a lot more competent in that field than I am.

What I want to deal with here are the consequences of this "story" that may be in store for Reiser's filesystems.

ReiserFS seems to have caused quite a few heated discussions on the Linux Kernel Mailing List (Archive: http://www.lkml.org). Obviously enough that Hans Reiser sees the main reason for Reiser4 not being transferred into the main kernel-tree in people simply not liking him.

How much of this is true or not shall not be matter of this post, and anyway I am not in the position to judge about this. But it seems to be quite a fact that Reiser didn't make himself very popular with the code he submitted. The problem was, as far as I remember, that it was written without following any kernel-coding-standards.

More Here




More in Tux Machines

Red Hat News

Development News: LLVM, New Releases, and GCC

PulseAudio 10 and Virtual GPU in Linux

  • PulseAudio 10 Coming Soon, Using Memfd Shared Memory By Default
    It's been a half year since the debut of PulseAudio 9.0 while the release of PulseAudio 10 is coming soon. PulseAudio 9.99.1 development release was tagged earlier this month, then usually after x.99.2 marks the official release, so it won't be much longer now before seeing PulseAudio 10.0 begin to appear in Linux distributions.
  • Experimenting With Virtual GPU Support On Linux 4.10 + Libvirt
    With the Linux 4.10 kernel having initial but limited Intel Graphics Virtualization Tech support, you can begin playing with the experimental virtual GPU support using the upstream kernel and libvirt.

Licensing FUD and Licensing Advice

  • On the Law and Your Open Source License [Ed: Black Duck is just a parasite selling proprietary software by bashing FOSS]
    "Looking back five or ten years, companies managing open source risk were squarely focused on license risk associated with complying with open source licenses," notes a report from Black Duck Software. Fast-forward to today, and the rules and processes surrounding open source licensing are more complex than ever.
  • Explaining the source code requirement in AGPLv3
    This condition was intended to apply mainly to what would now be considered SaaS deployments, although the reach of "interacting remotely through a computer network" should perhaps be read to cover situations going beyond conventional SaaS. The objective was to close a perceived loophole in the ordinary GPL in environments where users make use of functionality provided as a web service, but no distribution of the code providing the functionality occurs. Hence, Section 13 provides an additional source code disclosure requirement beyond the object code distribution triggered requirement contained in GPLv2 Section 3 and GPLv3 and AGPLv3 Section 6.