Star Wars theme: https://youtu.be/3KS02q0BUnY
I Wat to Break Free: https://youtu.be/lbd06i9B2wU
basically system memory size vs block device size was the opposite way around of today... then again people could and did have many individual floppy disks.
Luckily, the gen 7 tapes are 10-100 times that large, depending on who you ask. Each disk costs approximately $2-$5 as well, assuming you get some sort of discount. Tapes are more, they hold more, but at a certain point having a disc in a jewel case is better than having some tape. bluray drives are easy to find, tape readers, not so much.
I don’t think those are actually several TB. They’re fakes that are advertised as having several TB.
Portable flash drives using M.2 drives internally could reasonably be up to 8TB, but being at the high end they're expensive.
If i hadn't seen it myself i would have wondered why it wasn't already possible already.
I can imagine many programs doing this though.
As another example You could easily make RAM disks via a desktop menu, to facilitate the common setup of a single built in floppy drive. So you could copy files off into RAM via the GEM desktop GUI (literally drag and drop) and then put another disk in etc.
Random aside: I accidentally found that this machine would transmit audio over FM radio for a short but very useful range automatically.. blew my mind as a kid. I could never find anything official about this online later so not sure if it was an intentional design, poor EM design of the audio chip, or a hack of my particular 2nd hand franken-tari - either way it was super useful to have wireless audio in the 90s.
The ”FM” officially stands for Floppy & (RF) Modulator, but that’s some coincidence that the audio chip emits frequency modulated radio waves at a listenable frequency.
Every time you reboot, it will repair the array.
It seems necessary that the blocks storing the directory entries are cached too. Otherwise every non-existent lookup (that doesn't hit a negative dentry) would hit disk, each separately.
So yeah, the page cache is keyed by file, but the system should still cache the directory structure.
The DDoS scenario would be doing GET requests of random nonexistent filenames. You could change the name at every step so that the check for a negative dentry is never a cache hit.
Also the page/buffer cache would probably cache the FAT direntries so probably not a huge issue here.
edit: thinking about it, there's some good educational value, but maybe via vm than plopped on the interwebs :D