Chewy@discuss.tchncs.de to Linux@lemmy.ml · 10 个月前Booting Linux off of Google Driveersei.netexternal-linkmessage-square22fedilinkarrow-up1309cross-posted to: linux@programming.devlinux@programming.devhackernews@lemmy.smeargle.fans
arrow-up1309external-linkBooting Linux off of Google Driveersei.netChewy@discuss.tchncs.de to Linux@lemmy.ml · 10 个月前message-square22fedilinkcross-posted to: linux@programming.devlinux@programming.devhackernews@lemmy.smeargle.fans
minus-squareAdrien Jussak@piaille.frlinkfedilinkarrow-up7·10 个月前@Chewy7324 It seems be fun but the latency should be terrible 😅
minus-squareevidences@lemmy.worldlinkfedilinkarrow-up10·10 个月前Latency 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·10 个月前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.
minus-squareqaz@lemmy.worldlinkfedilinkarrow-up4·edit-210 个月前What about using a Google Sheets spreadsheet with the file content encoded in BASE64?
minus-squareSparkylinkfedilinkarrow-up2·9 个月前You maniac… What are you gonna do next? Run a cpu in a spreadsheet? Oh wait…
minus-squareferret@sh.itjust.workslinkfedilinkEnglisharrow-up5·10 个月前Once it all gets to ram, you should be just fine
@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