Anonymous
—If theoretically regular files and directories can also be supported, what difference would there be with persistence mode? Even assuming savestate is seemingly thought for “smaller saves”.
—There are “general” and “machine” state config files. But, how to configure the “user” part? It currently just copies automount.conf and default-desktop both from ~/.desktop-session.
(And how does default.desktop work? At boot it doesn’t really follow the set “default desktop”…)
My response here would be phrased differently if you had described “what you are trying to accomplish yet have not found a way to do so”
No, savestate is not intended for “smaller saves”. It accomplishes “general” and “machine” state saves; independent of persistence, it preserves alsa sound settings, network settings, across reboots (and/or if it detects that boot is occuring on a different, aka not previously seen, machine). Bear in mind: during each liveboot, we have the opportunity to invoke persistence (or not) for the current boot session. If persistence is selected, per–user saved details are saved within the rootfs file or homefs file (depending on the currently-selected persistence mode), and are only referenced later if/when the relevant persistence mode has again been selected.
To fully understand the nitty-gritty details of how savestate works and/or to tweak its functionality,
you would need to unpack the initrd.gz and refer to the save_state() and restore_state() functions within the script /etc/init.d/liveusb-save
^— The hyperlink points to a viewable copy of the script (perhaps not up-to-date with that found in antiX 21) residing in the antiX live-initrd.gz sourcecode repository at gitlab
someway of specifying which device the savestate config files are in ?
The expected paths of the state files are hardcoded (are unaffected by use of the bdir= boot parameter).
- This reply was modified 4 years, 7 months ago by Brian Masinick. Reason: From skidoo