Chewy to Linux@lemmy.ml · 5 months agoBooting Linux off of Google Driveersei.netexternal-linkmessage-square27fedilinkarrow-up1323arrow-down13cross-posted to: linux@programming.devlinux@programming.devhackernews@lemmy.smeargle.fans
arrow-up1320arrow-down1external-linkBooting Linux off of Google Driveersei.netChewy to Linux@lemmy.ml · 5 months agomessage-square27fedilinkcross-posted to: linux@programming.devlinux@programming.devhackernews@lemmy.smeargle.fans
minus-squareevidences@lemmy.worldlinkfedilinkarrow-up11·5 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-squareJolteon@lemmy.ziplinkfedilinkarrow-up7·5 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-squareqaz@lemmy.worldlinkfedilinkarrow-up4·edit-25 months agoWhat about using a Google Sheets spreadsheet with the file content encoded in BASE64?
minus-squareobject [Object]@lemmy.blahaj.zonelinkfedilinkarrow-up2·5 months 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…