The primary purpose of live remastering is to make it as safe, easy, and
convenient as possible for users to make their own customized version of
MX-14. The idea is that you use a LiveUSB or a LiveHD (a
frugal install to a
hard drive partition) as the development and testing environment. Add or
subtract packages and then when you are ready to remaster, use use a simple
remaster script or GUI to do the remaster and then reboot. If something goes
horribly wrong, simply reboot again with the rollback option and you
will boot into the previous environment.
If you are using a LiveUSB then the LiveUSB is your target system. You can use it to install your customized version of MX-14 on other systems. If you are using a LiveHD then you will need to create a LiveUSB or a LiveCD from the LiveHD in order to install elsewhere.
There are three simple and straightforward system requirements that are needed to perform live remastering:
The boot device must be writable
The boot device must have enough free space to create a new linuxfs file
The development system must have been created using a "frugal install", not a fromiso install
In other words, the development system must be booted using a linuxfs file that is on a writable device that has enough free space to create a new linuxfs file.
Remastering plus Persistence
A persistent home or a persistent root can be useful if you are doing remastering. A persistent home is a handy place to hold your development environment if you don’t want that environment to end up in your remaster. A persistent root is a handy way to save changes between reboots without having to go to the bother of doing a full remaster. Details, see Persistence.
Step by step
You typically will be in a Live session when you remaster. After you have made all the changes you want, click Start menu > System > RemasterCC and enter the root password. A dialog box opens with 4 buttons,
- Set up live persistence. If you made your bootable usb with unetbootin or similar tool, you can use this option to create a new persistence file which will let the user save changes made to the file system for future boots. This option isn't strictly needed if you just want to make a remaster, but its nice for saving changes between remasters.
- Configure live persistence. This will set how the liveUSB will save the persistence file. Although there is an automatic option, is does not currently work. The semi-automatic option is the default, whereby changes will be saved at logout. There is also a manual save option. Again, this is not strictly speaking required for the remaster to work.
- Save root persistence. This is how you save your filesystem changes to the persistence file in the event you elected a manual save option. This will also work if you just want to save changes immediately rather than waiting for logout in semi-automatic mode.
- Remaster. The remaster system will walk you through rolling up your filesystem changes, either made during the session or from your persistence files if available, into a new linuxfs file on the liveUSB. Your changes will now be part of the default linuxfs filesytem and will appear even if you do not choose the persistence options at boot.
Work your way carefully through the list, from top to bottom, following the directions that lead you through the process.
Live Remaster Boot Options
There are only two live remaster boot option because live remastering is almost entirely handled by a script or GUI. The only two options are to prevent live remastering and to rollback live remastering in case something goes horribly wrong.
|noremaster||don’t remaster even when a linuxfs.new file is found|
|rollback||return to previous version after a failed remaster|
For details, see Advanced: Remaster