Question about how the default remastering tool records changes

[eband]

When it's time for me to make a LIveUSB/CD/whatever, when does the tool record changes made regarding the installation and uninstallation of default and all other packages?

For example, I did read that the remaster operation has a recording session, or so I gather, so does it record in one period of time, or does it record changes when I tell it to?

I know, I know, I'm not impressing anyone by forgetting both my manners and the name of the remastering tool (perchance it has something to do with "Persistence?"), so sorry.

[j2mcgreg]

The Snapshot tool will generate a copy of the state your system is in at the time it is run. IE if you then made any changes to your computer, you would have to make another snapshot.

[dolphin_oracle]

there is a lot of question in that question, and I don't think you realize it because of the statement about not using the proper terms.

remaster happens when you run the remaster tool, and it takes all changes on the running live system and compresses them back into a new "default" read-only live system. the home folder is often excluded but doesn't have to be. this is typically done for live-usb setups and frugal installs. it has no meaning on an regular installed system.

as @j2mcgreg says, snapshot works on the running system, whether live or installed, to create a new custom installable iso image, similar to one of our official release isos.

persistence has many forms but mostly its a layered file system that allows changes to the usually read-only live sessions to be stored. it has many forms. here's a quick list

Code: Select all

persist_all - use separate persistence files for root and home. root is loaded into ram, and typically changes written back to the live-usb at shutdown.  home persistence files are always read from disk, changes are written as you go.

persist_root - use persistence file for root (home folder included). loaded into ram

persist_static - like persist_all, but not loaded into ram, accessed from live-usb if its writeable.  changes are written as you go.

p_static_root - like persist_root, but not loaded into ram, accessed from live-usb if its writeable. changes are written as you go.

persist_home - no root persistence file, only home. home is never loaded into ram.  changes are written as you go.

frugal_persist - like persist_all, but performs a "frugal" install onto a folder on an internal hard drive. subsequent boots with this option will try to find the existing frugal install and boot it.

frugal_root - like persist_root, but for frugal installs

frugal_static - like persist_static, but for frugal installs

f_static_root - like p_static_root, but for frugal installs

frugal_home - like persist_home, but for a frugal install

frugal_only - do a frugal install, but no persistence used (read only system).

technically remaster and snapshot do not require persistence files at all, as long as all changes to the file system fit into ram.

[eband]

All right. Thanks!

I have to admit, it's like a new language to learn, I've been using Cubic for Ubuntu all my life, and in my previous one, Remastersys.

All were Ubuntu-based, so sorry if I do seem a little behind.

Any good FAQs I should read up on before I proceed?

[artytux]

Before and after installing MXLinux 21 then MXL23 the MX tour Kde that gives a bunch of small easy to read/understand topics that differed from what I had been using (Linuxes),
also visiting this forum *Active Topics* helps too.
The Manual is only 197 pages,

And Welcome eband.