Where Does Porteus Store Modules and Changes?
Porteus loads software from .xzm modules in /porteus/modules and persists changes in /porteus/changes or a save.dat container file on the boot device.
Last updated
Porteus is modular down to the concept level. The base system plus each .xzm module in /porteus/modules layer together at boot. Adding software means adding a file, not running an installer, and removal is deletion.
Persistence is the changes layer: either a plain folder at /porteus/changes or a save.dat container holding the same content in one file. Containers suit Windows formatted sticks where folders cannot preserve Linux permissions. Either way, the boot device root next to the portEFI or boot folders is where to look.
Where Porteus stores this, by platform
/porteus/modules
Software layers loaded at boot, one .xzm per package set. The optional subfolder holds on demand modules. Add here offline, then reboot.
save.dat
Single file container for the changes layer on filesystems needing it. Created at first boot prompt with your chosen size. Copy it off for backups.
Frequently asked questions
How do I install software permanently on Porteus?
Place the .xzm file in /porteus/modules (or the optional subfolder for on demand use) and reboot, or activate live with the activate command. Modules stack as layers over the base system. Deactivate by removing the file.
What is the save.dat container?
Create one at boot when Porteus offers, sized to your needs on the boot device. It holds the changes layer as a single file, useful on FAT partitions. Back it up like any precious file since it contains your whole delta.
Notice an outdated path? Let us know.