3 ms·
> Moreover, the Finder had to maintain the catalog in RAM to keep track of folders, which were illusory. The Macintosh File System was not a true hierarchical s
by jauntywundrkind 3y ago
> Moreover, the Finder had to maintain the catalog in RAM to keep track of folders, which were illusory. The Macintosh File System was not a true hierarchical system; it only appeared to be in the Finder. Folders in fact were kept as "Finder Objects" in the Desktop file.
That is so frigging cool. JBOF, just a bunch of files. The data about structure being not the responsibility, it being a flat file store.
I'm curious how something like Ceph bluestore works, what it's design is. There's metadata nodes here too I think, it's some kind of dumb-ish blockstore, for limited size blocks.
- sillywalk 3y agoMy 5 minute dunning-kruger level look up: Bluestore is used to directly access raw storage without the overhead of a filesystem. [1][2] "BlueStore uses the RocksDB’ key-value database to manage internal metadata, such as the mapping from object names to block locations on a disk. [0] [0] https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/administration_guide/osd-bluestore https://access.redhat.com/documentation/en-us/red_hat_ceph_s... [1] https://blog.acolyer.org/2019/11/06/ceph-evolution/ https://blog.acolyer.org/2019/11/06/ceph-evolution/ [2] https://events.static.linuxfound.org/sites/events/files/slides/20170323%20bluestore.pdf https://events.static.linuxfound.org/sites/events/files/slid...
- 13of40 3y agoThat's the way PKZip archives work. The directory is just stored as part of the filename. It's a little bit of a pain because it uses / as the separator character and a lot of Windows zip APIs will "fix" that for you, so there's a difference between what you get from the API versus what's actually stored in the archive entry record in the file. On the other end of the spectrum is the Amiga file system, where every file entry has an entire sector of metadata, and a directory is a linked list of those sectors.
- malkia 3y agoOn Apple ][ (/e, /c, etc.) there was some non-standard DOS version (I don't think it was ProDOS, but something else) that was first geared towards using the 80 column mode (PR#3), but then it had the notion of directories.... but it was still storing everything in one big "flat" list, though each "file/dir" would have a parent index, so "cd someDir" and then "dir" would (I guess) just allow files that have in their parent_id as that dir. But after all, that's how you did any kind of "pointer" programming in language without pointers (like Apple Basic which was my first language) - you'll store things in array, and use indices (much like Databases)... Maybe it's somewhere in archive.org...
- buildbot 3y agoRight? It's actually to my mind a more advanced design than HFS - just store stuff, including the imaginary hierarchy of folders that might go with the stuff. Then, you could programmatically make new folders based on a query of a set of file metadata if you wanted. So many nice possibilities open up.