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/02 11:18]
bellard size cost
en:guides:manyinone [2020/06/16 15:16]
bellard s/pizza.slitaz.me/mypizza.slitaz.org/
Line 6: Line 6:
     * define the minimum RAM quantity necessary for each flavor.     * define the minimum RAM quantity necessary for each flavor.
  
-The many-in-1 ISO should ​be a little bit larger than the largest+The many-in-1 ISO may be a little bit larger than the largest
 flavor. Sometimes the sizes are identical. flavor. Sometimes the sizes are identical.
  
Line 16: Line 16:
     * and displays 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 ​have the same size : 31457280 bytes. (caused by the 1MB paddingit should ​be 123351 bytes larger otherwise).+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 paddingit would be 123351 bytes larger otherwise).
  
 ===== The best way: create a flavor ===== ===== The best way: create a flavor =====
Line 26: Line 26:
  
 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 ​with the according ram sizes from the largest to the smallest.+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.
  
 <​code>​ <​code>​
Line 36: 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 add the according ​necessary ​RAM size in **RAM needed** for each flavor with the **+** button. Fill the **ISO output** name and click **Build ISO**.+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**. 
 + 
 +<​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 47: 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
 </​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.txt · Last modified: 2020/06/16 15:16 by bellard