There are two different places we can run persist-config (to select persist-save mode) on the first persistent boot:

1. Right after we force the user to change passwords
2. Inside of X-windows

We have been doing it inside of X-windows but if people don't mind the CLI interface (it is just one choice) then I would prefer to move it to (1). Here's why. On the first persistence boot I want to:

• Force new passwords
• Have user select persist-save mode
• Do an immediate persist-save to save the selections just made

This has a couple of benefits. It works on core systems and when people boot into run level 3 on base and full. In addition, it works without any alteration if people use a completely different window manager. Running inside of X-windows requires that we add an entry to the window manager startup file. IMO changing the passwords is a big pain. Having to answer one simple multiple choice question after that is no big deal.

This is part of my effort to move live-system functionality out of /etc/init.d/ and out of WM startup files and into the initrd. This will help keep things consistent between systems that use sysVinit and that use systemd. In addition, it moves toward getting our Live system to work by simply using our live initrd and no changes to the file system. Such a system would, of course, be missing functionality such as remaster-live and persist-save but the idea is that it should boot into a functioning system. It might even"just work" even on non-Debian based systems.

i would actually PREFER it to be right after the password change before X starts.

CLI OK by me.