1. 31
  1.  

  2. 16

    It was mentioned in the article, but in case you missed it: the architect of the BeOS filesystem, Dominic Giampaolo, published a book describing the system called Practical Filesystem Design. He has since released the book for free, available here.

    I still have my dead-tree version from years ago. It’s a fantastic, well-written work.

    1. 2

      I was going to say “And now works at Apple” but Wikipedia page indicates he worked on a number of neat things. Including Silicon Graphics' InfiniteReality systems.

      https://en.wikipedia.org/wiki/Dominic_Giampaolo

      1. 2

        This book was the textbook for my university file systems class (which, unfortunately, my university no longer offers, having replaced it with a second operating systems class). It’s definitely a solid and well-written book. Wish I had a physical copy!

      2. 12

        Haiku, the open-source reimplementation of BeOS (including BFS) mentioned in this article, is still under heavy, active development. If you’re bored, I’d strongly recommend giving it a shot. They’ve got some wonderfully interesting ideas (e.g., their packaging system leaves bundles as a single file, but makes their contents show up virtually in the file system, meaning they’re easy to install/remove and inspect), while still preserving all the stuff that made BeOS great (spatial Tracker, saved queries, etc.). I’ve been enjoying playing with it on and off for the past couple weeks in a pique of retrocomputing. It’s kind of funny how ridiculously fast it is compared to a more modern OS in a lot of ways—though as a warning, writing apps for it will remind you how that was achieved. (It’s also reminded me why, while I’ve mostly made peace with C++14, I still really hate the C++ of the mid 90s, but that’s for another day.)

        1. 1

          The history of file systems article linked in the article is pretty fascinating as well