1. 20
  1. 4

    Always wondered who it was named after.


    Hans Thomas Reiser (born December 19, 1963) is an American computer programmer, entrepreneur, and convicted murderer.

    Cancel my meetings I’ve got some reading to do

    1. 12

      Yep. Perfect example of “well that escalated quickly.”

      I remember when it was in the news. I was sure Hans was innocent, given that one of his victim’s ex-boyfriends had already been in jail for murdering someone. I was genuinely shocked when he was found guilty and took the police to where he buried the body.

      Wired did a really good write up of it at the time.

      1. 7

        I actually had dinner with him a few months before the murder & I remember him ranting about his wife a lot at the time so I wasn’t that surprised.

        1. 10

          Also one of the early attempts the “geek defense” by framing himself as Asperger’s, throwing other autists under the bus with it. :/

          1. 4

            I was working at a startup that was using ReiserFS at the time, and he was doing contract work for us. I never met the dude, but it was very unsettling to be that close to the story.

          2. 1

            Yup! Kinda bizarre. I posted this excerpt several years ago:

            Reiser4 has a somewhat uncertain future. It has not yet been accepted into the main line Linux kernel, the lead designer is in prison, and the company developing it is not currently in business.


            1. 1

              There are a number of crime dramas about this as well.


              1. 1

                Oh you need to catch up to the Reiser4 FS story as well. Good readings.

              2. 2

                Interesting detail on resierfs(3) and nicely presented. I figured there would be a tie-in to resier4 but there is not.

                1. 2

                  I ran reiserfs(3) back in the day (when the reasonable choices on Linux were ext2 or reiserfs, and reiser had much better performance. The main issue I had with it was reiserfsck. Being a journaled FS, fsck was required far less often than it was for ext2. But when you did need it… well, usually you would go into it having one file or directory that would throw I/O errors when you tried to access it, and by the time fsck was done you would have tens of thousands of files in lost+found and no hope of ever doing anything useful with that FS again. Hope you took the advice to make a backup before fsck seriously.