SliTaz GNU/Linux official and community documentation wiki.
.png

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:guides:manyinone [2010/11/01 22:29]
bellard
en:guides:manyinone [2020/06/16 15:16] (current)
bellard s/pizza.slitaz.me/mypizza.slitaz.org/
Line 1: Line 1:
 ======= Create many-in-1 flavors ======= ======= Create many-in-1 flavors =======
  
-Slitaz ​live CD are fully running ​in RAM. The feature set depends on the available RAM size. You can build an auto adaptative live CD to ensure that the right feature set is launched according to the detected RAM size. You need to :+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:
  
-    * define a flavor list (or an ISO list) where each flavor is nested in the next 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 ​an error message with less than 32MB...+    * and displays ​an error message with less than 32MB..
 + 
 +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 ​informations ​to build a live CD+A flavor holds all the necessary ​information ​to build a LiveCD
-The [[http://​bb.slitaz.org/​|build bot]] will keep automagically the flavor file (.flavor) up to date and this tiny file will be used by tazlito to (re)generate the ISO image.+The [[http://​bb.slitaz.org/​|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.
  
-[[http://​hg.slitaz.org/​flavors|flavors]] are like software sources for the flavor file and the [[http://​bb.slitaz.org/​|build bot]] is a make tool. Providing flavors is like providing source files and providing ​ISO is like providing executables only.+[[http://​hg.slitaz.org/​flavors|flavors]] are like software sources for the flavor filethe [[http://​bb.slitaz.org/​|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. 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 ​and +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.
-the according ram sizes from the largest to the smallest.+
  
 <​code>​ <​code>​
Line 32: Line 36:
 ===== The easy way: using tazlitobox ===== ===== The easy way: using tazlitobox =====
  
-Launch **tazlitobox**,​ select tab **meta**. Enter the ISO file in **ISO input** and the according ​necessary ​RAM size in **RAM needed** for each flavor with the **+** button. +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**. 
-Fill **ISO output** name en klick **Build ISO**.+ 
 +<​note>​In recent SliTaz versions **tazlitobox** has moved into **tazpanel** in the menu **boot** -> **live** -> ** Build a meta ISO ** 
 +</​note>​
  
 ===== The cmdline way: using tazlito ===== ===== The cmdline way: using tazlito =====
Line 39: Line 45:
 Usage: tazlito merge size1 iso size2 rootfs2 [sizeN rootfsN]... Usage: tazlito merge size1 iso size2 rootfs2 [sizeN rootfsN]...
  
-The largest flavor is given as an ISO file to get the additional rootcd files.+The largest flavor is given as an ISO file to get the additional rootcd files and will get the resulting ISO.
  
 <​code>​ <​code>​
 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
 </​code>​ </​code>​
 +
 +===== 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**
 +<​note>​You can do something similar online with <​del>​[[http://​pizza.slitaz.me/​]]</​del>​[[http://​mypizza.slitaz.org]].</​note>​
 
en/guides/manyinone.1288646984.txt.gz · Last modified: 2010/11/01 22:29 by bellard