Where Does Slax Store Persistent Changes and Modules?
Slax keeps persistent changes in /slax/changes on the boot device (or a save.dat container), with extra modules as .sb files in /slax/modules.
Last updated
Slax runs live with an overlay for changes. Persistent mode writes those changes into /slax/changes on the boot device, so the next boot resumes where you left off. Without persistence configured, every boot starts clean by design.
Software comes as modules rather than packages. Drop .sb files into /slax/modules and they activate at boot. The save.dat alternative packs persistence into a single container file, handy on filesystems where a plain folder will not do. Check which mode a given stick uses before assuming files survive.
Where Slax stores this, by platform
/slax/changes
Persistent overlay contents on the boot device. Present only when persistence is configured. Back this folder up to preserve the customized system.
/slax/modules
Software bundles activated at boot, one .sb per application. Add or remove files here with the system offline. Core modules ship beside custom ones.
Frequently asked questions
How do I add software to Slax permanently?
Copy the .sb module file into /slax/modules on the boot device and reboot. Slax activates every module found there automatically. Remove the file to deactivate again. No package manager step exists for this path.
How do I make Slax remember changes?
Boot with the changes= cheatcode pointing at a device folder, or accept the offered save.dat container which stores changes in a file instead. Without either, Slax runs fresh each boot and forgets everything. Check free space since the container is fixed size.
Notice an outdated path? Let us know.