This way one is not tied down to a desktop, or version or architecture or even a distro. Space that would have been taken up by an installed system is now freed for Data Storage. Could regard the distro on ISO as stored program which now runs on the computer..Browser profiles can be switched to directories on real filesystems by invoking mozilla browsers with command line argument. This way each distro is kept encapsulated within the ISO live file. The ISO files (write once,read many) and Video files (write once, read once)) can all reside on a partition where journalling not used like ext2 filesystem
One-off Changes Folder/File
Boot Parameter (cheatcode) changeschanges-ro
... Keep saved changes in a read-only state. This is useful when
you have your system set up exactly how you like it and do not
want to save any other changes you might make during a live
session. This cheatcode should be used in conjunction with the
'changes=' or 'changes=EXIT:' cheatcodes.
Example: 'changes=/path/file.dat changes-ro'
- changes=EXIT:[/dev/sdXy]/Path/to/<Directory to hold Changes Folder>
When required setup reached, restart system without changes parameter
- changes-ro changes=[/dev/sdXy]/Path/to/<Directory to hold Changes Folder>
Starts up system with saved setup.
igreka wrote:Also, I know changes are supposed to be in rootcopy but in my case, Porteus has a changes folder populated instead.
This last method of creating module presumably that used by brokenman to set up his system.alienbob wrote:rootcopy/ - this directory is empty by default. Anything you (the user of the ISO) add to this directory will be copied verbatim into the filesystem by the init script when the Live OS boots. You can use this feature for instance if you do not want to create a separate squashfs module file for your application configuration files.