Hans Reiser, the creator of ReiserFS, talked about the deprecation of ReiserFS in the Linux kernel

ReiserFS

ReiserFS is a general purpose file system

Recently Frederick Brennan shared one of the letters he received from Hans Reiser, the creator of the ReiserFS file system, in which he talked about the deprecation of ReiserFS V3 in the Linux kernel.

In published letters, Hans regrets his mistakes when interacting with the community of developers, analyzes the deprecation of ReiserFS v3 in the Linux 6.6 kernel, analyzes the history of the development of ReiserFS, mentions the hopes associated with the promotion of ReiserFS v4 and explains some technical solutions implemented in ReiserFS v4.

For those who do not know about Hans Reiser, you should know that he is the creator of the ReiserFS file system and who in 2008 was sentenced to life in prison for the murder of his wife as a result of a fight with a subsequent attempt to cover up the crime. (In 2027, Hans will be able to apply for parole.)

Greetings LKML.

The following is a letter from Hans Reiser to me, which he wrote about two months ago and asked me to publish, with his thoughts on ReiserFS's deprecation of the Linux kernel. I have transcribed it to the best of my ability.

Hans Reiser shared his views on ReiserFS V3 removal of the Linux Kernel In the following letter addressing the decision to remove ReiserFS from the kernel, Hans highlights that the continued usefulness of this file system and its inclusion in the kernel should be decided by users and maintainers, taking into account current realities .

In addition to that, recognizes that keeping ReiserFS code in the kernel is an additional burden for maintainers, who must test and ensure compatibility with new kernel features. If ReiserFS is no longer relevant, there is no point in maintaining it as part of the Kernel. Although During the development of ReiserFS v4 many shortcomings were addressed of version 3 and maintenance was simplified, this version was never accepted in the kernel.

ReiserFS 4 provides a more maintainable foundation for the future for those
users who like the features of V3. If V3 is not used, it should disappear, i
rely on users and kernel maintainers to discuss whether it is
used and make the right decision together.

Hans makes a single request: add a README file to accompany the ReiserFS code before its removal from the kernel. In this README, mentions Mikhail Gilulu, Konstantin Shvachko and Anatoly Pinchuk, whose contributions to development were underestimated.

These developers They were hired by Hans and contributed to the development of ReiserFS. However, due to Hans' demanding nature and his expectations unrealistic (I worked around the clock and expected the same level of enthusiasm from others), They abandoned the project. Although Hans initially perceived this as a betrayal, over time he realized that his decision was justified under the circumstances.

And the letter mentions that the development ofe Reiser v4 was not without difficulties and personal challenges. Hans Reiser reflects on his experience and acknowledges the mistakes made along the way. From lack of effective communication to resistance to change, Hans Reiser shares lessons learned and areas where he could have acted differently.

One of the most important lessons What Hans Reiser highlights is the importance of collaboration and communication in software development. Recognizes the need to overcome initial hostility and cultivate positive relationships with the development community.

Despite challenges and controversies, Reiser v4's legacy lives on as a testament to the power of innovation and determination. Its modular architecture and focus on efficiency and flexibility continue to be sources of inspiration for file system developers.

Finally, if you are interested in knowing more about it, you can check the details of the letter In the following link.