Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:guides:manyinone [2010/11/01 21:35] – bellard | en:guides:manyinone [2020/06/16 13:16] (current) – s/pizza.slitaz.me/mypizza.slitaz.org/ bellard | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ======= Create many-in-1 flavors ======= | ======= Create many-in-1 flavors ======= | ||
| - | Slitaz | + | Slitaz |
| * define a flavor list (or an ISO list) where each flavor is nested in the previous one (like russian dolls), | * define a flavor list (or an ISO list) where each flavor is nested in the previous one (like russian dolls), | ||
| * define the minimum RAM quantity necessary for each flavor. | * define the minimum RAM quantity necessary for each flavor. | ||
| + | |||
| + | 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: | We will build the official slitaz-3in1 flavor which boots: | ||
| Line 11: | Line 14: | ||
| * the justx flavor with 96MB to 160MB | * the justx flavor with 96MB to 160MB | ||
| * the base flavor with 32MB to 96MB | * the base flavor with 32MB to 96MB | ||
| - | * and display | + | * and displays |
| + | |||
| + | 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). | ||
| ===== The best way: create a flavor ===== | ===== The best way: create a flavor ===== | ||
| - | A flavor holds all the necessary | + | A flavor holds all the necessary |
| - | The [[http:// | + | The [[http:// |
| - | [[http:// | + | [[http:// |
| A meta flavor has no rootfs, rootcd or packages.list. | A meta flavor has no rootfs, rootcd or packages.list. | ||
| - | The **ROOTFS_SELECTION** in the receipt (see http:// | + | The **ROOTFS_SELECTION** in the receipt (see http:// |
| - | the according ram sizes from the largest to the smallest. | + | |
| < | < | ||
| Line 32: | Line 36: | ||
| ===== The easy way: using tazlitobox ===== | ===== The easy way: using tazlitobox ===== | ||
| - | Launch **tazlitobox**, | + | Launch **tazlitobox**, |
| - | Fill **ISO output** name en klick **Build ISO**. | + | |
| + | < | ||
| + | </ | ||
| ===== The cmdline way: using tazlito ===== | ===== The cmdline way: using tazlito ===== | ||
| Line 44: | Line 50: | ||
| tazlito merge 160M slitaz-core.iso 96M rootfs-justx.gz 32M rootfs-base.gz | tazlito merge 160M slitaz-core.iso 96M rootfs-justx.gz 32M rootfs-base.gz | ||
| </ | </ | ||
| + | |||
| + | ===== Is it so useful ? ===== | ||
| + | |||
| + | 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... | ||
| + | |||
| + | * booting **live** a (very) old machine with less RAM may be in text mode. But the same PC can have a graphic desktop if SliTaz is installed on hard disk. The SliTaz base flavor can install the distribution. Without the russian dolls trick there is no way to use these machines with the default SliTaz cdrom. | ||
| + | |||
| + | * some people maybe don't like the default application set. They can boot a simpler flavor live (say justx), add their preferred packages, edit the config files and save the result with **tazlito writeiso** | ||
| + | < | ||