We are experimenting with saving some state information on the LiveUSB even if no persistence is enabled. Currently we save the desktop setting (window manager and icon manager), the alsa volume settings, and wireless networks and passwords. The alsa settings are saved on a machine by machine basis. Otherwise there will be conflicts and error messages because the alsa settings contain machine dependent information.
This should be transparent to you. What you may notice is that your choice of desktop, your wireless passwords, and your volume settings survive across reboots even if persistence is not enabled. There will also be messages about "saving state file ..." and "restoring state file ..." at startup and shutdown.
The files are stored under subdirectories in /antiX/state/ on the LiveUSB. The LiveUSB is normally mounted at /live/boot-dev when you are running Live. This directory should be created automatically the first time you boot the LiveUSB. You can control which files get saved by editing the files:
These will be also be automatically created on the first LiveUSB boot. The defaults are:
You can turn this off temporarily with the "nousbstate" cheat. You can turn it off permanently by touching the file /antiX/state/no-state. In the next release, the cheat code will change to "nosavestate" and "savestate". These will also touch and remove the no-state file so any change you make to enable or disable this feature with boot codes will survive reboots.
General state files are saved across all machines. This is being used to remember wireless networks and passwords. Machine state files are saved and restored on a machine by machine basis. If you only use the LiveUSB on one machine then they act like general state files but if you move the LiveUSB between machines then machine state files will only be restored to the machine they were stored on.
The reason for this is a conflict between making the LiveUSB work on different machines and saving the alsa volume. The file that stores the alsa volume also contains hardware specific information and will cause errors if it is used on a machine that has different hardware. To make a LiveUSB that has persistence general purpose (so it works on more than one machine) then we need to delete the volume information. Machine dependent state files keep a separate copy of the asound.state file for each machine the LiveUSB is run on. Machine are identified by a machine-id which is a hash of the files /sys/class/dmi/id/board_*.
The restoration of general state files and of the desktop session file is disabled if persistence is enabled. But the files are stilled stored at shutdown and will be available on the next non-persistent boot. The machine state files aways get used unless saving state is disabled. This should prevent alsa error when you move the LiveUSB between machines.