Chewy@discuss.tchncs.de to Linux@lemmy.ml · 1 year agoBooting Linux off of Google Driveersei.netexternal-linkmessage-square21linkfedilinkarrow-up1247arrow-down12
arrow-up1245arrow-down1external-linkBooting Linux off of Google Driveersei.netChewy@discuss.tchncs.de to Linux@lemmy.ml · 1 year agomessage-square21linkfedilink
minus-squareAdrien Jussak@piaille.frlinkfedilinkarrow-up6·1 year ago@Chewy7324 It seems be fun but the latency should be terrible 😅
minus-squareevidences@lemmy.worldlinkfedilinkarrow-up10·1 year 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·1 year 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-up2·edit-21 year agoWhat about using a Google Sheets spreadsheet with the file content encoded in BASE64?
minus-squareferret@sh.itjust.workslinkfedilinkEnglisharrow-up5·1 year agoOnce 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?
Once it all gets to ram, you should be just fine