Currently the default persist-save mode is semi-automatic which was chosen due to an abundance of caution.

1. Would it be better to make the default"automatic"?
2. Should we still ask the user to select the mode the first time they have enabled root persistence?
3. Should we still ask the user to select the mode after a live remaster with persist root enabled?

My answers are: yes, no, no. But I want to know what other people think. The one I am most uncertain about is (2).

BTW: these issues came up because I'm working on fixing the problems with asking the user to change the passwords. This should be fixed in the next iteration.

re #1
By providing a first-run prompt, pre-selecting whichever mode as"default" seems immaterial/non-problematic.

re #2
I believe the status quo first-run end of session prompt (within desktop environment) is ideal.
In case a new user hasn't read the docs (or did read the docs, but hasn't digested all the details/implications) the prompt reinforces
awareness that multiple"modes" are available and user is able to (right then) re-read the docs prior to choosing mode.
If the first-run prompt will now occur during shutdown (past the"point of no return" vs GUI within desktop environment), ouch.
If no first-run prompt, period, is provided... double ouch.

re #3
I can't remember -- if user elects to create a remaster"with persistence", the remaster script asks to choose a mode?
If so, seems the copy should just respect the creator's election. On the other hand, no harm really in asking again during first run.

Thanks!

I also favor the first run dialog, but I think the default should be automatic.

Thanks!

The feedback was unanimous so it will be:

1. Change default to automatic
2. Ask the user to select the mode the first time they have enabled root persistence
3. Don't ask the user to select the mode after a live remaster with persist root enabled

There is another feature we are working on for antiX-14: always do a persist-save without asking right after the user selects new passwords and selects the save mode. The idea is to preserve the password choices so if they forget to do a save, they don't have to re-enter passwords the next time they boot. Since the rootfs will be nearly empty the save should be very fast.

I'm also fixing a bug in persist-config that caused it to get confused when the language was changed.

I plan to use the passwords as an additional condition for running persist-config at boot time.

So if you set the root or demo password back to"root" or"demo" and then do a live-remaster with root persistence, you will be prompted to change the password and you will also be asked to select a persistence mode. Likewise if you enable root persistence some time after you did a live remaster where the root or demo password is"root" or"demo" then you will be asked to change the password and you will be prompted to select a persistence mode.

IOW, putting a"root" or"demo" password in your live remaster acts like a reset.