rchase wrote: ↑10 Aug 2020, 19:59
donald wrote: ↑10 Aug 2020, 19:43
@ rchase
The radio button "Save sessions for future logins"
should save open windows
so they do re-appear after a reboot.
Those sessions are stored in ~/.cache/sessions/ and have nothing to do with changes
you make to the system.
also the changes=EXIT or changes-ro cheatcode might be of some interest.
I'd like an answer to my several questions -- with respect to how Porteus makes changes, why is the /changes folder written at boot? It must incorporate changes made by the loading of packages as well as changes I make to my desktop, else why does networking fail the instant I attempt to use persistence, having done nothing else? I've verified that I have network access under Porteus 5.0rc2 with or without using the new kernel; how do I proceed to configure my desktop and make changes persistent? The "change-ro" cheatcode is of zero relevance, so far as I can see; networking breaks because I am trying to save changes -- I'm not repeatedly breaking Porteus doing something else and need to hold off committing changes!
Porteus doesn't write to the changes folder at boot. There's nothing to write at boot as nothing has been done to create changes. If networking fails when you try to use persistence that indicates that there's something wrong with previous changes that are in the folder. If you see an empty changes folder after booting in Always Fresh, that's because it's part of the files in the ISO, it's not created at boot.
The method you're using for saving changes to a partition is fine. It will save everything that changes
when it changes, it needs no input from the user. But, it will save all changes, good or bad, it has no way of determining which is which.
You mentioned that you were able to boot and get network access, I'd suggest you do that, in Always Fresh mode, get things the way you want them. Then delete any change folders that may be in place, and copy the changes folder in /mnt/live/memory to the partition you want to save on. If that doesn't work, then I have no idea what's happening.
I downloaded rc2, set up the command line for changes and it works fine here. It works as it always has.