(* yes, this is my first entry; going to try using this hashtag as a way of quickly making notes which I can file properly later, and maybe get help with issues)
@libc That is indeed an interesting article, with a few ideas I hadn't thought of.
One comment, though -- it lists this as a "lost feature":
Directory entries that point to secondary storage
The only difference I can see between that and mountpoints is that they're used more extensively and creatively... and it may be that "secondary storage" can refer to volumes that are currently offline, which is definitely a feature I've been wanting since the earliest root of this idea (when I was just thinking of it as a catalogue application).
The correction email at the end confirms this:
Multics didn't do what you describe. There was a mechanism, very like Unix mount points, for "master directories" whose subtree was mounted on a removable disk pack.
Also, regarding the labeling system in Alto -- I have to wonder if the hardware in modern SATA drives is still actually using powers-of-two-sized blocks under the hood, or just emulating them because that's what modern OSs expect.
HYDRA's operations management sounds not unlike what I had in mind with structure-templates.
I hadn't originally intended to go digging into lower-level filesystem details, but this article makes me think that it would definitely be worth doing in the long run, if what I have in mind is at all successful.
Thanks for an interesting read!
@woozle I am curious about this stuff, because once upon a time I tried to start learning how to use Linux music programs and I couldn't make heads or tails of any of it. This was many years ago, though.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!