11-13-2020, 01:56 PM
Please read the whole post because I approach this from several angles:
I'm trying to figure out how to do something and I have a few related questions. I want to be able to make a live Linux that will persist, but then I can set it to use the persistence file as read-only, so that it will still keep all the changes that I've made to that point, but not make any new ones, so I can save on wear and tear for my USB stick, and lock in the settings that I want.
First of all, when exactly does Ventoy update its persistence file - during shutdown or at any arbitrary time? So if I yank the USB drive before shutting down then will that prevent it from writing?
But more importantly, how can I make the file read-only, so that once I have it all set up the way that I want it, I can prevent further changes, and also save on wear and tear for my USB stick? Is there some line I can put into the .json file to just prevent it from writing anything to the drive?
I've tried disabling persistence in the .json file but that seems to ignore the file completely, thus reverting everything to defaults, but I need to be able to read and use the customizations that I've made. And I've also tried making the persistence file itself read-only (I disabled all write capabilities for all users), but it still somehow keeps updating, without even changing the date modified information!
Alternatively, is there a way that I can take all of the data in the persistence file and just put that into the ISO itself, to update it and build a new ISO or modify the existing one, so that I can just boot from that and turn off persistence?
And if none of this stuff is possible then PLEASE consider making an update for a new .json parameter to make persistence read-only! It should be very easy to implement - just use whatever function is for writing to the drive and make it conditional. I even tried looking into the source code myself but there are so many files and folders that I can't figure out how to fix it, much less how to even compile it so that I can redeploy it onto a USB stick (I'm new to Linux, btw).
I'm trying to figure out how to do something and I have a few related questions. I want to be able to make a live Linux that will persist, but then I can set it to use the persistence file as read-only, so that it will still keep all the changes that I've made to that point, but not make any new ones, so I can save on wear and tear for my USB stick, and lock in the settings that I want.
First of all, when exactly does Ventoy update its persistence file - during shutdown or at any arbitrary time? So if I yank the USB drive before shutting down then will that prevent it from writing?
But more importantly, how can I make the file read-only, so that once I have it all set up the way that I want it, I can prevent further changes, and also save on wear and tear for my USB stick? Is there some line I can put into the .json file to just prevent it from writing anything to the drive?
I've tried disabling persistence in the .json file but that seems to ignore the file completely, thus reverting everything to defaults, but I need to be able to read and use the customizations that I've made. And I've also tried making the persistence file itself read-only (I disabled all write capabilities for all users), but it still somehow keeps updating, without even changing the date modified information!
Alternatively, is there a way that I can take all of the data in the persistence file and just put that into the ISO itself, to update it and build a new ISO or modify the existing one, so that I can just boot from that and turn off persistence?
And if none of this stuff is possible then PLEASE consider making an update for a new .json parameter to make persistence read-only! It should be very easy to implement - just use whatever function is for writing to the drive and make it conditional. I even tried looking into the source code myself but there are so many files and folders that I can't figure out how to fix it, much less how to even compile it so that I can redeploy it onto a USB stick (I'm new to Linux, btw).