Chewy to [email protected] • 3 months agoBooting Linux off of Google Driveersei.netexternal-linkmessage-square27fedilinkarrow-up1316arrow-down14cross-posted to: [email protected][email protected]
arrow-up1312arrow-down1external-linkBooting Linux off of Google Driveersei.netChewy to [email protected] • 3 months agomessage-square27fedilinkcross-posted to: [email protected][email protected]
minus-squareAdrien Jussaklinkfedilink6•3 months ago@Chewy7324 It seems be fun but the latency should be terrible 😅
minus-square@evidenceslink12•3 months agoLatency isn’t the only issue. it’s slow, symbolic and hard linking don’t work correctly, and permissions and attributes aren’t recorded.
minus-squareJolteonlinkfedilink7•3 months agoYou could have a secondary layer that tarred every file on write, since tar maintains permission flags. It could also fix symbolic linking, but not hard linking. As an added benefit, it would drastically reduce the usefulness of the system.
minus-squareqazlink4•edit-23 months agoWhat about using a Google Sheets spreadsheet with the file content encoded in BASE64?
minus-square@[email protected]linkfedilink2•3 months agoYou maniac… What are you gonna do next? Run a cpu in a spreadsheet? Oh wait…
@Chewy7324 It seems be fun but the latency should be terrible 😅
Latency isn’t the only issue.
You could have a secondary layer that tarred every file on write, since tar maintains permission flags. It could also fix symbolic linking, but not hard linking. As an added benefit, it would drastically reduce the usefulness of the system.
What about using a Google Sheets spreadsheet with the file content encoded in BASE64?
You maniac… What are you gonna do next? Run a cpu in a spreadsheet? Oh wait…
Once it all gets to ram, you should be just fine