In the past, I saw that kubo ipfs did not work as a read-only (RO) filesystem as-is. I speculated that IPFS could work as an RO FS if the read-write (RW) parts of it were operating in an RW-enabled device. I recently found did that; how-to: 1. Have two repos (see also $IPFS_PATH): one is in a RO device and another is in a RW device. 2. Rename folder "blocks" in RW to "blocks_" then create an empty folder named "blocks". 3. Use xargs and stuff to automatically symlink each folder in RO blocks/ to RW blocks/. 4. Copy RO datastore/* to RW datastore/ and don't overwrite any files.
Then it works (it needs RW on at least one file which I think is "repo.lock"), and it's only missing MFS and pins list in RO. What could have I done better or differently? Answer - simply symlinking like this: "$ ln -s /ro/repo/blocks /rw/repo/blocks # ln -s TARGET LINK_NAME".
>>10306 >Ron-Someone Algorithm = "cryptographically weak" Butchered that from memory. Trying again from more recent refresher: Ron Rivest + [Fname] Simir + [Fname] Adleman = Rivest-Simir-Adleman algorithm/cryptosystem which is worryingly weak and inferior to AES-256 encryption. "ed25519" is probably also better than RSA.
>>10310 Before I had this one 64-bit computer die on me, I was more able to rip and burn CDs and DVDs. I think I can still burn a CD or DVD for 32-bit Debian, but it would be more of a hassle than before.