Chewy@discuss.tchncs.de to Linux@lemmy.ml · 12 days agoBooting Linux off of Google Driveersei.netexternal-linkmessage-square27fedilinkarrow-up1322arrow-down13
arrow-up1319arrow-down1external-linkBooting Linux off of Google Driveersei.netChewy@discuss.tchncs.de to Linux@lemmy.ml · 12 days agomessage-square27fedilink
minus-squareevidences@lemmy.worldlinkfedilinkarrow-up12·11 days 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-squareJolteon@lemmy.ziplinkfedilinkarrow-up8·11 days 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-squareqaz@lemmy.worldlinkfedilinkarrow-up4·edit-211 days agoWhat about using a Google Sheets spreadsheet with the file content encoded in BASE64?
minus-squareSparky@lemmy.blahaj.zonelinkfedilinkarrow-up2·10 days agoYou maniac… What are you gonna do next? Run a cpu in a spreadsheet? Oh wait…
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…