Slitaz LiveCDs run fully in RAM. The feature set depends on the available RAM size. You can build an auto adaptive LiveCD to ensure that the right feature set is launched according to the detected RAM size. You need to:
The many-in-1 ISO may be a little bit larger than the largest flavor. Sometimes the sizes are identical.
We will build the official slitaz-3in1 flavor which boots:
The ISO images slitaz-3.0-3in1.iso and the largest flavor slitaz-3.0.iso share the same size : 31457280 bytes. (caused by the 1MB padding: it would be 123351 bytes larger otherwise).
A flavor holds all the necessary information to build a LiveCD. The build bot will automagically keep the flavor file (.flavor) up to date and this tiny file will also be used by tazlito to (re)generate the ISO image.
flavors are like software sources for the flavor file: the build bot is a make tool and tazlito pack-flavor the compiler. Providing flavors is like providing source files and providing ISOs is like providing executables only.
A meta flavor has no rootfs, rootcd or packages.list. The ROOTFS_SELECTION in the receipt (see http://hg.slitaz.org/flavors/file/324757d594ef/core-3in1) gives the nested flavors according to the ram sizes from the largest to the smallest.
ROOTFS_SELECTION="160M core 96M justx 32M base"
The rootfs and the rootcd are taken from the largest flavor.
Launch tazlitobox, select tab meta. Enter the ISO file in ISO input and add the according RAM size in RAM needed for each flavor with the + button. Fill the ISO output name and then click Build ISO.
Usage: tazlito merge size1 iso size2 rootfs2 [sizeN rootfsN]…
The largest flavor is given as an ISO file to get the additional rootcd files and will get the resulting ISO.
tazlito merge 160M slitaz-core.iso 96M rootfs-justx.gz 32M rootfs-base.gz
Ok we can boot the live CD with less RAM but nowadays the computers have a lot of RAM. And booting in text mode is not so sexy…