tazlito view doc/tazlito.en.html @ rev 206

tazlito/loram-cdrom: fix unpacked fs path
author Pascal Bellard <pascal.bellard@slitaz.org>
date Sat Dec 25 22:52:13 2010 +0100 (2010-12-25)
parents a47ff98afc58
children deb4940afbdd
line source
1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
4 <head>
5 <title>Tazlito Manual - SliTaz Live Tool</title>
6 <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" />
7 <meta name="description" content="" />
8 <meta name="expires" content="never" />
9 <meta name="modified" content="2008-07-18 14:00:00" />
10 <style type="text/css"><!--
11 body { font: 90% sans-serif, vernada, arial; margin: 0; }
12 #header { background: #f0ba08; color: black; height: 50px;
13 border-top: 1px solid black; border-bottom: 1px solid black; }
14 #content { margin: 0px 50px 26px 50px; }
15 h1 { margin: 14px 0px 0px 16px; }
16 li { line-height: 1.4em; }
17 pre { padding: 5px; color: black; background: #e1e0b0; }
18 pre.script { padding: 10px; color: black; background: #e8e8e8;
19 border: 1px inset #333333; }
20 code { font-size: 100%; color: #669900; background: transparent; }
21 hr { color: white; background: white; height: 1px; border: 0; }
22 --></style>
23 </head>
24 <body bgcolor="#ffffff">
25 <div id="header">
26 <h1><font color="#3e1220">Tazlito Manual</font></h1>
27 </div>
28 <hr />
29 <!-- Start content -->
30 <div id="content">
32 <h2>NAME</h2>
33 <p>
34 Tazlito - SliTaz Live Tool.
35 </p>
37 <h2>SYNTAX</h2>
38 <pre>
39 tazlito [command] [list|iso|flavor] [dir]
40 </pre>
42 <h2>DESCRIPTION</h2>
43 <p>
44 Tazlito is a small utility to extract a LiveCD, rebuild the
45 ISO image and regenerate the root filesystem of the LiveCD.
46 Tazlito can also generate a distribution from a list of packages
47 previously downloaded. To run, Tazlito uses the configuration file
48 /etc/tazlito/tazlito.conf or an easily generated tazlito.conf
49 found in the current directory.
50 It specifies the name of the ISO, volume, maintainer and
51 the paths of the packages to distribute and the generated ISO.
52 Tazlito can also set up a directory containing additional files
53 which will be copied to the LiveCD when generating the distribution.
54 </p>
55 <p>
56 Tazlito is distributed under the free GNU licence GPL V3,
57 installed by default on SliTaz and installed/sucessfully tested
58 on Debian GNU/Linux. You will find additional information
59 about creating a LiveCD in the Handbook.
60 </p>
62 <h2>COMMANDS</h2>
64 <a name="usage"></a>
65 <h3><font color="#6c0023">usage</font></h3>
66 <p>
67 The 'usage' command displays a summary of available commands
68 with a short description:
69 </p>
70 <pre>
71 # tazlito usage
72 </pre>
74 <a name="stats"></a>
75 <h3><font color="#6c0023">stats</font></h3>
76 <p>
77 Stats displays the configuration variables, the paths to the
78 various files and directories, and information on the ISO image:
79 </p>
80 <pre>
81 # tazlito stats
82 </pre>
84 <a name="gen-config"></a>
85 <h3><font color="#6c0023">gen-config</font></h3>
86 <p>
87 The 'gen-config' command allows you to generate a configuration
88 file ready to be edited. By default the file is created in
89 the current directory, but can be in another directory
90 if specified via the command line:
91 </p>
92 <pre>
93 # tazlito gen-config
94 # tazlito gen-config /path/to/distro
95 </pre>
97 <a name="configure"></a>
98 <h3><font color="#6c0023">configure</font></h3>
99 <p>
100 This command configures the system configuration
101 file or one found in the current directory:
102 </p>
103 <pre>
104 # tazlito configure
105 </pre>
107 <a name="gen-iso"></a>
108 <h3><font color="#6c0023">gen-iso</font></h3>
109 <p>
110 The 'gen-iso' command can generate a
111 new LiveCD image following modifications and additions to the
112 root filesystem of the cdrom. To function, this command needs
113 a directory containing the distro-tree of the Live system.
114 This tree can easily be built with the 'extract-distro' command,
115 modified and rebuilt via:
116 </p>
117 <pre>
118 # tazlito gen-iso
119 </pre>
121 <a name="gen-initiso"></a>
122 <h3><font color="#6c0023">gen-initiso</font></h3>
123 <p>
124 The 'gen'initso' command will do the same work as 'gen-iso',
125 but it rebuilds the initramfs compressed system prior.
126 The initramfs contains the root filesystem and
127 must be rebuilt if modified:
128 </p>
129 <pre>
130 # tazlito gen-initiso
131 </pre>
133 <a name="list-flavors"></a>
134 <h3><font color="#6c0023">list-flavors</font></h3>
135 <p>
136 The 'list-flavors' command downloads (if necessary) and displays
137 a list of the different flavors available. You can force the
138 download with the --recharge option:
139 </p>
140 <pre>
141 # tazlito list-flavors
142 # tazlito list-flavors --recharge
143 </pre>
145 <a name="get-flavors"></a>
146 <h3><font color="#6c0023">get-flavor</font></h3>
147 <p>
148 The 'get-flavor' command downloads (if necessary) and prepares the
149 files for 'gen-distro' to generate a flavor:
150 </p>
151 <pre>
152 # tazlito get-flavor particular-flavor
153 </pre>
155 <a name="show-flavors"></a>
156 <h3><font color="#6c0023">show-flavor</font></h3>
157 <p>
158 The 'show-flavor' command displays the description of the
159 flavor and its size after regeneration. The options
160 --brief and --noheader reduce the output displayed:
161 </p>
162 <pre>
163 # tazlito show-flavor particular-flavor
164 # tazlito show-flavor particular-flavor --brief
165 # tazlito show-flavor particular-flavor --brief --noheader
166 </pre>
168 <a name="gen-flavor"></a>
169 <h3><font color="#6c0023">gen-flavor</font></h3>
170 <p>
171 The 'gen-flavor' command creates a description file of a new
172 flavor from the results of generating a distro (gen-distro).
173 The .flavor file can then be sent to slitaz.org:
174 </p>
175 <pre>
176 # tazlito gen-flavor new-flavor
177 </pre>
179 <a name="gen-liveflavor"></a>
180 <h3><font color="#6c0023">gen-liveflavor</font></h3>
181 <p>
182 The 'gen-liveflavor' command creates a description file of a new
183 flavor from the results of generating a distro based on the
184 current system. The --help option provides more information:
185 </p>
186 <pre> # tazlito gen-liveflavor
187 # tazlito gen-liveflavor --help
188 </pre>
190 <a name="upgrade-flavor"></a>
191 <h3><font color="#6c0023">upgrade-flavor</font></h3>
192 <p>
193 The `upgrade-flavor' command refreshes a flavor file by updating the
194 list of packages with the latest versions available:
195 </p>
196 <pre>
197 # tazlito upgrade-flavor this-flavor
198 </pre>
200 <a name="extract-flavor"></a>
201 <h3><font color="#6c0023">extract-flavor</font></h3>
202 <p>
203 The 'extract-flavor' command converts a flavor into an easily modifiable
204 tree structure in /home/slitaz/flavors which can be managed with
205 mercurial:
206 <a href="http://hg.slitaz.org/flavors">http://hg.slitaz.org/flavors</a>.
207 </p>
208 <pre>
209 # tazlito extract-flavor this-flavor
210 </pre>
212 <a name="pack-flavor"></a>
213 <h3><font color="#6c0023">pack-flavor</font></h3>
214 <p>
215 The 'pack-flavor' command converts a tree structure in /home/slitaz/flavors
216 into a flavor file (.flavor). It is inverse of 'tazlito extract-flavor':
217 </p>
218 <pre>
219 # tazlito pack-flavor this-flavor
220 </pre>
222 <a name="extract-distro"></a>
223 <h3><font color="#6c0023">extract-distro</font></h3>
224 <p>
225 The 'extract-distro' command is used to extract an ISO image
226 from the LiveCD to rebuild the structure of the root cdrom
227 and system. It is then possible to make the desired changes
228 or additions and rebuild the ISO image via 'gen-iso' or
229 'gen-initiso'. Example of use:
230 </p>
231 <pre>
232 # tazlito extract-distro slitaz-cooking.iso
233 </pre>
235 <a name="gen-distro"></a>
236 <h3><font color="#6c0023">gen-distro</font></h3>
237 <p>
238 The <em>Generate Distribution</em> command can generate the
239 distro-tree and an ISO image via a list of packages. To function,
240 this command needs a list of packages, a directory containing
241 all the (.tazpkg) packages on the list, and a directory to
242 generate the distribution. The list of packages can be extracted
243 from a flavor with the 'get-flavor' command. If one uses the
244 LiveCD, the options --cdrom and --iso= permit the regeneration
245 of packages that place files in /boot without being obliged
246 to download them and recovers the additional files of the
247 LiveCD. The path to the various directories are configured
248 in the configuration file and packages can be downloaded
249 from the SliTaz mirrors or generated by Tazwok. To generate
250 a distribution:
251 </p>
252 <pre>
253 # tazlito gen-distro
254 # tazlito gen-distro --cdrom
255 # tazlito gen-distro --iso=slitaz.iso
256 # tazlito gen-distro package-list
257 </pre>
259 <a name="clean-distro"></a>
260 <h3><font color="#6c0023">clean-distro</font></h3>
261 <p>
262 Removes all files generated or extracts of the structure
263 of the LiveCD:
264 </p>
265 <pre>
266 # tazlito clean-distro
267 </pre>
269 <a name="check-distro"></a>
270 <h3><font color="#6c0023">check-distro</font></h3>
271 <p>
272 This command simply verifies if files installed
273 by the packages are present on the system:
274 </p>
275 <pre>
276 # tazlito check-distro
277 </pre>
279 <a name="writeiso"></a>
280 <h3><font color="#6c0023">writeiso</font></h3>
281 <p>
282 This command will write the current filesystem to a cpio archive
283 (rootfs.gz) and then generate a bootable ISO image. Writeiso can
284 be used in a HD install or in live mode and will also archive your
285 current /home directory. This command lets you easily remaster and
286 build your own LiveCD image, just boot, modify any files, and then:
288 </p>
289 <pre>
290 # tazlito writeiso [gzip|lzma|none]
291 # tazlito writeiso gzip
292 # tazlito writeiso gzip image-name
293 </pre>
295 <a name="frugal-install"></a>
296 <h3><font color="#6c0023">frugal-install</font></h3>
297 <p>
298 Perfom a frugal installation into /boot/frugal and add a GRUB entry
299 if needed. Frugal mode will make SliTaz work completely in memory
300 (RAM) - useful to test a distro without burning an ISO or to have a
301 rescue system ready to use when the computer powers on. To install
302 all needed files from a distro tree or an ISO image:
303 </p>
304 <pre>
305 # tazlito frugal-install
306 # tazlito -fi slitaz.iso
307 </pre>
309 <a name="check-list"></a>
310 <h3><font color="#6c0023">check-list</font></h3>
311 <p>
312 Checks if the distro-packages.list is updated with the latest package
313 versions:
314 </p>
315 <pre>
316 # tazlito check-list
317 </pre>
319 <a name="repack"></a>
320 <h3><font color="#6c0023">repack</font></h3>
321 <p>
322 Recompresses the rootfs with the best possible compression:
323 </p>
324 <pre>
325 # tazlito repack slitaz.iso
326 </pre>
328 <a name="merge"></a>
329 <h3><font color="#6c0023">merge</font></h3>
330 <p>
331 Combines several flavors like nested Russian dolls. Each rootfs is a
332 subset of the previous. The first rootfs is extracted from the ISO image
333 used in the third argument. The flavor will then be chosen to launch at
334 startup according to the amount of RAM available:
335 </p>
336 <pre>
337 # tazlito merge 160M slitaz-core.iso 96M rootfs-justx.gz 32M rootfs-base.gz
338 </pre>
340 <a name="build-loram"></a>
341 <h3><font color="#6c0023">build-loram</font></h3>
342 <p>
343 Creates an ISO image flavor for low ram systems from a SliTaz ISO image.
344 You can build a flavor with / always in ram or where / resides on the cdrom:
345 </p>
346 <pre>
347 # tazlito build-loram slitaz.iso loram.iso
348 # tazlito build-loram slitaz.iso loram-cdrom.iso cdrom
349 </pre>
351 <a name="emu-iso"></a>
352 <h3><font color="#6c0023">emu-iso</font></h3>
353 <p>
354 The emu-iso command uses the Qemu emulator to start and run SliTaz.
355 Qemu is used to test the newly built ISO image without burning to a
356 cdrom or booting into frugal mode:
357 </p>
358 <pre>
359 # tazlito emu-iso
360 # tazlito emu-iso path/to/image.iso
361 </pre>
363 <a name="burn-iso"></a>
364 <h3><font color="#6c0023">burn-iso</font></h3>
365 <p>
366 Burn-iso will guess the cdrom device and its speed, and wodim
367 (part of cdrkit) will begin to burn an ISO image. The default
368 ISO image is the one located in the current configuration file,
369 but it's possible to specify a different image via the
370 command line:
371 </p>
372 <pre>
373 # tazlito burn-iso
374 # tazlito burn-iso slitaz-hacked.iso
375 </pre>
377 <h2>FLAVORS</h2>
378 <p>
379 A <i>.flavor</i> file contains just a few KB of information needed to
380 (re)manufacture a custom LiveCD of SliTaz.
381 </p>
383 <a name="rebuild-flavor"></a>
384 <h3><font color="#6c0023">Manufacture a flavor</font></h3>
385 <p>
386 You can choose the flavor to (re)manufacture from among those available:
387 </p>
388 <pre>
389 # tazlito list-flavors
391 List of flavors
392 ================================================================================
393 Name ISO Rootfs Description
394 ================================================================================
395 base 6.9M 13.1M Minimal set of packages to boot
396 core-3in1 31.5M 105.6M SliTaz core system with justX and base alternatives
397 core 31.5M 104.6M SliTaz core system
398 eeepc 31.2M 105.4M SliTaz eeepc system
399 justX 16.1M 51.2M SliTaz with a minimal X environment
400 </pre>
401 <p>
402 We will start by remanufacturing the <i>eeepc</i> flavor which uses 105.4M of RAM
403 and has a CD-ROM size of 31.2M:
404 </p>
405 <pre>
406 # tazlito clean-distro
407 # tazlito get-flavor eeepc
408 # tazlito gen-distro
409 </pre>
411 <a name="create-flavor"></a>
412 <h3><font color="#6c0023">Create a flavor</font></h3>
413 <p>
414 To create a flavor, you must:
415 </p>
416 <ul>
417 <li>Either create an ISO image with <b>tazlito gen-distro</b> and then create
418 a flavor file with <b>tazlito gen-flavor</b></li>
419 <li>Either directly create the tree structure that defines the flavor
420 (see <b>tazlito extract-flavor</b>) and then create the flavor with
421 <b>tazlito pack-flavor</b></li>
422 <li>Either use the
423 <a href="http://mirror.slitaz.org/pizza/">online builder</a></li>
424 </ul>
426 <a name="publish-flavor"></a>
427 <h3><font color="#6c0023">Post a flavor</font></h3>
428 <p>
429 Because a .flavor file contains just a few KB; it can be easily sent via the
430 mailing list.
431 </p>
432 <p>
433 The results of <b>tazlito extract flavor</b> can also be put in mercurial
434 (http://repos.slitaz.org/flavors). This method is preferred because the
435 tree will be directly visible with the
436 <a href="http://hg.slitaz.org/flavors/file/tip">mercurial web interface</a>.
437 </p>
438 <p>
439 This tree includes:
440 </p>
441 <ul>
442 <li>
443 A <b>receipt</b> file describing the flavor thanks to the variables:
444 <ul>
445 <li>
446 FLAVOR: The flavor name.
447 </li>
448 <li>
449 SHORT_DESC: Short description.
450 </li>
451 <li>
452 VERSION: Free format.
453 </li>
454 <li>
455 MAINTAINER: Email address of maintainer.
456 </li>
457 <li>
458 FRUGAL_RAM: Minimum RAM required (optional).
459 </li>
460 <li>
461 ROOTFS_SIZE: Size of rootfs.gz decompressed into RAM (optional).
462 </li>
463 <li>
464 INITRAMFS_SIZE: Size of rootfs.gz on the CD-ROM (optional).
465 </li>
466 <li>
467 ISO_SIZE: Size of CD-ROM (optional).
468 </li>
469 <li>
470 ROOTFS_SELECTION: Optional, see <i>Meta flavor</i> below.
471 </li>
472 </ul>
473 </li>
474 <li>
475 The file <b>packages.list</b> containing the list of packages without
476 specifying the version (tazlito uses the latest available).
477 This file is missing if ROOTFS_SELECTION exists in the receipt.
478 </li>
479 <li>
480 The optional <b>mirrors</b> file containing the list of unofficial mirrors
481 (undigest) to be added to include personal packages.
482 </li>
483 <li>
484 The optional directory <b>rootfs</b> containing the tree to add to the
485 root filesystem rootfs.gz (configuration files usually).
486 </li>
487 <li>
488 The optional directory <b>rootcd</b> containing the tree to add to the
489 root of the CD-ROM.
490 </li>
491 </ul>
493 <a name="tune-flavor"></a>
494 <h3><font color="#6c0023">Adapt a flavor</font></h3>
495 <p>
496 It is often easier to modify an existing flavor than to create one from
497 scratch. To adapt the eeepc flavor for example:
498 </p>
499 <pre>
500 # tazpkg get-install mercurial
501 # cd /home/slitaz
502 # hg clone http://hg.slitaz.org/flavors
503 # cd flavors
504 # cp -a eeepc myslitaz
505 </pre>
506 <p>
507 Files in my-slitaz can then be changed, and:
508 </p>
509 <pre>
510 # tazlito pack-flavor myslitaz
511 </pre>
512 <p>
513 Will simply create the new flavor.
514 </p>
515 <p>
516 Tip: you can skip mercurial installation by extracting a flavor.
517 Using the previous example:
518 </p>
519 <pre>
520 # tazlito get-flavor eeepc
521 # tazlito extract-flavor eeepc.flavor
522 # cd /home/slitaz/flavors
523 # cp -a eeepc myslitaz
524 </pre>
526 <a name="meta-flavor"></a>
527 <h3><font color="#6c0023">Meta flavor</font></h3>
528 <p>
529 A meta flavor contains several flavors like nested Russian dolls. The flavor
530 will be launched at startup according to the amount of RAM available.
531 The ROOTFS_SELECTION variable defines the minimim RAM and corresponding
532 flavor parameters, <a href="http://hg.slitaz.org/flavors/file/tip/core-3in1/receipt">
533 example</a>:
534 </p>
535 <pre>
536 ROOTFS_SELECTION="160M core 96M justX 32M base"
537 </pre>
538 <p>
539 A meta flavor doesn't contain a list of packages (packages.list). SliTaz
540 kernels prior to 2.6.30 do not support meta flavors.
541 </p>
543 <h2>MAINTAINER</h2>
544 <p>
545 Christophe Lincoln &lt;pankso at slitaz.org&gt;
546 </p>
548 <!-- End content -->
549 </div>
550 </body>
551 </html>