- +

About

SliTaz project

- -

+ +

Navigation

+ +

About us

Introduction
Overview
Web site & i18n
Reviews
Association

+ +

Introduction

Introduction to the project

SliTaz GNU/Linux is a free operating system working completely in memory from removeable media such as a cdrom or USB key. It is light, speedy and fully installable @@ -110,7 +100,7 @@

Overview

Root filesystem taking up about 100 MB and ISO image of less than 30 MB.
Ready to use Web server powered by LightTPD with CGI and PHP support.

Web site & i18n

SliTaz's Web site is also available in several languages and is part of the internationalization project. -The web site allows you to download the SliTaz +The web site allows you to download the SliTaz LiveCD and help us to develop the project. You can check the -documentation area to learn how to use the SliTaz +documentation area to learn how to use the SliTaz LiveCD and configure the system.

Reviews

SliTaz GNU/Linux has been reviewed on several web sites. Thanks to everyone for support.

3.0 - March 2010

3.0 - March 2010 & Cooking - Jan 2010

Wordpress - By K.Mandla.
Linux Journal - By Susan Linton.
Distrowatch - By Jesse Smith (Cooking just before 3.0).

2.0 - April 2009

Gdhpress (pt) - By Carlos Morimoto.

1.0 - March 2008

Distrowatch - By Ladislav Bodnar.

Cooking - January 2010

Distrowatch - By Jesse Smith.

- - -

- -

-Last modification : 2010-11-07 16:30:00 - -Top of the page -

- -

- - -

- -

+ + diff -r 111e058c9eff -r 18040398d744 en/asso/index.html --- a/en/asso/index.html Thu Jan 06 18:15:14 2011 +0100 +++ b/en/asso/index.html Thu Jan 06 23:01:09 2011 +0100 @@ -16,85 +16,75 @@ - + + - - -

- -

Navigation

- -

- - -

SliTaz Network

- + +

+ Français | + Português +

+ +

#!/GNU/Linux

- +

Association

Infrastructure and services

+ +

Navigation

+ +

Association

+ The SliTaz GNU/Linux association is a non-profit entity that maintains + and manages the project. Its mission is to ensure the durability of + the project. It provides an infrastruture and delivers professional services + to users, developers and business enterprises using the distribution. The + overall goals and operations of the association are described in the + statutes. +

+ +

-The SliTaz GNU/Linux association is a non-profit entity that maintains -and manages the project. Its mission is to ensure the durability of -the project. It provides an infrastruture and delivers professional services -to users, developers and business enterprises using the distribution. The -overall goals and operations of the association are described in the -statutes. -

Infrastructure and services

@@ -196,58 +186,44 @@

- -

Bank Transfer

-Bank details of the association for all transfers from bank to bank, -such as gifts, services or payment of contributions. Note that all -international cheques incur a fee of ~15 Euros and are best avoided. -

-Banque : Banque Cantonal Vaudoise
-Titulaire : Association SliTaz
-Compte : E 5212.94.24
-IBAN : IBAN CH25 0076 7000 E521 2942 4
-BIC/Swift : BCVLCH2LXXX -

Postal Address

Association SliTaz GNU/Linux
Rue du Village 40
1081 Montpreveyres
Switzerland

- -

-Last modification : 2008-07-16 21:30:00 - -Top of the page -

- -

- - -

- -

+ + diff -r 111e058c9eff -r 18040398d744 en/asso/statutes.html --- a/en/asso/statutes.html Thu Jan 06 18:15:14 2011 +0100 +++ b/en/asso/statutes.html Thu Jan 06 23:01:09 2011 +0100 @@ -16,66 +16,66 @@ - + + - - -

- -

Navigation

- -

- - -

SliTaz Network

- + +

+ Português +

+ +

#!/GNU/Linux

- +

Articles of the Association

Statutes

+ +

Navigation

+ +

Articles of the Association

+ +

Statutes

General

Article 1: Name, location and duration

@@ -266,34 +266,35 @@ Christophe Lincoln Pascal Bellard Eric Joseph-Alexandre

- -

-Last modification : 2008-07-16 21:30:00 - -Top of the page -

- -

- - -

- -

+ + diff -r 111e058c9eff -r 18040398d744 en/devel/index.html --- a/en/devel/index.html Thu Jan 06 18:15:14 2011 +0100 +++ b/en/devel/index.html Thu Jan 06 23:01:09 2011 +0100 @@ -16,85 +16,68 @@ - + + - - -

- -

Navigation

- -

- - -

SliTaz Network

- + +

+ Deutsch | + Français | + Português +

+ +

#!/GNU/Linux

- +

Development

SliTaz Developers corner

+ +

Navigation

+ +

Development

KISS and comply to standards.
Build host & home.
Mercurial repositories.
Implementation of iconv().
Tazpkg packages.
Website Management.

+ +

- +

SliTaz Developers corner

SliTaz is an open source and community driven distribution. Everyone is welcome to join and contribute, from users, to hackers and developers, there is always @@ -118,7 +101,7 @@

KISS and comply to standards

Keep it simple: follow the best standards, carefully draft and write high quality documentation, provide a stable and robust system and keep @@ -129,7 +112,7 @@

Tank - Build host & home

Each contributor may have an account on the project server with secure access, disk space, a public directory and all development tools. @@ -143,7 +126,7 @@

Mercurial repositories

SliTaz Mercurial or Hg repos can be browsed or cloned by anyone using the URL: http://hg.slitaz.org/. People with write @@ -151,7 +134,7 @@ Mercurial uses Python and is installable with: tazpkg get-install mercurial

~/.hgrc

Before you push your first commit onto the server, be sure that you have a correct Hg configuration file with your name and email address, and remember to check @@ -217,7 +200,7 @@ -

Implementation of iconv()

SliTaz uses iconv() provided by GNU glibc - any packages that offer libiconv must use the library contained in glibc-locale. @@ -225,7 +208,7 @@

Tazpkg Packages

The tazpkg packages in SliTaz are automatically created via Tazwok and a receipt in the wok. The Cookbook describes the @@ -263,10 +246,9 @@

Website Management and Books

Website Management

-The website and books (Handbook and Cookbook) are managed via -a mercurial repository, they can be cloned by: + The website is managed via a mercurial repository, they can be cloned by:

  $ hg clone http://hg.slitaz.org/website
@@ -274,14 +256,11 @@
  $ hg clone http://repos.slitaz.org/website

xHTML coding style

The pages and different books are coded in xHTML 1.0 -transitional. The colors for the body and the titles -are placed directly on the page so the links are easy to follow. -The title of level 1 is used only once (at the top), level 2 is -the title of the document and levels 3 and 4 are then used for +transitional. The title of level 1 is used only once (at the top), +level 2 is the title of the document and levels 3 and 4 are then used for the subtitles. If a list is used instead using smart anchors; then that starts at the top, just after the title of level 2. Paragraphs are contained in the tags <p></p>. @@ -312,7 +291,7 @@ of the code via the online validator of the W3C.

Diff and patch

The utilities diff and patch are command-line tools for creating and implementing a file containing differences between two files. @@ -330,34 +309,35 @@ $ patch file.orig file.diff - -

- -

-Last modification : 2009-06-13 21:15:00 - -Top of the page -

- -

- - -

- -

+ + diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/book.css --- a/en/doc/cookbook/book.css Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,170 +0,0 @@ -/* - CSS style for SliTaz GNU/Linux *book. - Pankso 2007 - www.slitaz.org -*/ - -body { - font: 13px sans-serif, vernada, arial; - background: #222222; - margin: 0; - padding-bottom: auto; -} - -#header { - background: #BFB06B url(images/css/header.png) repeat-x top; - color: black; - height: 50px; - border-top: 1px solid black; - border-bottom: 1px solid black; -} -#quicknav { - margin-right: 6px; - text-align: right; - font-size: 12px; - } -#quicknav { - margin-right: 6px; -} - -#quicknav a { - background: inherit; - color: white; -} - -#quicknav a:hover { - background: inherit; - color: #222222; -} - -/* content. */ - -#content { - background: white url(images/css/content-tl.png) no-repeat top left; - color: black; - padding: 20px; - margin: 30px 50px 0px 50px; - width: auto; - text-align: justify; -} - -#content li { - line-height: 1.5em; - text-align: left; -} - -/* Footer. */ - -#footer { - font-size: 11px; - font-weight: bold; - background: #eaeaea url(images/css/footer-bl.png) no-repeat bottom left; - color: black; - height: 20px; - padding: 6px 0px 0px 10px; - margin: 0px 50px 0px 50px; - width: auto; - text-align: center ; -} - -#footer a { - text-decoration: none; - background: #eaeaea; - color: #3E1220; -} - -#footer a:hover { - background: #eaeaea; - color: #DF8F06; -} - -/* Legal information */ - -#copy { - font-size: 11px ; - text-align: center ; - background: transparent; - color: #a8a8a8; - padding-top: 20px; -} - -#copy a { - background: inherit; - color: #a8a8a8; -} - -#copy a:hover { - background: inherit; - color: #EDEDED; -} - -/* Div for round corners. */ - -.content-right, .footer-right { - width: 16px; - color: white; - background-color: #333333; -} -.content-right { - background: url(images/css/content-tr.png) no-repeat top right; - height: 16px; - right: 50px; - top: 82px; - position: absolute; -} - -.footer-right { - background: url(images/css/footer-br.png) no-repeat bottom right; - height: 20px; - float: right; -} - -/* General HTML entities for content. */ - -h1 { - margin: 0px 0px 0px 16px; -} - -h2 { - margin: 12px 0; - color: #484B7C; - background: white; -} - -h3 { - font-weight: bold; - color: #6c0023; - background: white; -} - -a { - text-decoration: underline; -} -a:hover { - text-decoration: none; -} - -pre { - padding: 5px; - color: black; - background: #e1e0b0; -} -pre.script { - padding: 10px; - color: black; - background: #e8e8e8; - border: 1px inset #333333; -} - -code { - font-size: 12px; - color: #669900; - background: transparent; -} - -li { - line-height: 1.4em; -} - -hr { - border: 0pt none; -} diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/boot-scripts.html --- a/en/doc/cookbook/boot-scripts.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,203 +0,0 @@ - - - - SliTaz Cookbook (en) - Boot Scripts - - - - - - - - - - - - - - - -

- -

Boot scripts

-The startup and shutdown scripts with their configuration files. -

- -

SliTaz and startup.
/etc/init.d/* - Directory of scripts and daemons.
/etc/init.d/rcS - Primary initialization script.
Specific scripts and daemons - Scripts and - daemons with a very specific task.
/etc/inittab - Configuration file init.

- - -

SliTaz and startup

- -

-SliTaz does not use a level of execution (runlevel), the -system is initialized via a primary script and its main -configuration file. This script itself launches some other smaller -scripts which deal with the internationalization or the -commands placed for the system to start. -

- - -

/etc/init.d/* - Directory of scripts and daemons

-The directory /etc/init.d contains all of the rc scripts, -scripts finishing with '.sh' are simple shell scripts and -daemons such as 'dropbear' or 'lighttpd' are scripts -that launch a service. The daemon scripts can start, stop or -restart through the command: -

 # /etc/init.d/daemon [start|stop|restart]
-

-On SliTaz you will find a /etc/init.d/README describing the -basic function of rc scripts. Also note that all startup -scripts and daemons can call upon the /etc/init.d/rc.functions -file. This file makes it possible to include various functions -in rc scripts. For example, SliTaz uses a function status to -check whether the previous command has succeeded (0) or not. -

- - -

/etc/init.d/rcS - Primary initialization script

-The /etc/init.d/rcS script configures all the -basic services and initializes the base system. It begins by -mounting the filesystems and starts services like syslogd, klogd, -mdev and cleans up the system and so on. It -uses the configuration file /etc/rcS.conf to locate which daemons -and scripts to launch at startup. You can browse the script -to know which commands are executed: -

 # nano rootfs/etc/init.d/rcS 
-

- - - -

Specific scripts and daemons

- -

bootopts.sh - LiveCD mode options

-This script is used to configure the LiveCD options passed -at boot time and is readable via the /proc/cmdline file. -This is the script that allows you to use a USB key or -external hard disk /home partition with the option home=usb -or home=sda[1-9]. Note, it can also directly specify the language and -keyboard parameters. -

- -

network.sh - Initializing the network

-This script searches the network.sh configuration file -/etc/network.conf for the network interface to use; if one wants to -launch the DHCP client (or not) or if you want to use a fixed -(static) IP. On SliTaz the /etc/init.d/network.sh -script configures the network interfaces to start using the -information contained in /etc/network.conf. If the variable -$DHCP is equal to yes, then the /etc/init.d/network.sh -script launches the DHCP client on the $INTERFACE interface. -

- -

i18n.sh - Internationalization

-SliTaz backs up the configuration of the default locale in -/etc/locale.conf which is read by /etc/profile at each -login. The /etc/locale.conf is generated during boot time -thanks to the /etc/i18n.sh script. This script launches the -'tazlocale' application if /etc/locale.conf doesn't exist. -We use the same process for the keyboard layout using 'tazkmap' -and the /etc/kmap.conf configuration file. Both applications -are installed and located in /sbin and use dialog and the -ncurses library. The script also checks whether the -configuration file for the time zone /etc/TZ exists, -otherwise it creates one relying on the keyboard configuration. -

- -

local.sh - Local commands

-The /etc/init.d/local.sh script allows the system administrator -to add local commands to be executed at boot. Example: -

#!/bin/sh
-# /etc/init.d/local.sh: Local startup commands.
-# All commands here will be executed at boot time.
-#
-. /etc/init.d/rc.functions
-
-echo "Starting local startup commands... "
-
-

- -

rc.shutdown

-This script is invoked by /etc/inittab during system shutdown. -It also stops all daemons via the variable RUN_DAEMONS in -the primary /etc/rcS.conf configuration file. -

- - -

/etc/inittab - Configuration file init

-The first file read by the Kernel at boot. It defines the -initialization script (/etc/init.d/rcS), shells (ttys) and -actions in the event of a reboot or disruption. You will find -a complete example with accompanying notes in SliTaz tools: -

# /etc/inittab: init configuration for SliTaz GNU/Linux.
-# Boot-time system configuration/initialization script.
-#
-::sysinit:/etc/init.d/rcS
-
-# /sbin/getty respawn shell invocations for selected ttys.
-tty1::respawn:/sbin/getty 38400 tty1
-tty2::respawn:/sbin/getty 38400 tty2
-tty3::respawn:/sbin/getty 38400 tty3
-tty4::respawn:/sbin/getty 38400 tty4
-tty5::respawn:/sbin/getty 38400 tty5
-tty6::respawn:/sbin/getty 38400 tty6
-
-# Stuff to do when restarting the init 
-# process, or before rebooting.
-::restart:/etc/init.d/rc.shutdown
-::restart:/sbin/init
-::ctrlaltdel:/sbin/reboot
-::shutdown:/etc/init.d/rc.shutdown
-
-

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/build-bot.html --- a/en/doc/cookbook/build-bot.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,181 +0,0 @@ - - - - SliTaz Cookbook (en) - Build Bot - - - - - - - - - - - - - - - -

- -

Build Bot (tazbb)

- -

-The goal of Tazbb is to automate, test and report packages built inside a wok. -Run tazbb usage for the list of available commands with -a short description. -The Status of the Tank Build Bot via a Tazbb web interface is at -bb.slitaz.org and for collaboration, -use the Tazbb Wiki. -

- -

- - -

How it works

-Tazbb can be run by a cron job and checks the last commit done by contributors -and then cooks the modified packages. Runnning 'tazbb cook-commit' will just -rebuild the last modified packages. To rebuild all missing, modified or unbuilt -packages you must use the 'tazbb cook-all' command. -

-Generating a report will source all the receipts in the wok and check if a package -file exists, if not we add the package name to the current cooklist. For -existing packages we compare all the files' dates in the Hg wok (receipt, stuff) -against the package.tazpkg file date, if it differs we add the package to the cooklist. -

-Tazbb must also look in the chroot wok to check if the package is already built, (there -should be a taz/ directory), if not we log it and add it also to the cooklist. -All packages are cooked with a 'script'. Logs for cooked packages are stored in -$LOG_DIR and a link exists for the web interface so that developers can easily check -for bugs. -

-When run with the option 'cook' - Tazbb will also remove old and corrupted packages -and then execute 'tazwok genlist --text' to rebuild all the packages lists. To work -properly, the Tazwok and Tazbb configured paths must match. The Tazbb system wide -configuration file is: /etc/slitaz/tazbb.conf -

- - -

Commands

-Tazbb can be installed on your machine and run manually from the command -line - just type 'tazbb usage' for a list of available functions. Tazbb can be -run in report mode and made to display more information with the '--verbose' option. -

- - -

Hg and chroot Wok

-Tazbb uses 2 woks: a clean Hg wok and a wok to build packages in a chroot environment. -Each time Tazbb is called; the Hg wok is updated and copied to the build -wok, so we avoid messing with build results and can also manually modify -receipts or patches directly without affecting the main Hg. If configured -correctly 'tazdev update-wok' can also update the Hg wok and copy files. -

- - -

Log files

-Tazbb uses existing tools such as tazwok to build packages, but generates its own -log files and has its own database stored in a text file. The log files are -available through the web interface and the default path for the files is: -/var/log/tazbb -

- - -

Web interface

-Tazbb logs all its activity to log files and a cooklist. This information -can be displayed through a nice web interface so developers can have a quick -overview of the last build results. The Tazbb package provides a PHP web interface, -CSS stylesheets and images installed by default in /var/lib/tazbb/web. -A symlink is created in /var/www/vhosts by a package, it provides -easy access to the generated log files through a virtual host or you can use: -http://localhost/vhosts/bb -

- - -

Hg hook

-Mercurial offers a powerful mechanism to perform automated actions in response -to events that occur in a repository. The name Mercurial uses for one of these -actions is a hook. So Tazbb can be run each time a commit is done in the wok -through a simple hook in the .hgrc file of the repository. Example: -

-[hooks]
-commit = tazbb cook-commit
-

- - -

Cron Job

-Tazbb can also be run by a cron tab, so each new commit in the wok will cook the -correct package each time you want. Cron can also be used to refresh the report -or run a full cook. If the last cook is not yet finished or if tazbb has been -run by hand (and is still running), it will exit due to a lock file in /var/lock. -Example of a cron job to 'tazbb cook commit' every 2 hours and cook all missing, modified -or unbuilt packages each night: -

-*/2 * * * * /usr/bin/tazbb cook-commit
-03 02 * * * /usr/bin/tazbb cook-all
-

- - -

Database Files

blocked : List of blocked packages
cooklist : Current or next cooklist
corrupted : Corrupted packages list
packaged : All packages from the build wok
removed : Last removed packages
report : Last report from check_{wok,commit}
running : Current task running
summary : Last summary for the web interface
unbuilt : List of unbuilt packages

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/build-host.html --- a/en/doc/cookbook/build-host.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,172 +0,0 @@ - - - - SliTaz Cookbook (en) - Build Host - - - - - - - - - - - - - - - -

- -

SliTaz Build Host (tank)

- -

-SliTaz build host info and howto. -

- -

- - -

Folders in: /home/slitaz

cooking/ - Cooking chroot and flavors.
stable/ - Stable tree.
repos/ - All the project repos (where the commits are pushed).
www/ - Virtual hosts (website, hg, boot, people, etc).

- - -

Using tazdev

-To help maintain the mirror, flavors and other services, the tazdev command -is used. It is mostly configured for the cooking version. Usage: -

 $ tazdev usage
-

- - -

Cooking undigest packages

-You can use the undigest wok in the chroot environment to cook some -non supported packages. If you maintain official packages and they cook -successfully on tank, then you can test on your local machine and commit -in the official wok. Mirror maintainers will then rebuild and upload the -packages on mirror.slitaz.org. -

-To build packages in the undigest wok and in the chroot environment: -commands are sometimes better than a long text: -

 $ ln -s /home/slitaz/cooking/chroot/home/undigest .
-

-You can copy files with gFTP-sftp-scp directly into the wok or from the -current directory: -

 $ cp -a package undigest/wok
- $ su -c "tazdev chroot"
- /# cd home/undigest
- /# tazwok cook package
- /# exit
- $ ls undigest/packages
-

- - -

Cooking official packages

-Maintainers have root access and some have write access to the -main mirror at mirror.slitaz.org, if you want to help in this task please -contact one of the active developers (check hg repos). -

-Everything is cooked in a chroot environment, the default path for the build -wok is $CHROOT/home/slitaz/wok. Some changes can be made directly in this wok: the -real Hg is copied into the chroot by tazbb (Build Bot). To chroot in cooking: -

 # tazdev chroot
-

-Cook all the last commited packages or cook everything with 'cook-all', note -that comparison it not required if you know which packages to cook. If you -want to force the cooking of some of the packages by tazbb, you can then -clean with tazwok. By default tazbb cooks only the last commit: -

 /# tazbb cook-commit
-

-If needed (tazbb does this automatically), you can remove all the old packages -and then rebuild the lists manually: -

 /# tazbb clean-up
- /# tazwok gen-list --text
- /# exit
-

-If you have write access to the mirror, you can make a dry-push to check -and then upload; push will also remove any old packages on the mirror. -

- - -

Stable packages

-Packages for the stable release are also built in a chroot environment like -the Cooking packages: -

 # tazdev chroot stable
-

- - -

Upload by hand on mirror.slitaz.org

-Mirror maintainers can upload by hand with tazdev (-dp for a dry push): -

 # tazdev -p $USER
-

- - -

Update website by hand

-The Website and packages web interface are updated nightly by cron and can -also be updated by hand (used on the day of release for example): -

 # tazdev update-www
-

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/favicon.ico Binary file en/doc/cookbook/favicon.ico has changed diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/images/css/Thumbs.db Binary file en/doc/cookbook/images/css/Thumbs.db has changed diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/images/css/content-tl.png Binary file en/doc/cookbook/images/css/content-tl.png has changed diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/images/css/content-tr.png Binary file en/doc/cookbook/images/css/content-tr.png has changed diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/images/css/footer-bl.png Binary file en/doc/cookbook/images/css/footer-bl.png has changed diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/images/css/footer-br.png Binary file en/doc/cookbook/images/css/footer-br.png has changed diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/images/css/header.png Binary file en/doc/cookbook/images/css/header.png has changed diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/index.html --- a/en/doc/cookbook/index.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,82 +0,0 @@ - - - - SliTaz Cookbook (en) - - - - - - - - - - - - - - - -

- -

Developers documentation

- -

Wok & Tools - SliTaz Package Tools.
Receipts - Receipts for creating SliTaz - packages.
Build Host - SliTaz Build host (tank).
Build Bot - SliTaz Build bot (tazbb).
Boot Scripts - The startup and shutdown - scripts.
SliTaz Tools - The Toolbox.
Release Tasks - List of things to do before - publishing a new version.
Root cdrom (rootcd) - Descriptions of files - contained on the cdrom.

- -

About this Cookbook

-The Cookbook brings together information about the project management, operation -and development of the distribution. It talks about creating packages, receipts, -the wok, and scripts that start SliTaz. -

-At the base of the Cookbook is the Scratchbook, -this contains instructions to create your own LiveCD by describing the creation -of the first ever public version of SliTaz in March 2007. The Cookbook is modified -by the SliTaz community and steadily improved, it provides technical instructions -about the project useful to developers and advanced users. -

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/receipts.html --- a/en/doc/cookbook/receipts.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,334 +0,0 @@ - - - - SliTaz Cookbook (en) - Receipts - - - - - - - - - - - - - - - -

- - -

Receipts

- -

-This document describes the opportunities offered by the receipt used by -Tazwok to compile and generate packages for SliTaz and Tazpkg through -The wok and tools. The receipt for a package is -also used by Tazpkg to install/uninstall and provide information about a -.tazpkg package. Each receipt begins with a comment in English: -

-# SliTaz package receipt.
-

- -

Variables

-The first 5 variables should always be present and defined. They respectively -configure the package ($PACKAGE), its version, its category, provide a short -description and the name of the maintainer. Example for the package, file -manager Clex: -

-PACKAGE="clex"
-VERSION="3.16"
-CATEGORY="base-apps"
-SHORT_DESC="Text mode file manager."
-MAINTAINER="pankso@slitaz.org"
-

- -

Variables (optional)

-Tazwok also knows how to use various optional variables. It can, for example, -use the name of another source package. There are also variables that are -used by Tazpkg to manage dependencies or provide information about the package. -

- -$DEPENDS: Set dependencies, there may be several dependencies -seperated by a space or on several lines. This variable is used mainly by -Tazpkg when installing the package and Tazwok to build large packages such -as Xorg. Example for Clex which depends on ncurses: -

-DEPENDS="ncurses"
-

- -$BUILD_DEPENDS: Set compilation dependencies, again seperated -by a space or several lines. This variable is used by Tazwok during the -cooking of a package. Example: -

-BUILD_DEPENDS="ncurses-dev"
-

- -$TARBALL : The archive is a source with the extension (tar.gz, -tgz or tar.bz2). In general, the variables $PACKAGE and $VERSION are used to -just change the extension, it helps to upgrade the package without changing -the $VERSION variable. Generic example (see also $SOURCE example): -

-TARBALL="$PACKAGE-$VERSION.tar.gz"
-

- -$WEB_SITE : The official website of the package. It may be that -some libraries have no website, in this case, there is no need to specify a -URL. Note Tazwok and Tazpkg both expect to find a URL with the complete HTTP: -

-WEB_SITE="http://www.clex.sk/"
-

- -$WGET_URL : URL to download the source file. In general the -variable $TARBALL should be used to facilitate the updating of the package -without changing the $VERSION. Using a configuration file, Tazwok also -configures by default 3 mirrors: $GNU_MIRROR for the GNU mirror, $SF_MIRROR -for SourceForge and XORG_MIRROR for mirroring the graphical server Xorg. -Example for Clex: -

-WGET_URL="http://www.clex.sk/download/$TARBALL"
-

- -$CONFIG_FILES : Some packages provide customized -configuration files. The $CONFIG_FILES variable provides a list of these -files that can be saved by the 'tazpkg repack-config' command. -These files are not overwritten when reinstalling the package if they already -exist and the package can be successfully recreated with 'tazpkg repack', -(even if they have been modified since). Netatalk for example: -

 CONFIG_FILES="/etc/netatalk/AppleVolumes.* /etc/netatalk/*.conf"
-

- -$SUGGESTED : Lists useful packages without being essential. -Also used to activate optional features. -

- -$WANTED : SliTaz packages normally depend on the compilation of -a source package. Sometimes the receipt of a package requires no compilation -of rules, then $WANTED is used to copy files from the source of another -package by using the variable $ src. -

- -$SOURCE : It may be that the Tazpkg package name differs from -the name of the source package. Example for Xorg packages, the name of Tazpkg -library X11 is 'xorg-libX11' and the name of the package source is libX11. -$SOURCE allows you to use the variables $src and $_pkg during the cooking of -a package. It should be noted that in the case of libX11, the name of the -source archive becomes $SOURCE-$VERSION.tar.gz. -

- -$PROVIDE : Some packages offer the same functionality, for -instance the web server was at first lighttpd; now apache is available. -All packages dependent on a web server refer to lighttpd. -The $PROVIDE="apache" variable in the apache receipt says -that packages dependent on lighttpd do not need to install the lighttpd -package if apache is already on the system. Some packages may vary according -to the webserver you choose, ie. the php package is dependent on lighttpd, -as is php-apache on apache. The PROVIDE="php:apache" in the -apache receipt says that you must install php-apache instead of php, if -apache is already on the system. Therefore each package dependent on php -will install either php-apache or php according to the webserver on the -system. This variable also chooses packages compiled with different options. -The PROVIDE="epdfview:cups" in the epdfview-cups receipt allows -you to install epdfview with printer support via cups if cups is already on -the system. -

-You can also define virtual packages with this variable. -The lines PROVIDE="libgl" in the mesa package and -PROVIDE="libgl:nvidia" in the nvidia-glx package, define that -libgl is an optimized version when the nvidia package is installed. -

- -$SELF_INSTALL : Certain packages use commands provided by -the package itself in the post_install function. To install this package -into a directory other than root and still be able to use these commands, -the package must have been installed in / in earlier stages. The line: -SELF_INSTALL=1 alerts tazpkg to this feature. -

- -

Variables automatically generated by Tazwok

-Certain factors are known only during the cooking of -a package or after the package has been cooked. Tazwok -will add them to the receipt automatically. -

- -$PACKED_SIZE : Tazpkg file size. -

- -$UNPACKED_SIZE : Space taken up by the package after -installation. -

- -$EXTRAVERSION : Some packages have 2 different versions. -This is in case of modules added to the Linux kernel, such as squashfs, -because the module depends on the version of the kernel with which it was -compiled. In this case $EXTRAVERSION contains the kernel version and Tazwok -determines the module from the contents of /lib/modules. -

- -

Variables used in functions

-Tazwok configures several variables that facilitate the compilation and -construction of Tazpkg packages. These variables are controlled automatically -by Tazwok using the information contained in the receipt; they can be used -by the functions compile_rules and genpkg_rules described in the chapter -Functions. -

- -$src : Defines the path to the directory of unarchived sources. -

- -$_pkg : Defines the path to the compiled binaries installed via -'make DESTDIR=$PWD/_pkg install'. This variable is used to copy the generated -files and create Tazpkg packages. -

- -$fs : Defines the path to the pseudo filesystem (fs) in each -package. The 'fs' of the package corresponds to the root of the system, a bit -like Clex will for example be in $fs/usr/bin/clex. Note the need to create the -necessary directories via function genpkg_rules() before copying the files. -

- -$CONFIGURE_ARGS : This variable is defined in the Tazwok -configuration file (tazwok.conf). It allows you to specify generic optimization -arguments during construction of a package. Default is the i486 architecture. -

- -

Functions

-A receipt may contain 4 functions. Tazwok knows how to deal with functions -containing compilation rules (compile_rules) and rules used to generate a -package (genpkg_rules). These functions may contain all sorts of GNU/Linux -standard commands, such as sed, awk, patch and variables automatically -configured. -

- -

compile_rules()

-To compile a package you can use the variable $src to move (cd) in the -directory of sources and use $CONFIGURE_ARGS to include arguments from the -Tazwok configuration file. To build the package you usually launch 'make' -without any arguments, and to install the package into the directory _pkg, -it is necessary to use the command 'make DESTDIR=$PWD/_pkg install'. Generic -example: -

-# Rules to configure and make the package.
-compile_rules()
-{
-	cd $src
-	./configure --prefix=/usr --infodir=/usr/share/info \
-	--mandir=/usr/share/man $CONFIGURE_ARGS
-	make
-	make DESTDIR=$PWD/_pkg install
-}
-

- -

genpkg_rules()

-To generate a tazkg package we must specify commands in the function -genpkg_rules. In this example we create a psuedo directory -usr/ in the filesystem of the package, copy the whole -binary(s) and finally use strip to clean the files: -

-# Rules to gen a SliTaz package suitable for Tazpkg.
-genpkg_rules()
-{
-	mkdir -p $fs/usr
-	cp -a $_pkg/usr/bin $fs/usr
-	strip -s $fs/usr/bin/*
-}
-

- -

pre_install() and post_install()

-These 2 functions are initiated by Tazpkg when installing the package. They -must be defined before generating the .tazpkg package with Tazwok. If no rules -are given for these functions, they have no raison d'etre and can be removed. -Example using echo to display some text (no function should be empty): -

-# Pre and post install commands for Tazpkg.
-pre_install()
-{
-	echo "Processing pre-install commands..."
-}
-post_install()
-{
-	echo "Processing post-install commands..."
-}
-

- -

clean_wok()

-This function helps to define additional commands to be run when cleaning the wok, -it is useful to delete files or directories that are not supported by Tazwok. -

# clean commands for Tazwok.
-clean_wok()
-{
-	rm -rf $WOK/$PACKAGE/vim71
-}
-

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/reltasks.html --- a/en/doc/cookbook/reltasks.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,88 +0,0 @@ - - - - SliTaz Cookbook (en) - Release tasks - - - - - - - - - - - - - - - -

- -

Release tasks

- -

-Things to do before publishing a new version. -

- -

Check list

Release version is specified by /etc/slitaz-release, this file - is controlled by slitaz-base-files. Base files are tagged just before - a stable release to change the version string and let Tazpkg use the new - packages.
Check that the SliTaz version specified in /etc/issue message is - the same as displayed in isolinux.msg.
Add and check that documents and images are in the root of the CD - ie. - README, index.html, style.css and the directory of images. All files are - in the slitaz-tools archive; just copy the addfiles/ and - regenerate the ISO.
Test, test, and test ...
Prepare the website announcement and RSS feeds. The Mailing list is used - for translation and any text should be submitted 1 or 2 days before release.

- -

Stable documentation

-SliTaz stable release provides the release notes on the LiveCD through -the package slitaz-doc, the repos are tagged just before release -and are archived on the mirror. After the wok has been copied to wok-stable, -the docs are back to a cooking cycle and just provide an index with basic -information. On the system, docs are located in /usr/share/doc/slitaz, a -desktop file and icon are provided in the sources package and can be used -to have quick access to the documentation. -

SliTaz Doc repo
SliTaz Doc on the Labs

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/rootcd.html --- a/en/doc/cookbook/rootcd.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,205 +0,0 @@ - - - - SliTaz Cookbook (en) - RootCD - - - - - - - - - - - - - - - -

- -

Rootcd

-Descriptions of files contained on the cdrom. -

- -

- - -

Syslinux/isolinux

-Syslinux and the main bootloader of SliTaz - we use the isolinux version to start -the system contained on the CD-ROM. Simple effective and configurable, isolinux -was installed during the creation of the base system. -The binary is named isolinux.bin and its configuration file: isolinux.cfg. -Here's an example of isolinux.cfg using isolinux.msg to post the splash -image and displayable help files via F1, F2, F3 and F4. You will find the -files help.txt, options.txt, etc in SliTaz tools. -

display isolinux.msg
-default slitaz
-label slitaz
-	kernel /boot/bzImage
-	append initrd=/boot/rootfs.gz rw root=/dev/null vga=788
-implicit 0	
-prompt 1	
-timeout 80
-F1 help.txt
-F2 options.txt
-F3 isolinux.msg
-F4 display.txt
-

- - -

Isolinux boot splash image

-We can configure isolinux to display a splash image when booting SliTaz or -any other operating system using isolinux. This image has a particular -format .lss, suitable for Syslinux, and must be indexed using the 16 color -mode. You can use the official logo, ppmforge, imagemagick, GIMP or -other tools to create your image. -

-The Syslinux file (sample/syslogo.lss) provides an official logo which you can -directly use by copying to the root of the CD-ROM. SliTaz -provides a logo (rootcd/boot/isolinux/splash.lss) which you can locate in -SliTaz tools. -To display a splash image when booting, it's necessary that the 'display' option calls -the isolinux.msg file which loads the *.lss format image. Note that the isolinux.msg file -uses 24 ASCII characters. Example using 'echo' and an isolinux.msg file incorporating a .lss -splash image: -

 # echo -e "\24isplash.lss\n" > isolinux.msg
-

-You can also add a text message underneath the splash image by modifying this -file with your favorite text editor, echo or cat and so on. -

- - -

ISO bootable with isolinux

-To create a bootable ISO image using isolinux and genisoimage: -

 # genisoimage -R -o slitaz-test.iso -b boot/isolinux/isolinux.bin \
-   	-c boot/isolinux/boot.cat -no-emul-boot -boot-load-size 4 \
-   	-V "SliTaz" -input-charset iso8859-1 -boot-info-table rootcd 
-

- - -

GRUB

-GRUB (GRand Unified Bootloader) is a bootloader distributed by the GNU -project. This is what is used during installation to a hard drive; it can -boot Linux, BSD, HURD and Window$. GRUB provides stage2_eltorito -to start the ISO images. To find stage2_eltorito on your system, you need -to have the GRUB package installed. Finally you copy stage2_eltorito to the -root of the cdrom. Note that SliTaz provides a (.tazpkg) package -grub-0.97 that you can find on the mirrors or you can rebuild grub-0.97 -from sources. Sample copy of the stage2_eltorito image from a -Debian system or SliTaz: -

 # mkdir -p rootcd/boot/grub
- # cp /usr/lib/grub/i386-pc/stage2_eltorito \
-   	rootcd/boot/grub
-

-The GRUB configuration file is called menu.lst and can be edited with your -favorite text editor. Example: -

# By default, boot the first entry.
-default 0
-
-# Boot automatically after 20 secs.
-timeout 20
-
-# Change the colors.
-color yellow/brown white/black
-
-title  SliTaz GNU/Linux 1.0 (vga 800x600) (Kernel 2.6.20)
-       kernel /boot/bzImage root=/dev/null vga=788
-       initrd /boot/rootfs.gz
-
-title  SliTaz GNU/Linux 1.0 (vga 1024x768) (Kernel 2.6.20)
-       kernel /boot/bzImage root=/dev/null vga=771
-       initrd /boot/rootfs.gz
-

- - -

ISO bootable with GRUB

-To create a bootable ISO image using GRUB and genisoimage or mkisofs: -

 # genisoimage -R -o slitaz-test.iso -b boot/grub/stage2_eltorito \
-   	-no-emul-boot -V "SliTaz" -boot-load-size 4 -input-charset iso8859-1 \
-   	-boot-info-table rootcd
-

- -

Memtest86

-The application memtest86 is a tool to test random access memory -(RAM). We download the utility into the src directory, decompress the archive, -and copy the (precompiled) binary: -

 # mkdir -v -p src
- # cd src
- # wget http://www.memtest86.com/memtest86-3.2.tar.gz
- # tar xzfv memtest86-3.2.tar.gz
- # cd memtest86-3.2
- (# more README)
- # cp precomp.bin ../../rootcd/boot/memtest
- # cd ../..
-

-Once installed, you can add the label for the memtest86 file to isolinux.cfg, -specifing the path to the utility: -

label memtest
-	kernel /boot/memtest
-

-Or if you want to use GRUB, here's the line to launch memtest86: -

title 	Memtest86 (Test system memory)
-kernel 	/boot/memtest
-

-Once the lines are added, you can then create a new ISO and test. -

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/slitaz-tools.html --- a/en/doc/cookbook/slitaz-tools.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,92 +0,0 @@ - - - - SliTaz Cookbook (en) - SliTaz Tools - - - - - - - - - - - - - - - -

- -

SliTaz Tools

-The SliTaz Toolbox -

Mercurial repository.
*box - dialog/GTKdialog.
Archives source: - HTTP.

- -

-The SliTaz Tools contain useful scripts that enable you to -customize SliTaz, such as a script to create a new initramfs -or an ISO image, Makefile, etc. The archive is also distributed -because it contains files that might be useful to hacker -type individuals... The tools are constantly evolving and -continue to expand, following the cycle of changes made by the -Cooking and Stable versions. -

- - -

Mercurial repository

-The SliTaz Tools have their own Mercurial repository on the -SliTaz server, they can be cloned via the command: -

- $ hg clone http://hg.slitaz.org/slitaz-tools/
-

- - -

*box

-Mountbox, Netbox, Bootfloopybox, Tazlocale, etc are tools -for creating SliTaz using dialog (ncurses) or GTKdialog; -the scripts are contained in the directory tinyutils/. -Desktopbox has the ability to be able to launch -various boxes (desktopbox usage) scripted or created with Glade3. -

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/template.html --- a/en/doc/cookbook/template.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,68 +0,0 @@ - - - - SliTaz Cookbook (en) - Template - - - - - - - - - - - - - - - -

- -

Template

- -

-DESC -

- -

List
List
List

- - -

Title

-CONTENT -

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - diff -r 111e058c9eff -r 18040398d744 en/doc/cookbook/wok-tools.html --- a/en/doc/cookbook/wok-tools.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,220 +0,0 @@ - - - - SliTaz Cookbook (en) - Wok & Tools - - - - - - - - - - - - - - - -

- -

Wok & Tools

- -

- - -

Overview

-With the passing of time, the SliTaz project created a variety of small -utilities to rebuild the system from source automatically. Tazwok is used -to compile and generate code (cook to cook) via instructions found in the -receipts. The project also offers an archive of tools (SliTaz tools) -containing various small utilities, examples and configuration files. -The distribution generator Tazlito is designed for users and -developers. Tazlito will retrieve and reconstruct a LiveCD ISO image and -generate a distribution flavor from a list of packages, a configuration file -and a description. The utilities are all distributed as a source archive -and are installed by default on SliTaz. Developers and future contributors -can refer to the development page that provides information on SliTaz project -management. -

- -

Tazwok and the wok

-The idea is to use a directory (wok) containing all the available packages, each package contains -at least one receipt to download, unpack, compile and generate the binary package. To operate, -Tazwok also needs to create a directory to store downloaded sources ($SOURCES_REPOSITORY) and a -repository of generated packages ($PACKAGES_REPOSITORY), these values can be configured using the -/etc/tazwok.conf file. -

- - -

Wok tools

-To begin, Tazwok must already be installed -on the system and the main development tools (binutils, compiler, libraries-dev, make) must be downloaded. -On Slitaz you need to install the meta-package slitaz-toolchain: -

 # tazpkg recharge
- # tazpkg get-install slitaz-toolchain
-

-To access the SliTaz repositories you need to install the mercurial package: -

 # tazpkg get-install mercurial
-

Get the wok

-Before working it is necessary to recover the wok from the Mercurial repositories or an archive of -the primary mirror (TuxFamily). Example using SliTaz to be built in /home/slitaz: -

 $ hg clone http://hg.slitaz.org/wok/ /home/slitaz/wok
-

-The archives are also available from the URL: -ftp://download.tuxfamily.org/slitaz/wok/. -Just take the latest version from the cooking or undigest directories. Before compiling your first package, -Tazwok must know where to look for the files. By default the path is /home/slitaz/wok, -you can change this or rename the wok you want to download. To view/check Tazwok paths that will be used -and the number of packages in the wok, you can use the Tazwok command stats: -

 # tazwok stats
-

- - -

Compile and generate packages

-Configure, compile, strip.., The way SliTaz generates a package can be put into a single command. -To avoid frustration, it is advisable to build your package without changing its receipt or seeking -dependancies. M4 is an ideal candidate for your first cook: -

 # tazwok cook m4
-

-Once the work is finished, the package is located in the directory specified by the configuration file -(default /home/slitaz/packages). If all went well, you can install the package on the host system -or use it to generate a LiveCD distribution via Tazlito. To create a new package you can use new-tree -with the option --interactive and read the documentation on the options provided by the -receipt. -

Cook-list - List of cooking

-To compile several packages with a single command, you can use a cooking list. There are example lists in -usr/share/examples/tazwok/cooklists on SliTaz, these are just text files with a package put on every line. -Cook-list example using mypkgs.cooklist: -

 # tazwok cook-list mypkgs.cooklist
-

- - -

Options during compilation of package

-You are free to use any options you want, it is necessary to respect the FSH, the docs in /usr/share/doc -and follow the Freedesktop standards (.desktop). Then it's just a question of choice, for example you can disable -support for XML, have smaller binaries for PHP and get rid of libxml2, but in the case of PHP, it's not worth the -cost in terms of loss of functionality. If you have any doubts, look at the receipts and compiler options in -compile_rules. -

Optimization

-The official SliTaz packages are optimized for i486, the optimization arguments used to configure are specified in -/etc/tazwok.conf and can be called via the variable $CONFIGURE_ARGS. -If you want to compile a package with different arguments, you can modify the Tazwok configuration file: -

CONFIGURE_ARGS="--build=i486-pc-linux-gnu --host=i486-pc-linux-gnu"
-

- - -

Files included or excluded packages

-Generally the base packages contain no man, info, doc or static libraries, we have to create them via a package-doc -or a package-dev. Note that SliTaz is not intending to use the man or info command, so there's no manual or GNU -info file. The creation of packages containing docs is really optional, especially if the material is in English -(I say). By contrast a piece of text on the package in the Handbook is more appreciated. -

-In terms of configuration, whenever possible, the aim is to offer basic configuration files to run the package -directly. In the case of the web server LightTPD package, SliTaz supplies configuration files and startup scripts -located in /etc/init.d (documented in the Handbook). For a new package, you are free to choose its default -configuration depending on what you think is easiest for the end user. On SliTaz you have /usr/share/examples -for example configurations and other kinds of useful infomation. -

- - -

Categories of packages

-The categories of packages exist only for informational purposes and are not fixed, the idea is to classify -packages so that a web page can be generated each night recovering data in the package receipt. For the short term, place -developement packages in 'devel', Xorg in 'x-window' and the variety of new packages in 'extra' -

- - -

Structure of a package in the wok

-The structure of the packages in the wok should always be respected so that Tazwok can find the correct files and directories. -Possible contents of a package (note the directory taz/ is created at time of cooking): -

stuff/ : The material used to configure, compile and generate the package - (patch(es), Makefile, pseudo fs, etc).
taz/ : Directory tree containing the package Tazpkg generated, the compressed package is stored - in the directory specified by $PACKAGES_REPOSITORY in the Tazwok configuraton file.
receipt : The receipt (see - receipts).
description.txt : (optional) The description of the package is copied to the root of the Tazpkg - package. Once installed, Tazpkg knows how do deal with this file via 'tazpkg desc pkgname'.

- - -

Structure of a Tazpkg package

-The SliTaz packages are cpio archives containing files and a filesystem compressed with gzip: -

fs/ : Pseudo filesystem containing all the files to install.
receipt : The receipt (see receipt.txt).
files.list : A list of files in the package.
description.txt : The description of the package (optional).

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/book.css --- a/en/doc/handbook/book.css Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,170 +0,0 @@ -/* - CSS style for SliTaz GNU/Linux *book. - Pankso 2007 - www.slitaz.org -*/ - -body { - font: 13px sans-serif, vernada, arial; - background: #222222; - margin: 0; - padding-bottom: auto; -} - -#header { - background: #BFB06B url(images/css/header.png) repeat-x top; - color: black; - height: 50px; - border-top: 1px solid black; - border-bottom: 1px solid black; -} -#quicknav { - margin-right: 6px; - text-align: right; - font-size: 12px; - } -#quicknav { - margin-right: 6px; -} - -#quicknav a { - background: inherit; - color: #222222; -} - -#quicknav a:hover { - background: inherit; - color: #EDEDED; -} - -/* content. */ - -#content { - background: white url(images/css/content-tl.png) no-repeat top left; - color: black; - padding: 20px; - margin: 30px 50px 0px 50px; - width: auto; - text-align: justify; -} - -#content li { - line-height: 1.5em; - text-align: left; -} - -/* Footer. */ - -#footer { - font-size: 11px; - font-weight: bold; - background: #eaeaea url(images/css/footer-bl.png) no-repeat bottom left; - color: black; - height: 20px; - padding: 6px 0px 0px 10px; - margin: 0px 50px 0px 50px; - width: auto; - text-align: center ; -} - -#footer a { - text-decoration: none; - background: #eaeaea; - color: #3E1220; -} - -#footer a:hover { - background: #eaeaea; - color: #DF8F06; -} - -/* Legal information */ - -#copy { - font-size: 11px ; - text-align: center ; - background: transparent; - color: #a8a8a8; - padding-top: 20px; -} - -#copy a { - background: inherit; - color: #a8a8a8; -} - -#copy a:hover { - background: inherit; - color: #EDEDED; -} - -/* Div for round corners. */ - -.content-right, .footer-right { - width: 16px; - color: white; - background-color: #333333; -} -.content-right { - background: url(images/css/content-tr.png) no-repeat top right; - height: 16px; - right: 50px; - top: 82px; - position: absolute; -} - -.footer-right { - background: url(images/css/footer-br.png) no-repeat bottom right; - height: 20px; - float: right; -} - -/* General HTML entities for content. */ - -h1 { - margin: 0px 0px 0px 16px; -} - -h2 { - margin: 12px 0; - color: #484B7C; - background: white; -} - -h3 { - font-weight: bold; - color: #6c0023; - background: white; -} - -a { - text-decoration: underline; -} -a:hover { - text-decoration: none; -} - -pre { - padding: 5px; - color: black; - background: #e1e0b0; -} -pre.script { - padding: 10px; - color: black; - background: #e8e8e8; - border: 1px inset #333333; -} - -code { - font-size: 12px; - color: #669900; - background: transparent; -} - -li { - line-height: 1.4em; -} - -hr { - border: 0pt none; -} diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/chroot-env.html --- a/en/doc/handbook/chroot-env.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,168 +0,0 @@ - - - - SliTaz Handbook (en) - Chroot environment - - - - - - - - - - - - - - - -

- -

Chroot environment

- -

-This document describes the necessary steps to create a chrooted environment, in order to change the root -of the system so that you can work. This makes it possible to compile, test and develop SliTaz without any risk to -the host system you're working on. The host system can be SliTaz installed to a hard drive or any other GNU/Linux system -such as Debian, Fedora, PCLinuxOS and so on. You can also create a chrooted environment in LiveCD mode -associated with USB media. The only prerequisite is to have a SliTaz ISO image available and a little -time. Note that all commands are carried out as system administrator (root). -

Prepare the environment

-To begin, we must extract the contents of the ISO image into the directory that will serve as our chroot. -The directory can be created any place you choose, we'll use a directory /home/slitaz/chroot-env. -To extract the contents of an ISO image, we must mount it in a loop directory and then copy the compressed -root filesystem (rootfs.gz) into the chroot directory. Assuming the ISO is in the current directory: -

 # mkdir /tmp/loop
- # mount -o loop slitaz-cooking.iso /tmp/loop
- # mkdir -p /home/slitaz/chroot-env
- # cp /tmp/loop/boot/rootfs.gz \
-   /home/slitaz/chroot-env
- # umount /tmp/loop
-

-Now we have a copy of the compressed filesystem, we must extract and unpack it (this is a cpio -archive compressed with either gzip or lzma). To complete this stage, we can remove the -rootfs which is no longer required: -

 # cd /home/slitaz/chroot-env
- # (zcat rootfs.gz 2>/dev/null || lzma d rootfs.gz -so) | cpio -id
- # rm rootfs rootfs.gz
-

-If the unpacking of the rootfs compressed with lzma fails; you can use the following method: -

 # unlzma rootfs.gz -S .gz 
- # cat rootfs | cpio -id
-

- -

Using the environment

-To begin using the chrooted environment, you just need to mount some virtual filesystems and use the chroot -command. To simplify things, we can write a small script automating the process. Example using the -chroot directory /home/slitaz/chroot-env and creating a script -chroot_in_env.sh in /home/slitaz. -On any systems other than SliTaz you can uncomment the lines about /dev and -/tmp - Note to save typing you can copy and paste: -

 # cat > /home/slitaz/chroot_in_env.sh << "EOF"
-

#!/bin/sh
-# Chroot in SliTaz to hack.
-#
-ROOTFS="/home/slitaz/chroot-env"
-
-# Mount virtual Kernel file systems and chroot.
-#
-#mount --bind /dev $ROOTFS/dev
-#mount --bind /tmp $ROOTFS/tmp
-mount -t proc proc $ROOTFS/proc
-mount -t sysfs sysfs $ROOTFS/sys
-mount -t devpts devpts $ROOTFS/dev/pts
-mount -t tmpfs shm $ROOTFS/dev/shm
-
-echo "Chrooting into $ROOTFS... "
-chroot $ROOTFS /bin/sh --login
-
-# Unmount virtual Kernel file systems on exit.
-#
-umount $ROOTFS/dev/shm
-umount $ROOTFS/dev/pts
-umount $ROOTFS/sys
-umount $ROOTFS/proc
-#umount $ROOTFS/tmp
-#umount $ROOTFS/dev
-
-echo "Exiting $ROOTFS chroot environment... "
-
-EOF
-

-To finish and test the environment, you just make the script executable and run: -

 # chmod +x /home/slitaz/chroot_in_env.sh
- # sh /home/slitaz/chroot_in_env.sh
-

To activate the network

-In order to have the network up to download and install some development packages, just start the -DHCP client on the correct interface. Example using eth1: -

 /# udhcpc -i eth1
-

Installing packages

-If the network is functional, just reload the list of packages and use tazpkg get-install to -install them. If a connection is not possible, you can download the packages from another system, copy them -to the chrooted environment and install them with the tazpkg install command. To install the basic -compilation tools: -

 /# tazpkg recharge
- /# tazpkg get-install slitaz-toolchain
-

-Once the environment is configured, you can compile applications from source to create packages, test scripts, etc. -The Cookbook should help you out here: -

Exit the environment

-To exit the chrooted environment, just type exit, the chroot_in_env.sh script will then end -by unmounting the virtual filesystems from the Linux Kernel: -

 /# exit
- #
-

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/cmdline.html --- a/en/doc/handbook/cmdline.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,368 +0,0 @@ - - - - SliTaz Handbook (en) - Commands - - - - - - - - - - - - - - - -

- -

Command Line Reference (cmdline)

- -

- - -

Introduction to the commands

-This document is intended as a quick reference for using commands on SliTaz via -a Linux terminal or a graphical terminal (xterm). There are many GNU/Linux commands -for file handling, system maintenance or network management. You can also browse -the web, chat on IRC, download files, edit scripts or even play games in text mode. -Note it is necessary to operate as root to assemble the hard drive or cdrom. -You can use the command su to become system administrator. -

- -

Help and list available commands

-Most GNU/Linux system commands have an option for providing information on -their use. For support on the use of a command, it is necessary to type the -command followed by the --help option. Example using the -cp command to copy files: -

- $ cp --help
-

-To list all the commands available on the system, you can simply press the -Tab button on the left of the keyboard twice. For commands provided by the -Busybox utility you can type busybox --help. -

- - -

List the files in a directory

-To list the files and folders contained in a directory, you can use the -ls command. For all options remember to use the --help -flag. To simply list the files in the current directory: -

- $ ls
-

-List all the files using the -al option: -

- $ ls -al
-

-List a directory: -

- $ ls /home/slitaz
-

- - -

Moving around directories

-To browse to the files, you can use the cd command: -

- $ cd /usr/share/doc
- Back to the parent directory:
- $ cd ..
-

-To go into the directory of the user (root = /root): -

- $ cd
- Or :
- $ cd ~
- Or :
- $ cd $HOME
-

- - -

Copy files

-The cp command copies files or folders. The example copies the -info.txt file in the current directory into the Documents directory: -

- $ cp info.txt Documents/
-

-Copy a whole directory. Here the command copies the Templates directory -into /home/hacker: -

- $ cp -a Templates /home/hacker
-

- - -

Create a new directory

-This command will create a new directory. The following command creates a -directory called Projects. It will be created in the directory /home of the -current user or in the directory which one is in. Note you can display -your current working directory with the pwd command: -

- $ mkdir Projects
-

-Creation of a directory named script-1.0 in the Projects folder: -

- $ mkdir Projects/script-1.0
-

-You can also create a directory tree with the -p parents option: -

- $ mkdir -p one/two/three/four
-

- - -

Delete files or directories

-The command rm lets you delete a file. Let's remove the -file work.txt which is in the current directory: -

- $ rm work.txt
-

-The command rm has several options. To delete a directory and -its contents, we use the -rf option. -Example: -

- $ rm -rf /home/hacker/Templates
-

-Note you can also use the -i option to remove files or directories and their contents interactively: -

- $ rm -ir /home/hacker/Templates
-

- - -

View files

-To read the contents of a file or script, you can use the -less, more or cat commands, or the web -browser Retawq. Examples with a README file, essential.txt, and -script.sh: -

- $ less -EM essential.txt
- or :
- $ more README
- or :
- $ cat /path/to/script.sh
-

-Display a text or html file with the web browser Retawq: -

- $ retawq /usr/share/doc/index.html
-

- - -

Edit files

-Editing text files, scripts, configuration files, etc, can be done easily using -the text editor GNU Nano in a console or graphical terminal. -Example with a file bookmarks.html (<Ctrl+X> to quit -and save): -

- $ nano Public/bookmarks.html
-

- - -

Cat

-You can use the cat command to create various text files. EOF signifies -End Of File, this is where the file ends. Example with a file packages.list, this -removes the current contents of the file and lets you add some new text: -

- $ cat > packages.list << "EOF"
- The text...
- and more text
- 
- EOF
-

-To append to the following text file, put two greater than signs -(>>) after cat, example: -

- $ cat >> packages.list << "EOF"
- The text...
- 
- EOF
-

- - -

Navigate the web

-Surf the web quickly and simply with the 'retawq' text-mode web browser. -Note that you can also use the local browser. You can then navigate easily -with the arrows on your keyboard - links are colored blue and can be -followed by pressing <ENTER>: -

- $ retawq http://www.slitaz.org/en
- or :
- $ retawq http://localhost/
-

- - -

Talk on IRC

-To discuss and transfer files via the many IRC servers available, SliTaz -provides Rhapsody. The IRC client is simple, fast and lightweight, providing -a pleasant, easy to handle ncurses configuration menu. To start the application -from a terminal connecting to server (irc.toile-libre.org) and joining #slitaz: -

- $ rhapsody
- /connect irc.freenode.net
- /join #slitaz
-

- -

Download files

-To download various file formats on the internet, you have the wget -command. To grab a simple html page, the contents of a folder or an entire -website: -

- $ wget http://www.slitaz.org/en/doc/handbook/
-

- - -

List the available partitions

-To list the partitions on an internal or external hard drive, you can use -cat to display the contents of /proc/partitions -or use the fdisk utility with the -l option -meaning list. You can then mount the individual partition(s) -that you want to use: -

- $ cat /proc/partitions
- or :
- # fdisk -l
-

- - -

Mount a partition, CD or USB drive

-To mount a local partition in the SliTaz filesystem, we recommend you use -the /mnt directory. Example creating the necessary directory and mounting -the hda6 partition of the first local hard drive on /mnt/hda6: -

- # mkdir -p /mnt/hda6
- # mount -t ext3 /dev/hda6 /mnt/hda6
-

-SliTaz functions in RAM, you can mount the same cdrom or remove it -to mount another (/dev/cdrom is a link to the first cdrom drive). -Note that a cdrom is a removable medium and should be -mounted on /media: -

- # mount -t iso9660 /dev/cdrom /media/cdrom
-

-To mount a USB or flash drive you must specify the proper filesystem. -Normally a USB key is formatted in FAT32 which can be read from GNU/Linux -and Windows operating systems. On a GNU/Linux system is it generally -recognized as the sda1 device - we now prepare a link sda1 on -flash to facilitate the task. Note it is also a removable medium -and should be mounted on /media: -

- # mount -t vfat /dev/flash /media/flash
-

- - -

Turn off the system or restart

-To stop or restart SliTaz, you can use the halt or reboot -commands or the <Ctrl+Alt+Delete> key combination which enables a -system reboot. In case of any problems you can use the -f -option signifing forced: -

- # halt
- To restart :
- # reboot
- Or :
- # reboot -f
-

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/desktop.html --- a/en/doc/handbook/desktop.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,237 +0,0 @@ - - - - SliTaz Handbook (en) - Desktop - - - - - - - - - - - - - - - -

- -

SliTaz Desktop

- -

- - -

Introduction

-The default SliTaz desktop is brought to you using different components -of the LXDE project. Openbox, PCmanFM and LXPanel combine to implement a -Desktop providing simplicity and functionality. -

- - -

Openbox

-Openbox is a fast, simple, themeable window manager that doesn't -consume all of your system resources, it is the window manager -by default on SliTaz. A window manager is an application that runs -on top of the X server to control the appearance of windows, open -a X terminal or display applications. It can then place, cut and -resize windows at will. -

-Openbox provides a context menu via a right click on the desktop, -this menu can be changed by editing a configuration file. The key -combinations Alt + TAB allow you to list and navigate -through open windows. Obconf can be used to graphically configure -the window manager and various small tools (specific to SliTaz) allow -you to have a simple, stylish and coherent desktop. By default, -SliTaz uses 4 virtual desktops. -

-The Desktop provided by SliTaz complies with the Freedesktop standards, the -file manager PCmanFM allows for management of desktop icons, drag and drop -(drag and drop) and the mounting of devices with a solitary click. -The panel menu, taskbar, icons, etc are powered by LXpanel. -

- - -

Configuring Openbox

-Most options can be configured graphically using the Obconf utility -located in the "Preferences" menu. The configuration file can also -be modified using your favorite text editor, this is located in your -home directory ~/.config/openbox/rc.xml and is a XML file. -The keyboard shortcuts are defined in the <keyboard> section of the -configuration file. -

- - -

Themes

-Openbox supports themes through a single file using syntax specific to the -window manager. Several default themes are provided, they can be selected -via Obconf and are found in /usr/share/themes. Each system user -can install their own themes in the directory ~/.themes either -manually or via Obconf. If you want to create your own themes for SliTaz, -then the easiest way is to copy and rename an existing theme and then -edit the file themerc. Optional themes can also use images for -buttons, icons, etc. These images can be created or modified via an image -editor such as the Gimp or mtpaint. -

-On the Internet you will find many more themes created by the Openbox community. -More information can be found on the official Openbox -website. -

- - -

Context Menu

-The menu is in the file ~/.config/openbox/menu.xml, the syntax -of the XML file is simple and easy to understand. It also possible to edit -this file with obmenu (not installed by default). An -example for an application in a sub menu: -

<item label="File Manager">
-  <action name="Execute"><command>pcmanfm</command></action>
-</item>
-

-The subumenus are defined at the end of the file using the menu -tag. The tag menu can use a pipe to display the menu entries, -ie. a script that creates entries on the fly. SliTaz offers by default -a pipe menu that allows you to directly open your Favorites folder -with the file manager PCmanFM. The script is found in /usr/lib/openbox -and can be used as an example. -

- - -

Applications started automatically

-When starting in graphical mode, Openbox allows many applications to start -automatically via the ~/.config/Openbox/autostart.sh script. -By default, using this script, SliTaz starts the file manager PCmanFM for the -management of screen and desktop icons, the panel (LXpanel) for the menu, -and dbus and Ivman for the management of devices or media such as USB keys. -To add or remove applications launched at startup of the session, you can edit -the script or use the small SliTaz GUI located in the menu "Preferences" → -"Auto started applications": -

- -

- - -

Wallpaper and icons using PCmanFM

-Openbox doesn't manage the screen natively, you can use -an external tool, this allow more freedom of choice. The default desktop -on SliTaz uses the file manager PCmanFM to display pictures as wallpaper -and have desktop icons. Alternatively, you can use the package -hsetroot to display a picture or xsetroot for -a solid color. PCmanFM is started with the Openbox session as a daemon; -ie, it runs in the background and launches faster. To change the current -background image, you can go through the file manager preferences or via -the menu "Preferences" → "Wallpaper". -

-The icons are displayed via a simple text file (.desktop), -following the Freedesktop standards, you can create your own or customize -using your favorite text editor. To add icons to the desktop, SliTaz provides -a tiny graphical box accessible via the menu "Preferences" → -"Desktop icons" or alternatively, you can use the Openbox context menu -"Desktop files & Icons" → "Add new icon": -

- -

- - -

LXPanel

-LXPanel forms part of the LXDE project and handles the taskbar, menus, -icons etc. Menus are dynamically generated by adding .desktop -files to the /usr/share/applications directory. -

-The system configuration file is located in /etc/lxpanel -and can also be stored locally in ~/.config, though it is -recommended that you configure LXPanel graphically by using the -"Panel Settings" (right click) entry on the taskbar. -

- -

Panel Preferences

-The LXPanel configurator has 3 tabs:- -

General handles the position, size - either dynamic - or fixed, panel background and properties.
Panel Applets lets you add, remove, edit and move - plugins around on the panel.
Advanced allows you to set preferred applications - like the file manager, terminal and logout command.

-The official website for the LXDE project and LXPanel can be found -here. -

- - -

Visual effects

-SliTaz provides several tiny tools to give effects to the Openbox windows -and menus. You can have transparent windows or use shadows to create -depth on the Desktop. The effects are achieved via xcompmgr -(composite manager) and transset-df -(transparency) and both can be activated at the same time on the -session using the Openbox context menu → "Desktop Effects". -

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/development.html --- a/en/doc/handbook/development.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,298 +0,0 @@ - - - - SliTaz Handbook (en) - Development - - - - - - - - - - - - - - - -

- -

Development

- -

About Development
SHell scripts - #!/bin/sh
Dialog - GUI based console.
Geany - IDE or Integrated Development Environment. -
Perl or Microperl - Code Perl scripts.
Python - The Python Language.
Ruby - The Ruby Language.
Toolchain - Libraries, C compiler and tools.

- - -

About Development

-SliTaz provides development tools for web design, editing scripts and source code. -On the website, the Development page will -give you general information about the developers and opportunities for involvement. -

- - -

SHell scripts

-Writing SHell scripts is the easiest way to start coding, they can provide quick results and -the only prerequisites are being able to open a terminal and using a text editor such as Nano, -Leafpad or Geany. SHell scripts can do many things on a GNU/Linux system - initialize the system, -make backups, perform repetitive tasks, display system information, create or modify files and so on. -In a SHell script you can use variables, functions or calls to include a file. Note that you can -name your script as you see fit and the .sh extension is widely used. -

Create a SHell script

-Before starting a new SHell script, you must pay attention to the interpreter used. Most SHell -scripts use /bin/sh, because it's more portable, but there are scripts that rely on -/bin/bash and this must be installed on the system. For a SHell script to function, it -must be made executable by changing permissions on the command line -using the chmod tool. To create a script.sh and make it executable: -

- $ touch script.sh
- $ chmod +x script.sh
-

-Now that you have a new executable file, you can edit it. You can continue to stay in the terminal -and use the Nano editor (Ctrl + x to save & exit) or IDE Geany to edit: -

- $ nano script.sh
- Or :
- $ geany script.sh &
-

-Here's a script that contains a variable NAME and displays the value with the echo -command: -

-#!/bin/sh
-
-NAME="kayam"
-
-echo "$NAME is nice."
-
-

-Once you have created/modified your script.sh, you can execute it to see the result: -

- $ ./script.sh
-

-So much for this brief introduction to SHell scripts. The Web is full of information if you wish to -explore further. -

- - -

Dialog

-Dialog can create GUI-based consoles such as the SliTaz 'installer'. The configuration files are /etc/dialogrc -and/or ~/dialogrc for each user. Here's a simple example of using dialog via a console or terminal: -

- $ dialog --title "Hello $USER" \
-   --msgbox "Message made by dialog." 5 54
-

-You can find plenty of example scripts in the /sample directory inside the source code of dialog, -which can be downloaded from: invisible-island.net/dialog/dialog.html. Download sources and decompress: -

- $ wget ftp://invisible-island.net/dialog/dialog.tar.gz
- $ tar xzf dialog.tar.gz
-

- - -

Geany IDE

-Geany is an IDE or Integrated Development Environment. Geany is simple, quick and light, offering colored -syntax, tabs and auto completion. Geany was used to create this page and most of the website documentation -(with a little bit of Nano as well). -

Launch Geany

-You will find Geany in the menu --> Development --> Geany. -Once launched for the first time, you can adjust your preferences via Edit --> Preferences. -You can also launch Geany via a terminal: -

- $ geany &
-

-Note when compiling the source code, the ./configure script offers the option: --enable-the-force... Which you can use if you ever feel the need to become -Luke Skywalker! -

- - -

Perl or Microperl - Code/use Perl scripts

-On SliTaz you can use the powerful scripting language Perl -via the perl or microperl binary. Microperl is a streamlined version of perl - -compiled from official sources, Perl scripts running Microperl are compatible with the complete version of Perl. -One of Perl's strengths is its portability, it can be used on any system and it's an interpreted language, -which means that the code doesn't need to be compiled and can be used directly. On SliTaz, Perl and Microperl -are not installed by default on the LiveCD: you can either rebuild your ISO or install through the package -manager. Note: Microperl is only 1 MB and provides no modules: -

- # tazpkg install perl
- Or :
- # tazpkg install microperl
-

- -

Hello world!

-The purpose of this script is to display Hello World. You can start -by creating the file and making it executable on the command line and then editing with IDE Geany. -Note the script is called hello.pl, but you can name it as you see -fit, with or without the .pl extension: -

- $ touch hello.pl
- $ chmod +x hello.pl
- $ geany hello.pl &
-

-The first line of a Perl script begins by defining the path -to the Perl interpreter, usually /usr/bin/perl and to display text, just use the -print command. It should be noted that Perl is case sensitive and a line of code should -always end with a semicolon. Example code (you can copy and paste): -

-#!/usr/bin/perl
-#
-
-print "Hello World!\n";
-
-

-To execute and test the script: -

- $ ./hello.pl
-

- -

CGI Scripts and Perl

-CGI scripts are designed to display dynamically generated -web pages. The Perl language associated with the LightTPD -web server allows you to use CGI scripts through your public space or via virtual hosts. -Perl is quite adapted to Web 2.0 and can generate xHTML pages. On SliTaz you must -have Perl or Microperl installed and the LightTPD server -configured before you can use CGI scripts coded in Perl. Note that -by default SHell scripts (.sh) can be placed in /cgi-bin/. -

-Once the server is properly configured, you can put your CGI in your $HOME/Public/cgi-bin using -the .pl or .cgi extension and view them locally or remotely. Example of using a -Perl CGI script: -

-#!/usr/bin/perl
-#
-print "content-type : text/html\n\n";
-
-print "Hello World!\n";
-
-

- - -

Python

-The Python programming language is available as an installable package. Once installed, you can create your -own scripts/programs and use CGI applications with the LightTPD web server, taking care to -configure the server properly. The official SliTaz Mercurial -repositories are provided by a CGI/Python web interface - a solution suited to a product that's -reliable and robust. To install the python package with tazpkg: -

- # tazpkg get-install python
-

- - -

Ruby

-The Ruby programming language is available as an installable package. Ruby is -(to quote the official website):- "A dynamic, open source programming language with a focus on simplicity -and productivity. It has an elegant syntax that is natural to read and easy to write". -Ruby handles exceptions, supports Object-Orientated Programming (OOP), automatic memory management and is -highly portable. To install the ruby package with tazpkg: -

- # tazpkg get-install ruby
-

- - -

Toolchain - Libraries, C compiler and tools

-To compile software from sources or your own code, you need -at least the basic toolchain, comprising of Binutils, -Glibc, C compiler, Kernel headers and the Make utility. -Note that the toolchain is used by the SliTaz developers to compile the entire system from source. -To install the meta package and all dependancies: -

- # tazpkg get-install slitaz-toolchain
-

-The installation of the toolchain can now compile basic applications in console mode without a problem using -the Busybox Ash SHell, but some other packages will not compile without Bash. GNU Bash is available as -a package along with various other development tools such as -Flex, M4, Bison or Pkg-config. If you are looking for pkg-config for example: -

- $ tazpkg search pkg-config
-

-If you would like to compile applications utilizing the Ncurses library, you must install the -ncurses-dev package. -Note the ncurses package also provides a variety of small programs such as tic or -tack: -

- $ tazpkg search ncurses
-

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/enlightenment.html --- a/en/doc/handbook/enlightenment.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,108 +0,0 @@ - - - - SliTaz Handbook (en) - Enlightenment - - - - - - - - - - - - - - - -

- -

Enlightenment

- - -

Enlightenment (e17)

-Enlightenment is a complete desktop environment, fully configurable with the -mouse and offering many themes. The version supplied by the SliTaz project -is known as e17 and is still in development, this version is considered stable -enough to be incorporated into the distribution. Enlightenment was designed to -be deployed on systems with limited resources, as well as more powerful -systems. It allows for wallpapers, menus, animated and interactive gadgets -and knows how to manage virtual desktops. To install e17: -

 # tazpkg get-install enlightenment
-

-Logout your current X session, type F1 at Slim login and choose -e17 to start Enlightenment. -

Menu and desktop icons

-Enlightenment is compliant to the Freedesktop standards. -Applications are sorted by category and icons automatically appear -if a desktop file is supplied. The (.desktop) system files are -contained in the /usr/share/applications directory or hidden home -~/.local/share/applications directory. These files -have a simple syntax and are editable from the panel or with -a simple text editor. The file menus displaying categories -in the Enlightenment menu are found in the slitaz-menus -package: -

 # tazpkg get-install slitaz-menus
-

An icon on the desktop

-To have an icon on the desktop launching applications, you can -create by hand a .desktop file in your local directory -~/Desktop. Desktop files placed in this directory are automatically -recognized by Enlightenment. A single .desktop file can -contain eight lines with respectively:- the name (Name), generic -name, comment, the command to execute (Exec), icon, type -and Freedesktop categories. Example of a .desktop file for Xterm icon: -

[Desktop Entry]
-Name=XTerm
-GenericName=Terminal
-Comment=Run commands in a shell
-Exec=xterm -bg black -fg white -cr orange -sb -bd violet -rightbar
-Icon=/usr/share/icons/Tango/jwm/utilities-terminal.png
-Type=Application
-Categories=Utility;Terminal;
-

-Additional themes can be found on: -exchange.enlightenment.org/ -

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/favicon.ico Binary file en/doc/handbook/favicon.ico has changed diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/gen-livecd.html --- a/en/doc/handbook/gen-livecd.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,296 +0,0 @@ - - - - SliTaz Handbook (en) - Gen a LiveCD to taste - - - - - - - - - - - - - - - -

- -

Generate a LiveCD to taste

-Create your own LiveCD quickly and easily with Tazlito. -

- -

- - -

To begin

-Creating your own LiveCD version of SliTaz with Tazlito -takes very little time and you can choose precisely the software -packages that you want to find on the system. The support -of flavors permits you to generate a customized LiveCD -amended by a list of packages or flavors created by the SliTaz -community. Tazlito is a command line tool that is not too -demanding, you can have your own ISO image in two commands -or burned in one. -

-The generation of the LiveCD requires a minimum of 256 MB -RAM and system compression with LZMA may take some time. It's -possible to create a distribution from the LiveCD or from an -installed system. In LiveCD mode, it's advisable to use persistent -media or a USB drive to store generated files and save space in RAM. -

-Tazlito is used by developers to generate the official LiveCD. -The only prerequisite is to have Tazlito installed. This is installed -by default on SliTaz, but you can generate from another -LiveCD distribution if they have the necessary packages on hand -or they can be downloaded. -

Install Tazlito on another distribution

-Tazlito does not generate dependencies for the LiveCD, but -it depends on Cdrkit to burn the image and Tazpkg to -regenerate SliTaz packages you want installed. To retrieve -and install Tazlito, follow the instructions in the README -file in the sources of Tazlito. -

- - -

A LiveCD in 2 commands

Get a flavor : tazlito get-flavor core
Optional : Amend the list of packages or add - additional files.
Generate the distribution : tazlito gen-distro

-Once finished, you will find the LiveCD ISO image in the -/home/slitaz/distro. -

-For simple instructions click here . -

- - -

Get a taste

-A flavor is a .flavor file containing all the necessary information -for the creation of the CD. The flavor provides the list of -packages (distro-packages.list) and additional files for the -chosen flavor. A list of flavors can be downloaded and -updated with Tazlito: -

- # tazlito list-flavors
- Or :
- # tazlito list-flavors --recharge
-

-A list of flavors will automatically be displayed, giving the -size of the LiveCD and a brief description. For the remainder, -the get-flavor command will download the flavor file, -automatically extract the package list and description in -the current directory and put additional files in the -/home/slitaz/distro/addfiles directory. To store flavors, -we suggest that you use a specific directory such as -/home/slitaz/flavors. You can create this yourself and proceed -inside: -

- # mkdir -p /home/slitaz/flavors
- # cd /home/slitaz/flavors
-

-To download and/or extract the files in a particular flavor: -

- # tazlito get-flavor particular-flavor
-

-The description of the flavor can be displayed with the -show-flavor command. Once the chosen flavor is downloaded -you can start to generate the distribution. - -

- - -

Generate the distribution

-For your first ISO, we advise you to test without modifying -the list, then you can start to delete or add packages -at will. But beware, the base system packages are essential. -The gen-distro command generates an ISO image with all the -packages on the list, it must be run as root and be in the -same directory as the list and the configuration file. -To generate a LiveCD: -

- # tazlito gen-distro
-

-Voilà; your first LiveCD ISO image is generated in /home/slitaz/distro, -but without an account for the user hacker. -

The user hacker

-If you want to have a hacker user account, we must add one -and then recreate the compressed root filesystem: -

- # tazlito addhacker
- # tazlito gen-initiso
-

Clean and regenerate distro

-To continue to go further, you can simply add one or two packages -to the list, clean the distro and regenerate the root -filesystem with a new ISO image: -

- # tazlito clean-distro
- # tazlito gen-distro
-

-Tazlito also offers several possibilities, such as burning the -ISO, copying additional files into the system or directly -on to the cdrom. The Tazlito Manual -provides more information. - -

- - -

Create a flavor

-Tazlito allows you to easily create your own flavor from -the results of generating the distribution (gen-distro). -The file will contain all the flavor's additional files, -a description and a list of packages which can be reused later -and updated according to the versions of packages. To generate -your own flavor responding to one or two questions: -

- # tazlito gen-flavor new-flavor
-

-Once your flavor is fully functioning and well tested, you -can send it to slitaz.org to make it available to all and sundry, -listed via list-flavor and usable via get-flavor. To send -a flavor you have several means, announce through the mailing list, -save the file online and report on the forum or send by mail -to a contributor of the project. -

- - -

Additional files

-The files containing flavors usually have additional files -copied directly into the filesystem or the root of the cdrom. -The path to the files used is specified in the configuration -file tazlito.conf - by default, the files are -located in /home/slitaz/distro/addfiles. The additional files -the core flavor provides are for example, the window manager -JWM and some wallpapers. It is easy enough to modify, add -or delete files in the root filesystem (rootfs) or the root -of the CD (rootcd) and regenerate the distribution. -To clean and regenerate the distribution: -

- # tazlito clean-distro
- # tazlito gen-distro
-

- - -

Packages used

-To create your distro you need SliTaz packages. Tazlito and -Tazpkg allow us to recreate packages from a SliTaz system -in operation or to download packages directly depending on -the flavor chosen. By default, SliTaz packages are located -in the directory /home/slitaz/packages, but you can change -this via the Tazlito configuration file (tazlito.conf). -

-If you want to retrieve packages manually, you can use -FTP software such as gFTP (installed by default on SliTaz) -or the command line and wget to download official packages. -The direct URL to package versions: -ftp://download.tuxfamily.org/slitaz/packages/ -

-You can also use your own packages by putting them in the -packages directory. If you are looking for documentation -about the creation of SliTaz packages, you can refer to the -Cookbook. -

- - -

Configuration file

-By default, Tazlito uses the system configuration file -/etc/tazlito/tazlito.conf or the tazlito.conf - located in the current directory. This means that you can use the default -file or a configuration file specific to the distro you want to -create. This file can change the name of the ISO image, the -name of the maintainer and the paths to the working -directories. To create and configure your own configuration -file, you just need to run Tazlito with the configure -command from the working directory of the distro. -Assuming you have the tree of the distro in /home/slitaz/distro -and you're located within: -

- $ tazlito configure
-

-Once you've answered the questions, you can either -create the ISO image, rebuild the root filesystem and ISO, or -generate a new distro with the list of packages. -

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/graphics.html --- a/en/doc/handbook/graphics.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,120 +0,0 @@ - - - - SliTaz Handbook (en) - Graphics - - - - - - - - - - - - - - - -

- -

Graphics and Image management

- -

Gcolor2 - Color selector.
Gimp - Manipulate and create images.
GQview - Image manager.
jpeg - JPEG command line tools.
mtPaint - Image processing.

- - -

Gcolor2 - Select and manage colors

-Gcolor2 is a tool to select and retain palette colors. It can be useful for the creation of SliTaz themes, -for example. It can be found in the Graphics category or run from the command line: -

 $ gcolor2 &
-

- - -

Gimp - Manipulate and create images

-The GIMP (GNU Image Manipulation) is software that can manipulate images to a very high quality level. -It allows you to do what you would expect from an application that processes images, ie. layers, filters, -support scripts adding functionality, etc. GIMP supports a large number of image formats such as: -PNG, JPEG, XPM, PPM, TIFF, PostScript, PSD, it also offers its own XCF format. To install GIMP: -

 # tazpkg get-install gimp
-

-GIMP is scalable and can be configured with the main interface - configuration files, brushes and personal -scripts are located in the ~/.gimp-2.2 directory. -

- - -

GQview - Image manager

-GQview is very light and quick and allows you to navigate rapidly between images by selecting files -in a directory tree with a single mouse click. It supports slideshows, image rotation, adding -keywords and tags, drag and drop, and can display EXIF data. It also allows you to edit images -in the software of your choice (Mtpaint, GIMP for example). To install GQview: -

 # tazpkg get-install gqview
-

- - -

jpeg - JPEG command line tools

-To allow applications that use JPEG to function, linked libraries must be provided by the package -jpeg-6b, this package also contains some tiny utilities that can be used on the command -line such as cjpeg and djpeg. To modify JPEG images on the command line you -can also use jpegtran, installed by default on SliTaz, jpegtran allows you to -rotate images via the -rotate option. To find out all of the options available for these -tools, just specify the --help option. Example: -

 $ cjpeg --help
-

- - -

mtPaint - Image processing

-mtPaint is an application for the creation and retouching of PNG, TIFF, -XPM and BMP images. It offers many simple, lightweight, fast functions like -capture screen (screenshot) which you can access from the menu --> Graphics --> -Grab screenshot, or via a terminal: -

 $ mtpaint -s
-

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/hacking-livecd.html --- a/en/doc/handbook/hacking-livecd.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,354 +0,0 @@ - - - - - SliTaz Handbook (en) - Hacking LiveCD - - - - - - - - - - - - - - - -

- -

Hacking SliTaz LiveCD

- -

- - -

Introduction

-Hacking SliTaz LiveCD or how to have fun with the LiveCD ISO image. Note that you can also -create a custom flavor with Tazlito. -Creating your own bootable ISO image is easily achievable and the steps are carefully described here. The manipulation of a personal ISO image can add new files or modify existing -ones found on the SliTaz Live CD. The SliTaz ISO image is less than 30 MB and a CD-R or CD-RW provides around 700 MB, -so there's plenty of scope for expansion. For example, you could store your images and even provide a live slideshow -using GQview. The hacking of the ISO image allows you to modify boot loader configuration files -(boot loader), splash images and GRUB itself. You could also add the -Memtest86 utility (tool used to test system RAM). Using the same techniques it's even possible to -modify the filesystem - this does however require some extra manipulation and a bit more time.

- - -

Organization and preparation

-To begin, first we must define where we are going to work by creating a directory and several sub directories -to accomodate all the different files. The hacking of the ISO can be done from within a SliTaz system or any -other GNU/Linux distribution such as Debian, Fedora, PCLinuxOS, etc. If you use SliTaz LiveCD mode -(where you can remove the CD once SliTaz has launched in RAM and burn your new ISO), It's advisable to use -USB media to carry on working, otherwise your work will be lost on shutdown. To begin you need to create a -hacking directory that you can use inside /home/slitaz within the -root of your user space. The use of a /home/slitaz directory enables you to store an original -ISO image and gives you the option to create a src/ directory to download possible source packages. -All the various stages of hacking can be done on the command line via a X terminal (Xterm) or in console mode -on a Linux terminal. It's advisable to run all commands as root to avoid any permission problems. -To become the (root) adminsistrator, create a /home/slitaz/hacked directory and proceed -inside: -

 $ su
- # mkdir -p /home/slitaz/hacked
- (# mkdir -p /home/slitaz/src)
- # cd /home/slitaz/hacked
-

Getting the contents of the ISO

-Now that you are in the working directory, we must create the root of the amended CD-ROM and retrieve the files contained on the original SliTaz ISO - namely, the Linux Kernel (bzImage), the compressed -filesystem (rootfs.gz) and the isolinux bootloader files. To recover these files you have two -options, either take them from a burned CD or from an ISO image stored locally. To create the root of your CD -(rootcd) and copy files from the cdrom device /dev/cdrom mounted on -/media/cdrom: -

 # mount -t iso9660 /dev/cdrom /media/cdrom
- # mkdir rootcd
- # cp -a /media/cdrom/* rootcd
-

-To mount an ISO image using loop in the temporary directory /tmp/loop -(with the ISO image slitaz-cooking.iso), create the root of the CD -(rootcd), copy all the files and dismount the ISO image: -

 # mkdir /tmp/loop
- # mount -o loop slitaz-cooking.iso /tmp/loop
- # mkdir rootcd
- # cp -a /tmp/loop/* rootcd
- # umount /tmp/loop
-

-Voilà, all the necessary files should now be present in the rootcd/ directory. -To be sure, you can list all of the files recursively with the ls command: -

 # ls -R rootcd
-

- - -

Adding the files to the ISO

-The addition of various files and directories to the ISO image simply consists of copying data to -the root of the cdrom (rootcd/) and generating a new image. The data may be classified -in one or two directories created in the root of the CD. Once the ISO image is burned to a CD-R/CD-RW, -you can use SliTaz as before, mounted on /media/cdrom and navigate through your data using -emelFM2, Clex or the command line. Your data will also be legible from all GNU/Linux systems, BSD or even -... Windows. -

Create directories and copy data

-To create and copy files, you can start by using the command line and then continue on graphically as a simple -user. We will create an images/ directory as root and change the permissions so that all -users have write access: -

 # mkdir rootcd/images
- # chmod 777 rootcd/images
-

-Now that a directory exists that anybody can write to, you can start to fill it. Once you've finished -you can then generate a bootable ISO image. -

- - -

Modify the isolinux configuration

-The modification of isolinux allows you to create custom entries with pre-boot parameters, -for example you can add a label launching SliTaz with the lang=en -and kmap=en options. At the design level you can easily change the splash -image displayed at startup. The isolinux application manages the starting of the -boot loader of the LiveCD and is provided by the Syslinux package. The source file of -Syslinux provides various applications whose role it is to start a GNU/Linux system. The binary -isolinux.bin controls the actual boot loading. The boot loader is simple, fast and easily -configured either graphically or using a text editor. The syntax of the configuration file -isolinux.cfg is easy to understand - to add new entries just copy and paste using the -original file. To edit the file graphically using Leafpad: -

 # leafpad rootcd/boot/isolinux/isolinux.cfg &
-

Configuration file isolinux.cfg

-The isolinux.cfg file found on the standard LiveCD of -SliTaz, begins with the value display, this will either display -a text file or a (isolinux.msg) file using 24 ASCII characters and -a splash image. The default value defines the name of the label -started by default after the (timeout) waiting time. Timeout is the -number of seconds to wait before booting the system, you can make it 0 to start booting -immediately or choose a waiting time as long as 80s. Finally the prompt can be -deactivated using the value 0. F1, F2, F3 display help files and F4 displays a text file: -

display isolinux.msg
-default slitaz
-label slitaz
-      kernel /boot/bzImage
-      append initrd=/boot/rootfs.gz rw root=/dev/null vga=788
-implicit 0	
-prompt 1	
-timeout 80
-F1 help.txt
-F2 options.txt
-F3 isolinux.msg
-F4 display.txt
-

-Example of a label slitazen which you can add to the original -to directly configure the language of the system as English and use the UK keyboard:

label slitazen
-      kernel /boot/bzImage
-      append initrd=/boot/rootfs.gz rw root=/dev/null lang=en kmap=en

-Once you've finished modifying the configuration file, don't forget to save your changes and -generate a bootable ISO image with isolinux. -

- - -

Install and use Memtest86

-The application memtest86 (92 kB) is a tool for testing your system memory (RAM). -Memtest86 performs indepth tests, that if failed, point heavily towards a hardware fault. -The tool resides in the boot/ directory and can be launched directly by typing -memtest at the isolinux boot prompt. Navigate to /home/slitaz/src -(if the directory doesn't exist: mkdir -p /home/slitaz/src), download the source -and unpack:

 # cd /home/slitaz/src
- # wget http://www.memtest86.com/memtest86-3.3.tar.gz
- # tar xzf memtest86-3.3.tar.gz
-

-On unpacking the source of the memtest86 package you'll find a -README providing information about the tool. Now you can install -into the root CD of your hacked ISO. Based on the premise that you'll be -working with a /home/slitaz/hacked directory, we will copy the binary -you precompiled into the boot/ directory of the root of the CD: -

 # cp memtest86-3.3/precomp.bin \
-   /home/slitaz/hacked/rootcd/boot/memtest
-

-Now that the binary is installed in the root CD, we can just add an entry for memtest86 -to the isolinux configuration file and generate a bootable ISO image. -Navigate to /home/slitaz/hacked and edit isolinux.cfg using Leafpad: -

 # cd /home/slitaz/hacked
- # leafpad rootcd/boot/isolinux/isolinux.cfg &
-

label memtest
-      kernel /boot/memtest
-

-Official website of Memtest86 -

- - -

Manipulate the Live root system

-Changes to the Live root system allow you for example, to add a new user and password, customize graphics or -execute commands automatically at boot time. The necessary operations for changing the root file system are: -extract the compressed file system rootfs.gz, modify, rebuild the image and generate the ISO. -Based on the assumption that you've prepared a working directory, we begin by creating -a directory to contain the files on the changed system. Since the compressed root file system is named -rootfs.gz, we suggest you use rootfs/ to extract to. Navigate to the hacked/ -directory, create the root directory and copy the compressed file system from rootcd/boot/ -(the root of the cdrom): -

 # cd /home/slitaz/hacked
- # mkdir rootfs
- # cp rootcd/boot/rootfs.gz rootfs
-

-Now that you have the compressed copy of the system, just unpack with cpio. -Technically rootfs.gz is a cpio file compressed with lzma or gzip. It's recognized like an -initramfs image by the Linux Kernel. At the start up of the machine, the Kernel is loaded into -memory and then decompresses the system image and carries out the initialization scripts.

To extract the file system - into rootfs/ and delete the unarchived copy (remember you can copy & paste): -

 # cd rootfs
- # (zcat rootfs.gz 2>/dev/null || lzma d rootfs.gz -so) | cpio -id
- # rm rootfs rootfs.gz
-

-The system is now ready to be hacked, you can list all files at the root of your system by using the -ls command. -

Modify a file

-To keep things simple and to help you understand the principle, we are going to change a script file in -order to execute some commands to be carried out automatically when the CD starts up. The target is -etc/init.d/local.sh - just open with your favorite text editor such as Geany: -

 # geany etc/init.d/local.sh &
-

-We'll add a command displaying a message and letting the system sleep for 4 seconds. Example using local script: -

echo "* Hacked SliTaz version booting..."
-sleep 4
-

Rebuilding the image of the compressed system

-Once the changes are completed, you can rebuild a compressed image of your system by using -find to find the files, cpio for archiving, lzma and -gzip for compression and the pipe | to connect -everything together. This command must be launched from the root system (rootfs/) -and creates a compressed file rootfs.gz in the preceding directory: -

 # find . -print | cpio -o -H newc | lzma e -si -so > ../rootfs.gz
- Or with gzip:
- # find . -print | cpio -o -H newc | gzip -9 > ../rootfs.gz
-

-Finally copy the compressed file system into the boot/ directory at the root of the CD and -generate a bootable ISO image with isolinux. To copy the newly compressed -rootfs into the working directory: -

 # cd ../
- # cp -a rootfs.gz rootcd/boot
-

- - -

Generate a bootable ISO image

-The following commands create an image with the -boot loader isolinux, using the -genisoimage application and a few options. The name of the ISO is -specified at the beginning, after the -o option and the root directory -(rootcd/) at the end, after the -boot-info-table option: -

 # genisoimage -R -o slitaz-hacked.iso -b boot/isolinux/isolinux.bin \
-   -c boot/isolinux/boot.cat -no-emul-boot -boot-load-size 4 \
-   -V "SliTaz-Hacked" -input-charset iso8859-1 -boot-info-table rootcd
-

-If you want to check the contents of the ISO before burning, just mount the image in loop -and list the files. On SliTaz and most GNU/Linux systems, you can burn images in ISO format with the -wodim utility. -

Generate a new ISO via a script

-If you wish to test out a lot of new possibilities and generate a lot of ISO images, you may want to -semi-automate the process via a simple SHell script. This tiny script can be created on the command line -or edited graphically, but don't forget to make it executable. You can create the script with cat; -note that EOF signifies End Of File. To create the script gen_hacked_iso.sh -using two variables to change the name of the ISO image and the path to the root directory of the cdrom: -

 # cat > gen_hacked_iso.sh << "EOF"
-

#!/bin/sh
-# Gen a new hacked ISO image.
-#
-ISO_NAME="slitaz-hacked.iso"
-ROOTCD="rootcd"
-
-genisoimage -R -o $ISO_NAME -b boot/isolinux/isolinux.bin \
-   -c boot/isolinux/boot.cat -no-emul-boot -boot-load-size 4 \
-   -V "SliTaz-Hacked" -input-charset iso8859-1 -boot-info-table $ROOTCD
-
-EOF
-

-To use the script, just make it executable and execute: -

 # chmod +x gen_hacked_iso.sh
- # ./gen_hacked_iso.sh
-

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/images/css/Thumbs.db Binary file en/doc/handbook/images/css/Thumbs.db has changed diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/images/css/content-tl.png Binary file en/doc/handbook/images/css/content-tl.png has changed diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/images/css/content-tr.png Binary file en/doc/handbook/images/css/content-tr.png has changed diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/images/css/footer-bl.png Binary file en/doc/handbook/images/css/footer-bl.png has changed diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/images/css/footer-br.png Binary file en/doc/handbook/images/css/footer-br.png has changed diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/images/css/header.png Binary file en/doc/handbook/images/css/header.png has changed diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/images/screenshots/desktopbox-add-icons.png Binary file en/doc/handbook/images/screenshots/desktopbox-add-icons.png has changed diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/images/screenshots/desktopbox-autostart.png Binary file en/doc/handbook/images/screenshots/desktopbox-autostart.png has changed diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/images/screenshots/netbox.png Binary file en/doc/handbook/images/screenshots/netbox.png has changed diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/images/screenshots/wifibox.png Binary file en/doc/handbook/images/screenshots/wifibox.png has changed diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/index.html --- a/en/doc/handbook/index.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,119 +0,0 @@ - - - - SliTaz Handbook (en) - - - - - - - - - - - - - - - -

- -

SliTaz English Handbook

- -

LiveCD usage - How to boot and set options - at the command prompt.
Desktop - Configure the Desktop and Window Managers.
Commands - List of useful commands.
Installation - HD install instructions.

- -

Applications

Utilities - Calculator, Text editor, Create - CD/DVDs and ISOs.
Office - Word processor, Personal organizer and - PDF reader.
Internet - Web browsers, IRC chat client, mail client, BitTorrent and FTP.
Graphics - Computer graphics and Image - management.
Development - SHell scripts, Perl, Python and Toolchain.
Multimedia - Sound, music and video.
System Tools - File & Disk managers and other tools.

- -

System

Packages - Install more software, keep - system up-to-date.
Network configuration - Ethernet, DHCP, - static IP or PPP dialup connection, Firewall (Iptables).
System administration - Mount devices, - manage users and groups, adjust system time.
X Window System - Xvesa & Xorg servers, Slim Login - and Window managers.
Generate a LiveCD flavor - Generate your - own LiveCD flavor using Tazlito.
LiveUSB media - Create bootable USB media - using TazUSB.
Hacking LiveCD - Manipulate and play with the ISO - image of LiveCD.
Web server - Configure and use the LightTPD web server.
Chroot Environment - Build a chroot to protect the host system.
Secure SHell (SSH) - Secure login using Dropbear SSH client/server.
Security - SliTaz and system security.

- -

Other window managers

Enlightenment - Lightweight Desktop Environment.
JWM - Lightweight window manager.

- -

About this Handbook

-This is the SliTaz GNU/Linux English Handbook, a collection of instructions and manuals -about the distribution. This book is coded in xHTML 1.0, following the W3C -standards and is validated for better accessibility. This book is a community -effort to provide high quality documentation for SliTaz users, the first page -was created on the 26 of February 2008. The SliTaz Handbook is always in -development and follows the distribution changes and improvements. -

-To participate, you can correct typos or start a new page using the book -template.html. Before starting any new work, you -should notify the mailing list or an official contributor to avoid any duplication. -

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/install.html --- a/en/doc/handbook/install.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,230 +0,0 @@ - - - - SliTaz - HD Installation - - - - - - - - - - - - - - - -

- -

HD Installation

- -

- - -

Introduction

-This document gives information and necessary instructions on how to -install SliTaz on a hard disk. This should take about 10 minutes, SliTaz core -LiveCD expands to 80 Mb, so we suggest a minimum of 120 Mb of free space. -This way you will be able to install a few more packages. If you can -use the LiveCD, you should be able to install SliTaz. -

- - -

SliTaz Installer

-SliTaz provides a simple to use Installer which can be launched from the -"System Tools" menu. SliTaz 2.0 Installer messages are in English -and can be used with these complimentary instructions. -

Install type

-The first step lets you choose the type of installation: new install or system -upgrade. In most cases you will want a new and clean installation. On confirming this -the installer will mount the master cdrom device and search for the compressed -filesystem (rootfs.gz). If no filesystem is found, then the -installation will abort. -

-If you get into trouble because the compressed filesystem is not found, please -check that SliTaz is in the master CD/DVD device. If the problem persists you -can use a downloaded ISO image and mount it on /media/cdrom where -the HD Installer expects to find it: -

- # mount -o loop slitaz-1.0.iso /media/cdrom
-

Target partition

-Second step is the partition configuration. If you already have a free partition -you can directly use it, if not you will have to create one graphically using -Gparted or from the command line with fdisk. For example if you want to install -SliTaz on the first partition of the first disk recognized as hda: -

/dev/hda1
-

Formating

-The next step lets you format the target partition into ext3. Ext3 -is a robust, stable and journaled filesystem. If the partition is already -formated you can skip this step, if not just accept. Warning formating a -partition will destroy all current data. -

Hostname

-Hostname configuration lets you set the machine name. The hostname is used -internally to identify the host on the network. This value can be -changed after the system is installed. -

Bootloader - GRUB

-When the installation process is finished you have the option to install the GRUB -bootloader which is capable of booting almost any kind of operating system. If -you want to use an existing GRUB installation, skip this step and add the -correct lines to your GRUB configuration file (menu.lst). Note -that the SliTaz Installer creates a configuration file on the target which can be -used as an example (/mnt/target/boot/grub/menu.lst). -

End of installation

-When the Installer has finally done its job you have the option to exit or -directly reboot your new SliTaz GNU/Linux operating system. First boot is like -the LiveCD, you will be prompted for locale, keyboard, sound card and screen -selection. Future reboots will not prompt you anymore for configuration details, -but all the values can be changed either manually or with the project tools -such as tazlocale or tazx. -

- - -

Installation by hand

-SliTaz can also be installed by hand from the command line. To install SliTaz -by hand you can use a cdrom or an ISO image. The following commands can be -copied/pasted from Firefox to Xterm. -

-The first thing you have to do is prepare a target partition and mount it. -Example using partition /dev/hda1: -

- # mkdir /mnt/target
- # mount /dev/hda1 /mnt/target
-

Mount cdrom or ISO image

-Now you have to mount the cdrom: -

- # mount /dev/cdrom /media/cdrom
-

-Or an ISO image: -

- # mount -o loop slitaz-1.0.iso /media/cdrom
-

Install and extract

-The goal now is to copy needed files from the media into the target partition -and then extract the compressed filesystem (rootfs.gz). Create a -boot directory and install the Linux Kernel: -

- # mkdir /mnt/target/boot
- # cp -a /media/cdrom/boot/vmlinuz-* /mnt/target/boot
-

-Copy the rootfs: -

- # cp /media/cdrom/boot/rootfs.gz /mnt/target
-

-Now the necessary files are present so you can change (cd) -to the target directory and uncompress the filesystem with lzma and -cpio: -

- # cd /mnt/target
- # lzma d rootfs.gz -so | cpio -id 
- # rm rootfs.gz init
-

-That's all, SliTaz is installed. Before rebooting on your new SliTaz GNU/Linux -installation, please check that you have a bootloader (GRUB or Lilo) and add -the necessary lines to boot SliTaz. -

- - -

GRUB bootloader

-GRUB is an universal bootloader capable of booting almost any operating system -such as Linux, BSD or Windows. GRUB uses a single configuration file named -menu.lst, if you used the SliTaz Installer -and installed GRUB you dont need to manually install GRUB, just reboot. -

-Installation of GRUB onto the mbr, using root directory /mnt/target -(the target mounted partition) and the disk named hda: -

- # grub-install --root-directory=/mnt/target /dev/hda
-

-You can now create a GRUB configuration file and add the lines which will boot -SliTaz. Menu.lst can be edited with your favorite text editor such as Nano or -Leafpad: -

- # leafpad /mnt/target/boot/grub/menu.lst
-

/boot/grub/menu.lst - Example

-title  SliTaz GNU/Linux 1.0 (Kernel 2.6.25.5-slitaz)
-       root(hd0,0)
-       kernel /boot/vmlinuz-2.6.25.5-slitaz root=/dev/hda1 vga=normal
-

-Verify again that everything is in place before rebooting: -

- # reboot
-

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/jwm.html --- a/en/doc/handbook/jwm.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,180 +0,0 @@ - - - - SliTaz Handbook (en) - JWM - - - - - - - - - - - - - - - -

- -

JWM

- - -

JWM - Joe's Window Manager

-Joe's window manager, written in C is quick, simple, clean, stable and efficient. -JWM proposes a taskbar, a menu of icons and a pager for the management of virtual -desktops. The taskbar can also act as a dock. In addition it is easily configurable -with a single text file that can change the menu, fonts and their sizes, and different -colors. To install jwm on SliTaz: -

 # tazpkg get-install jwm
-

-Logout your current X session, type F1 at Slim login and choose -jwm to start JWM. To make JWM your default Window -Manager, just type: tazx jwm. -

- -

Use and configure JWM

-The application of Joe's Window Manager is very fast. To view the menu just -click somewhere on the desktop. You can resize a window through the edges or -corners, minimize or pass a virtual desktop to another via a pager. You -also have configurable keyboard shortcuts for faster access to the applications -that you often use. On SliTaz the system configuration file is -/etc/jwm/system.jwmrc. Apart from this file, each user can use -its own configuration file hidden in ~/.jwmrc. This is a text file using XML -syntax, it can edited with a simple text editor - lines beginning with: -<!-- are comments that let you understand what each tag does. -

-To facilitate the customization of the desktop, SliTaz automatically copies -at the launch of the first (graphical) session, a system configuration file to -the root directory of the user. You can directly modify this file and test -without risk. To edit with your favorite text editor: -

- $ geany $HOME/.jwmrc &
-

-To retrieve an original configuration file, you can copy the system configuration -file and rename it .jwmrc in your home directory: -

- $ cp /etc/jwm/system.jwmrc $HOME/.jwmrc
-

-The tag RootMenu corresponds to the menu displayed by clicking on one of the -(three) buttons on the mouse. To add a category, you must use the tag: Menu - - this contains entries for various programs. Any entry in the JWM menu can -fit on one line. Example using the GQview image management application: -

-<Program icon="gqview.png" label="GQview">gqview</Program>
-

-There are still many opportunities to configure RootMenu according to the -mouse buttons; the choice of method to move windows, create groups, etc. -The Manual is available online at the official website of the project. To view -a list of command-line options, just type jwm -h in a terminal. -

- -

Create your own JWM style

-Creating your own graphical style with JWM is relatively quick -and easy, the tags are clear and the attributes possible -are given in the comments. When preparing your work, you can -see your amendments by restarting the window manager from the -menu or via the jwm -restart command. In the configuration -file, style tags start after the  comment. To -begin, here is a short list of the main style tags with a short -description: -

Background manages the wallpaper. This tag supports the - solid, gradient, image or tile - attributes, to respectively:- use a solid color, create a gradient, - display a resized image or tile an image.
BorderStyle controls the windows border.
TrayStyle controls a taskbar. The taskbar may, among other - things be automatically hidden or only fill a part of the - screen with the width attribute.
TrayListStyle controls the style of the list of open windows - on the current desktop.
PagerStyle controls the pager displaying different virtual - desktops (4 by default).
MenuStyle defines the menu style.
The icons are defined by the IconPath tag, you can use your - own personal icons by specifing the full path to the directory - that contains them. Note that you can specify more than - one path, if you want, you can use your own icons and those - contained in the /usr/share/pixmaps and /usr/share/icons - system directories. SliTaz uses the Tango theme icons: - tango.freedesktop.org - for the menu, these are 16x16 and are stored in - /usr/share/icons/Tango. You can add, edit, delete - these... If you want to install new icons in your user - space, we advise you to use ~/Picture/Icons (set as default) - or a hidden directory ~/.Icons.

-The colors can be defined by their name or RGB number, such -as #3A4956. To use colors in their gradient mode, you must -specify the two colors separated by a colon, example -#6C0023:#3E1220. You can change fonts and their sizes by -using the Font tag. There are still some small things that -you can change to customize your desktop, such as the name -of a menu item and its icon. Before restarting JWM with your -new configuration file, you can check its syntax by using -the command: jwm -p. To explore further, the official -handbook describes all the tags, options and valid attributes. -You can view it online at the JWM website. -

- -

JWM website

www.joewing.net/programs/jwm/ - The official website of - Joe's Window Manager, providing news and a comprehensive manual.
#jwm on irc.freenode.net - The JWM IRC discussion channel on - Freenode server.

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/livecd.html --- a/en/doc/handbook/livecd.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,262 +0,0 @@ - - - - SliTaz Handbook (en) - LiveCD usage and options - - - - - - - - - - - - - - - -

- -

LiveCD usage and options

- -

Boot from a cdrom.
Options to pass at boot.
Linux Kernel Parameters.
Option : home=usb - Use USB media as /home - partition.
Options : lang=XX and kmap=XX - Specify language - and keyboard.
Option : config=<device>,<path> - - Execute a script at boot time.
Option : screen=<type> - Specify screen resolution.
Option : sound=* - Disable sound support.
Option : modprobe=modules - Load needed Kernel - modules.
Option : laptop - Load ac and battery modules.
Option : previous - Rollback to previous filesystem.
Sessions - Logins, passwords and X.

- - -

Boot from a cdrom

-To boot SliTaz from a cdrom, just burn the ISO image onto a blank disc, then -reboot your computer with the disc in your cdrom drive. In most cases your -computer is already configured to boot from the cdrom, if this is not the case -you can change the boot order via the BIOS setup utility (generally by -pressing the F11, F12, Esc button or otherwise) a few seconds after starting -the machine. When you are in the BIOS, you can also change the boot sequence and -settings so that the cdrom comes first. Finally, remember to save your changes -before leaving the BIOS configuration interface. The first splash image -is powered by isolinux bootloader, you can then just press ENTER -with or without any options to start system initialization. Note that pressing -F1-F4 will display help and information. SliTaz runs entirely -in memory and will not damage the installed host system. When the boot -process is finished, you can login without any password as user -tux. To become root administrator, you can use the command -su with the password root in a XTerm window or -the Linux console. In LiveCD mode the root password is root. -

- - -

Options and parameters to pass at boot

-The SliTaz LiveCD can pass various boot options via the command prompt powered by syslinux. -There are two types of options: those of SliTaz and those of the Linux Kernel. -The options for SliTaz are used by various startup scripts and the parameters -such as the VGA mode are managed directly by the Kernel (kernel boot parameters). -To pass options at startup, just precede your commands with slitaz -

 slitaz vga=791 no387
-

-Note that the Linux Kernel keeps data passed to boot in the text file /proc/cmdline. -On a GNU/Linux system, you can view this information by running the command: -

 $ cat /proc/cmdline 
-

- - -

Parameters of the Linux Kernel

-On GNU/Linux systems, parameters specific to the Kernel vary greatly depending on -the configuration used in compiling it. The kernel used by SliTaz -is constructed with a minimum of modules and offers very -few modifiable parameters at startup. However, you can disable the -emulation of a math coprocessor via option: no387 and/or activate -irqpoll in the case of problems with interrupts (CD/DVD). The SliTaz -Kernel also provides a video output mode for the VGA Vesa framebuffer - - this is what displays the tux logo and manages the display of the Linux terminal. -Once the system has started you have access to six pseudo terminals via the key combinations -Ctrl+alt+F1, Ctrl+alt+F2, and so on. -

- -

vga=XXX - VGA Kernel modes

Colors | 640x480  800x600  1024x768  1280x1024  1600x1200
--------------------------------------------------------
-256    |  769      771       773       775        796
-32768  |  784      787       790       793        797
-65536  |  785      788       791       794        798
-16,8M  |  786      789       792       795        799
-

- - -

Option : home=usb

-To store your data permanently (bookmarks, downloads, Firefox Add-ons, etc), -you need USB media with a partition formatted in ext3 and it must -specify home=usb for sda1 (most cases) or -home=devname at boot time. Note that you can also specify the -device using the partition UUID or label by using home=*. Example: -

- slitaz home=sda1
-

Prepare USB media

-All USB media can formatted in the native Linux ext3 filesystem. -Ext3 is a journaled, stable filesystem, it allows you to keep permissions -on all files and is much more secure than the default Windows FAT32 filesystem. -To format USB media you have a few options: the command line with -mkfs.ext3, the tazusb utility or graphically with Gparted. -To get a full list of available partitions including the USB drive you can use the command -fdisk -l and then format. Example: -

- # fdisk -l
- # tazusb format /dev/sda1
-

- - -

Options : lang=XX and kmap=XX

-When you use the LiveCD you have two options to directly configure the system -language and keyboard mapping. These options can be set by simply navigating to -your country code and reloading the bootloader configuration with ENTER. -To skip the language and keyboard configuration you can simply type options on the command -line, for English/UK: -

- slitaz lang=en kmap=en
-

- - -

Option : config=<device>,<path>

-The config= option lets you execute a script at SliTaz boot time, -the script can be located on external media or a HD partition. For example, the -script can mount an ISO image on /usr to save memory and boot the -LiveCD on computers with only 32 Mb of RAM. An example with a script named -slitaz.sh located on the first disk and partition: -

- slitaz config=/dev/hda1,slitaz.sh
-

- - -

Option : screen=<type>

-The screen= option lets you specify your screen resolution at boot. -Note that the screen=text option disables the Slim login manager. Example: -

 slitaz screen=1024x768x24
-

- - -

Option : sound=*

-The option sound=no or sound=noconf lets you respectively disable all -of the modules and applications relating to sound to save memory (ram) or skip the automatic setup -of the sound card, but still allow you to manually configure if needed: -

 slitaz sound=no
-

- - -

Option : modprobe=modules

-To load Kernel modules at boot time use the following example: -

- slitaz modprobe=module1,module2
-

- - -

Option : laptop

-The option laptop will automatically load ac and battery Kernel -modules - useful for laptop computers: -

- slitaz laptop
-

- - -

Option : previous

-Used by the Tazusb utility to rollback to a previous filesystem: -

-slitaz previous
-

- - -

Sessions - Login, passwords and X

-When the system has finished its initialization, the screen is cleared and the -login prompt or the session manager Slim is displayed. Now you can choose to login -as tux (without password) or as root administrator (password root). -Once logged into a session, you can use the many commands available in Busybox, -the GNU text editor Nano or the Clex file manager. You can initiate a graphical server -(X) via startx or connect to a remote machine via SSH or X. -The startx command will launch Xvesa and start the window manager. -

-The desktop is powered by Openbox, you can get the menu by right -clicking on the screen with the mouse buttons. Applications are -classified by category and are available in English. Menu, theme and wallpaper -can all easily be changed to your needs/preferences, and -personal settings and data can be stored on various USB media (Flash key, SD card, etc). -

-To launch a X session from the Linux console, for example if you have passed the -screen=text option or if Slim is not configured to run at startup: -

 $ startx
-

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/liveusb.html --- a/en/doc/handbook/liveusb.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,110 +0,0 @@ - - - - SliTaz Handbook (en) - LiveUSB media - - - - - - - - - - - - - - - -

- -

LiveUSB media

- - -

Tazusb - Live USB Tool

-Tazusb is a tool that can create bootable usb media with a few simple commands. -It can also compress and backup the entire current filesystem to the media, -thus preserving all modifications for future use. Type tazusb usage -for a full list of commands or read the -TazUSB manual. -

Generate your own LiveUSB media

-To generate your own LiveUSB media, first you need to login as root with -su and locate your usb storage device using the command: -

# fdisk -l     # normally /dev/sda1
-

-Then format and label your device -(Warning: this will erase all data, make sure you specify the right device): -

# tazusb format /dev/sda1 
-

-And finally generate LiveUSB media device: -

# tazusb gen-liveusb /dev/sda1
-

-And that's all you need to do, you can now boot SliTaz from usb media (providing -your computer bios supports this method). -

Maintaining system settings

When you finish your LiveUSB session, make sure you maintain your installed -packages, system settings, etc, by backing up the entire current filesystem with: -

# tazusb writefs gzip
-

-This effectively compresses and writes everything to 'rootfs.gz' to be -loaded the next time you boot. -

-If anything should go wrong when writing your filesystem, you can simply rollback -to your previous filesystem by typing 'previous' at the 'boot:' prompt. Older backups are -named 'rootfs.gz.unixtimestamp' and can be safely deleted from the /home folder to save disk space. -

Tazusb Manual

-The official Tazusb manual can be found in SliTaz -Web site documentation. -which contains a lot more useful information. The manual is also available through the documentation menu on the LiveCD. -

-The maintainer of Tazusb has also written a nice -article -about the utility. -

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/multimedia.html --- a/en/doc/handbook/multimedia.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,217 +0,0 @@ - - - - SliTaz Handbook (en) - Multimedia - - - - - - - - - - - - - - - -

- -

Multimedia

- -

SliTaz sound and video.
Configure the sound card.
Alsamixer - Mixer.
Alsaplayer - Audio Player.
Asunder - Audio CD Ripper.
MPD - Music Player Daemon.
mpg123 - Command line audio player.
Mplayer - Movie Player.
Xine - Multimedia Player.

- - -

SliTaz sound and video

-SliTaz LiveCD mode provides sound support, but no video player, however you can watch YouTube by installing -the get-flash-plugin package. To watch videos you can use Xine, it supports most formats such -as avi, mov, mpeg, etc. Note Xine can also act as an audio player. At the sound level, you have a mixer -(alsamixer) and audio player (alsaplayer), both installed by default on the standard LiveCD. SliTaz also -provides tools to configure your sound card. -

- - -

Configure the sound card

-In LiveCD mode SliTaz automatically configures the sound card by launching a dialog. In most cases the sound -card is instantly recognized and you just press ENTER to continue to login and have your sound working. -However, sometimes your card is not recognized at startup or simply not supported. Before throwing in the -towel, you can try to manually configure your card by asking for help on the mailing list or on the -hardware support forum. -

Soundconf

-To configure or reconfigure a sound card, SliTaz provides a script (soundconf), this utility -is used at startup and doesn't pose any questions, supports the right modules and automatically configures -/etc/rsS.conf so that the right driver is loaded on each start. Soundconf will also -automatically adjust volume levels, you can change the settings later through the mixer and -alsactl. To start the sound configuration interface, you must have administrator priviledges -and type: -

- # soundconf
-

Alsactl

-Alsactl controls alsa and can store settings or restore sound for example, to retain -preferences for each start. When configuring sound with soundconf, volumes are automatically adjusted. You -can use alsamixer as root to change the values and then launch alsactl -to store the configuration: -

- # alsactl store
-

-To restore the configuration, you can use the alsactl restore command or to restore your -preferences at each system startup you can edit /etc/init.d/local.sh with your favorite text editor or simply -'echo' the changes: -

- # echo 'alsactl restore' > /etc/init.d/local.sh
-

- - -

Alsamixer

-Alsamixer is the official mixer of the Alsa project. It is simple and effective and can be run from the -menu or directly from a terminal. The volumes can be regulated with the up/down arrows or muted using -the m key. To start from a Linux terminal: -

- $ alsamixer
-

- - -

Alsaplayer

-The audio player Alsaplayer is designed to be simple, clean and intuitive. Alsaplayer on SliTaz provides -support for ogg, mp3 (via libmad) and wav files, playlists and viewers to accompany sound and the ability -to adjust pitch and volume. Once launched from the menu, just click the play button or load a playlist to -start. -

- - -

Asunder - Audio CD Ripper

-Asunder retrieves and encodes audio tracks from a CD. The toolkit is simple and easy to use, encoding -songs into wav, ogg or mp3 (via lame package). It can search CDDB, create playlists and -edit file names. You will find Asunder in the Multimedia category on the menu. -

- - -

MPD - Music Player Daemon

-MPD is a great little music player that uses the server/client architecture, this means it can be even -run remotely without a X server operating. To install MPD on SliTaz: tazpkg get-install mpd. -MPD on SliTaz drops root priviledges, so to start the server, just run: -

 $ mpd
-

-And to stop it: -

 $ mpd --kill
-

-Simply drag your music files into the ~/music folder (or create a link) and then run mpd --create-db as root to update the database -and you're ready to use one of the many clients. The mpd --version command lets you have a full list of available formats and outputs. -

- -

MPC - Music Player Client

-MPC is a popular client for MPD, to load all the files into MPC from the MPD database -and start to play them, simply install: tazpkg get-install mpc and run: -

 $ mpc add /
- $ mpc play
-

-The command mpc --help gives you a full list of all the available options that allow you to edit the playlist, enable crossfade, -adjust the volume and shuffle tracks, etc. -

- - -

mpg123

-Mpg123 is a command line audio player and file converter. This means that you can listen to music or -convert files from a terminal. To display help, use the --help option. -To play a mp3 file, just launch mpg123 followed by the name of the audio file: -

- $ mpg123 sound.mp3
-

-Mpg123 can also encode a file into another format, for example you can convert -a wav file into a mp3 file. Example: -

- $ mpg123 -w sound.mp3 sound.wav 
-

- - -

Mplayer

-Mplayer is a popular movie player for Linux suppporting many formats including, DVD, VCD, mpeg, wmv, realvideo, etc. -It can also play various audio codecs such as aac, wma, realaudio, as well as ogg, flac, etc. Mplayer is configurable -via a right click menu and customizable using various skins and GUIs that easily enable you to configure your own video -drivers, output devices and so on. -

- - -

Xine

-Xine is a multimedia project providing various video viewers and audio players. SliTaz provides libraries -and a media player contained in the package xine-ui. Xine uses a Xlib interface, a control -panel, a right click configuration menu and various plugins. It can play ogg, mp3 and flac audio codecs, -and mov, avi or mpg video formats. To install xine and its dependancies: -

- # tazpkg get-install xine-ui
-

Official Xine website -

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/network-config.html --- a/en/doc/handbook/network-config.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,437 +0,0 @@ - - - - SliTaz Handbook - Network configuration - - - - - - - - - - - - - - - -

- -

Network configuration

- -

About the Network.
Netbox - Configure the network.
Wifibox - Configure wireless networks.
/etc/hostname - Hostname.
/etc/network.conf - Network - configuration file.
Dynamic IP - Client DHCP udhcpc.
Static IP - Using a specific address.
PPPoE kernel-mode - Dial-up modem connection - in Kernel mode.
PPPoE with rp-pppoe - Dial-up modem.
Install network card driver - Find and load - Kernel modules.
Firewall - Manage the Firewall (Iptables).

- - -

About the Network

-By default SliTaz starts a DHCP client (udhcpc) on eth0 at boot time. If your -network card has been identified as an eth0 interface and you use -a router, your connection should already be working. DHCP is dynamically -configured, on each boot the client asks for a new IP address from -the DHCP server which is integrated into the router, or on another computer. -If you need a static IP, you can directly edit config files or use the GUI -netbox available from the System menu --> System tools. -In a terminal or a Linux console, you can list all available network -interfaces with the command ifconfig followed by the --a option: -

- $ ifconfig -a
-

To display the Kernel's IP routing table, you can use the route command -without any arguments: -

-$ route
-

-The system wide network configuration file is /etc/network.conf. -It can be graphically configured with netbox or directly edited by -the root administrator. -

- - -

Netbox - Configure the network

-Netbox is a small GTK+ application to configure a network interface using -DCHP or a fixed (static) IP address. The tabs can be used to start/stop the -connections and automatically change the values in the system files. Netbox -provides a system wide tab from which you can directly edit network -configuration files, and tabs to configure PPP/PPPoE username/passwords. -Servers such as SSH, DHCP, PXE, DNS, etc can also be configured and it's -possible to create your own virtual private network (VPN) using the tools -provided. -

- -

- -

-You can start netbox from the System tools menu or via a terminal: -

- $ subox netbox
-

- - -

Wifibox - Graphical configuration of the wireless network

-Wifibox is small interface to configure a network connection (Wifi, -WLAN, or Wireless). The 'Networks' tab displays a list of available -networks, just double click on a network name to connect. If the network -is secure, the key will then be sought. -

- -

- -

-The 'Favorites' tab allows you to set your preferred networks. Once a -network is added, just double click on the network name to connect. The -'Configuration' tab lets you configure a connection manually using the -advanced settings such as the mode or channel. The 'Drivers' tab allows -you to configure a network card; there are 3 options: -

The card is supported directly by the kernel via a module.
The card needs a module and non-free firmware that can be installed - automatically via the auto-detect tool (tazhw).
The card is not supported by Linux and a Windows driver must be - installed via the Windows driver manager (tazndis).

- - -

/etc/hostname - The hostname

-The file /etc/hostname sets the machine name. This is loaded at system -startup with the command 'hostname', without an argument this -command returns the current machine name: -

- $ hostame
-

-To change the hostname, you can use the echo command or a text -editor available on SliTaz (you must be root). Example using echo -and the machine name kayam: -

- # echo "kayam" > /etc/hostname
-

- - -

/etc/network.conf

-/etc/network.conf is the SliTaz system network configuration file. It's syntax -is simple and you can edit its contents with a text editor such as Nano. -/etc/network.conf is used by the script /etc/init.d/network.sh to configure the -network interface at boot time. -

- - -

Dynamic IP - DHCP client udhcpc

-The DHCP client udhcpc supplied with Busybox uses the -/usr/share/udhcpc/default.script to get an IP address dynamically at -boot. It supports various options which you can view with the ---help option: -

 # udhcpc --help
-

-To disable udhcpc on eth0 or modify the interface (eg eth1), you must -edit the /etc/network.conf file and place the value "no" in the variable DHCP=: -

-# Dynamic IP address.
-# Enable/disable DHCP client at boot time.
-DHCP="no"
-

- - -

Static IP - Using a specific address

-You can specify a fixed IP address to configure at boot time by using -the value "yes" in the variable STATIC=: -

-# Static IP address.
-# Enable/disable static IP at boot time.
-STATIC="yes"
-

-For the configuration to work, you must specify an IP address, its subnet -mask, a default gateway (gateway) and DNS server to use. Example: -

-# Set IP address, and netmask for a static IP.
-IP="192.168.0.6"
-NETMASK="255.255.255.0"
-
-# Set route gateway for a static IP.
-GATEWAY="192.168.0.1"
-
-# Set DNS server. for a static IP.
-DNS_SERVER="192.168.0.1"
-

- - -

PPPoE connection kernel-mode

-PPPoE connection in kernel-mode needs 2 files. The first file is -/etc/ppp/options where you must specify your login name: -

-plugin rp-pppoe.so
-name <your provider connection ID>
-noipdefault
-defaultroute
-mtu 1492
-mru 1492
-lock
-

-Now you have to configure /etc/ppp/pap-secrets or /etc/ppp/chap-secrets: -

-# client	       server	       secret			IP addresses
-"your_login"       *               "your_password"
-

-The config file /etc/resolv.conf will be automatically loaded. Finished, you can -now connect to the internet with pppd: -

-pppd eth0
-

-On an installed system you can start pppd on each boot using the local startup -script: /etc/init.d/local.sh -

- - -

Enable Dial-up Modem - PPPoE with rp-pppoe

-To set an ASDL protocol via PPPoE, SliTaz provides the utilities -package rp-pppoe. Using pppoe-setup is a snap and you -can quickly configure the network. If you use DCHP it's even easier, because -the server from your ISP will take care of everything. If you do not have DHCP, -you must first disable its use via DHCP="no" in the -configuration file /etc/network.conf. It should be noted that to -modify configuration files and system logs you must first become root. -To install and change the variable DHCP with Nano (ctrl + X to save & exit): -

- $ su
- # tazpkg get-install rp-pppoe
- # nano /etc/network.conf
-

Configure with pppoe-setup

-To begin to configure your PPPoE connection, you must first open an Xterm or -Linux console and launch pppoe-setup and then begin to answer -the following questions: -

-  # pppoe-setup
-

Enter your username, please note that this is the username with which you - communicate with your ISP.
Internet interface, default is eth0 unless you have more than one, - in which case you will have eth1, eth2, etc. Usually the Enter key is - sufficient.
If you have a permanent ASDL link answer - yes, otherwise answer no (default).
Specify the primary and secondary DNS your ISP uses (you may have to ask).
Enter the password with which you communicate with your ISP (you need - to enter it twice).
Choose the firewall settings depending on your hardware. If you - have a router you can enter 1 or 2. If in doubt enter 1.

Start and Stop the connection

-Still using the command line, simply type pppoe-start to start -the connection. A few seconds later the system tells you that it is connected. -If it gives you a message like TIMED OUT, you may have poorly configured or -the connection is defective. Please check the wiring and repeat the installation -from the beginning. To start the connection: -

 # pppoe-start
-

-To stop the connection, you can type -pppoe-stop. -

- - -

Install network card driver

-In case you need a network card driver and don't know the driver name, you can -use the command lspci to find your card and then modprobe -to load a module. In Live mode you can use the SliTaz boot option -modprobe=modules to automatically load Kernel modules. To get a -list of all available network card drivers, display PCI eth cards and load a -module: -

- # modprobe -l | grep drivers/net
- # lspci | grep [Ee]th
- # modprobe -v module_name
-

-On an installed system you just need to add the module_name to the variable -LOAD_MODULES in /etc/rcS.conf to load your module -on each boot. -

- - -

Manage the Firewall (firewall) using Iptables

-SliTaz provides a very basic firewall, the kernel security rules are launched -at boot time and iptables rules are disabled by default. You can -activate/disable these at startup by using the configuration file -/etc/firewall.conf. -

-The default firewall script begins with its own set options for the -Kernel ie. ICMP redirects, source routing, logs for unresolved addresses and -spoof filters. The script then launches the rules defined in the -iptables_rules() function of the configuration file: -/etc/firewall.conf. -

-The firewall uses Iptables, it consists of two files: -/etc/firewall.conf and /etc/init.d/firewall, you shouldn't need to modify -these. Note Iptables has lots of options. For more infomation see the official -documentation available online: -www.netfilter.org/documentation/. -

Start, stop, restart the firewall

-The script /etc/init.d/firewall lets you start/restart, stop or display the -status of the firewall. The restart option is often used to test new rules -after editing the configuration file. Example: -

- # /etc/init.d/firewall restart
-

Enable/Disable the firewall at boot

-To enable/disable options specific to the Kernel place "yes" -or "no" in the variable KERNEL_SECURITY= : -

-# Enable/disable kernel security at boot time.
-KERNEL_SECURITY="yes"
-

-and to activate/deactivate the iptables rules, it is necessary to modify the -IPTABLES_RULES= variable : -

-# Enable/disable iptables rules.
-IPTABLES_RULES="yes"
-

Add, delete or modify the iptables rules

-At the bottom of the configuration file: /etc/firewall.conf, you will find a -function named: iptables_rules(). This function contains all of -the iptables commands to launch when the firewall starts. To delete a rule, It -is advisable to comment out the corresponding line with a #. It is -not advisable to leave the function completely empty, if you want to disable the -iptables rules just add "no" to the variable IPTABLES_RULES= in the -configuration file. -

-Here's an example of using iptables rules. It only allows connections on the -localhost and the local network, and ports 80, 22, and 21 used by the web server -HTTP, the SSH secure server and FTP respectively. All other incoming and -outgoing connections are refused, so it's fairly restrictive. -

-# Netfilter/iptables rules.
-# This shell function is included in /etc/init.d/firewall.sh
-# to start iptables rules.
-#
-iptables_rules()
-{
-
-# Drop all connections.
-iptables -P INPUT DROP
-iptables -P OUTPUT DROP
-
-# Accept all on localhost (127.0.0.1).
-iptables -A INPUT -i lo -j ACCEPT
-iptables -A OUTPUT -o lo -j ACCEPT
-
-# Accept all on the local network (192.168.0.0/24).
-iptables -A INPUT -s 192.168.0.0/24 -j ACCEPT
-iptables -A OUTPUT -d 192.168.0.0/24 -j ACCEPT
-
-# Accept port 80 for the HTTP server.
-iptables -A INPUT -i $INTERFACE -p tcp --sport 80 -j ACCEPT
-iptables -A OUTPUT -o $INTERFACE -p tcp --dport 80 -j ACCEPT
-
-# Accept port 22 for SSH.
-iptables -A INPUT -i $INTERFACE -p tcp --dport 22 -j ACCEPT
-iptables -A OUTPUT -o $INTERFACE -tcp --sport 22 -j ACCEPT
-
-# Accept port 21 for active FTP connections.
-iptables -A INPUT -i $INTERFACE -p tcp --dport 21 -j ACCEPT
-iptables -A OUTPUT -i $INTERFACE -p tcp --sport 21 -j ACCEPT
-
-}
-

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/network.html --- a/en/doc/handbook/network.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,197 +0,0 @@ - - - - SliTaz Handbook (en) - Internet - - - - - - - - - - - - - - - -

- -

Internet

- -

Mozilla Firefox - Firefox web browser.
Midori - Lightweight web browser.
Retawq - Text mode web browser.
Links - Graphical & Text browser.
LostIRC - IRC chat client.
Ghost In The Mail - Email client.
Sylpheed - Mail Client.
Transmission - Lightweight BitTorrent client.
gFTP - Simple FTP client.
gtk-gnutella - P2P client.
pscan - Port scanner.

- - -

Mozilla Firefox - Web Browser

-SliTaz is proud to provide Mozilla Firefox, one of the world's best web -browsers. It is secure, fast, standards compliant and customizable via a -system of plugins. -To launch Firefox on SliTaz simply select from the menu ---> -Internet --> Mozilla Firefox. The web browser configuration files are stored in the hidden -(dot) directory ~/.mozilla/firefox. -

-Tip: When you combine LiveCD with USB media, you can keep your bookmarks and plugins wherever you go. -

- - -

Midori - Lightweight web browser

-Midori is a lightweight web browser with very fast page rendering -through the rendering engine Webkit. This is a serious alternative to -Firefox for systems with low resources or those seeking a fast and sleek -alternative. It supports most web standards, CSS stylesheets and images. -Midori is configurable via a small interface and is located in the -'Internet' menu once installed. -

- - -

Retawq - Text mode web browser

-All versions of SliTaz provide the text mode web browser Retawq. You -can run 'retawq' from the console, a graphical terminal or in X from -the menu ---> Internet --> Retawq. To -start retawq from a terminal, just type (with or without the url): -

 $ retawq
- $ retawq http://www.slitaz.org/en
-

-The configuration files are in ~/.retawq, you can edit them with a text -editor. Pressing <b> will display the bookmarks (bookmarks.html) -and the <h> key will display the home page. -

- - -

Links - Graphical & Text browser

-Links was the first graphical web browser on the SliTaz LiveCD, it has since been replaced -by Firefox, but Links is always available as a package: -

 # tazpkg get-install links
-

-Links offers a graphical and a text mode. To use the graphical mode, we can use the option -g: -

 $ links -g &
- $ links -g http://www.slitaz.org/en &
- $ links
-

The configuration files are stored in ~/.links, though it's not advisable -to modify them. However, Links provides a configuration interface via -the toolbar at the top, where you can configure the languages, -bookmarks, etc. When you change options, you must save them via the menu -bar --> Configuration --> Save options. -

- - -

LostIRC - IRC chat client

LostIRC is a simple, yet useful IRC client that supports multiple -servers and automatic joining of servers/channels. The configuration -files are located in ~/.lostirc. Simply select from the menu --> -Internet --> LostIRC. The documentation on the -website contains a lot of -useful information. -

-SliTaz channel: irc.toile-libre.org / #slitaz -

- - -

Ghost In The Mail - Email client

-To send messages quickly without having to set up an email account, you -can use Ghost In The Mail (gitmail). The minimal mail client offers a -simple GTK interface and supports attachments. It allows you to send -mail using SMTP with your existing mail account. You will find gitmail -via the menu --> Internet --> Ghost In The Mail. -

- - -

Sylpheed - Mail Client

-If you'd rather have a fully featured email client - you can download Sylpheed. Simple, -reliable and easy to use, it offers powerful search and filters, and junk mail control. -

 # tazpkg get-install sylpheed
-

- - -

Transmission - Lightweight BitTorrent client

Transmission is a GTK+ BitTorrent client that is fast, light and easy -to use. It offers a 'Preferences' option which allows you to limit the -rate of uploads/downloads, specify port, download folders, etc. You will -find Transmission via the menu --> Internet --> Transmission. -Project website: http://transmission.m0k.org/ -

- - -

gFTP - FTP client

-The gFTP application is a fast, ergonomic client for FTP transfers. It -can resume interrupted transfers, manage bookmarks (favorites) and FTP -or HTTP proxies. In addition -gFTP supports the use of drag and drop, can make -several transfers at the same time, compares windows, remembers -passwords and can even define external applications for viewing or editing -files. On SliTaz, you will find gFTP via the menu --> Internet ---> -gFTP. -

- - -

gtk-gnutella - P2P client

-gtk-gnutella is a P2P file sharing application that uses the Gnutella network. -Written in C, it requires a lot less resources than other clients. -It supports the use of searches and filters, features for downloading large files -and bandwidth control. To install gtk-gnutella: -

 # tazpkg get-install gtk-gnutella
-

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/office.html --- a/en/doc/handbook/office.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,133 +0,0 @@ - - - - SliTaz Handbook (en) - Office - - - - - - - - - - - - - - - -

- -

Office

- -

Abiword - Word Processor.
Osmo - Personal Organizer.
SQLite - Tiny SQL Database engine.
ePDFView - Lightweight PDF viewer.
Gnumeric - Spreadsheet.
Homebank - Finance management.
Notecase - Notes manager.

- - -

Abiword - Word Processor

-Abiword is a word processor application rich in features. It contains fast, simple, intuitive lightweight tools -and proposes the proper format (.abw), supporting Open Office and Microsoft Word documents, it can also export to PDF or -HTML. To install Abiword on SliTaz just run: -

 # tazpkg get-install abiword
-

- - -

Osmo - Personal Organizer

-Osmo is a small personal organizer providing a timetable and a list of tasks and contacts with the -possibility of opening them directly in a web browser via a URL or a mail client using an email address. -Osmo also offers a calendar, a date calculator and the ability to take notes classified by day. If -you use USB media associated with the LiveCD, it will even retain your data for you. On an installed -system, you can syncronize data with USB media by using Grsync. Osmo keeps its data in the -hidden folder ~/.osmo. -

- - -

SQLite - Tiny SQL Database engine

-SQLite is a small relational SQL database engine whose entire database is stored in a single file. -It's fast, powerful, speeds applications and implements most of the SQL92 standard. SQLite is ideal -for managing small websites, while requiring minimal deployment. The official website for the project is: -http://www.sqlite.org/ -

- - -

ePDFView - Lightweight PDF viewer

-To view PDF documents, SliTaz uses the epdfview package. This provides a fast, simple, easy to use -PDF viewer. ePDFview uses GTK+ and the rendering library poppler, this enables you to view, move from page to -page and search or navigate the index. -

- - -

Gnumeric - Spreadsheet

-Gnumeric is free spreadsheet program and has the ability to import/export several file formats such as CSV, -Microsoft Exel, Latex, HTML, etc. As well as providing its own format: .gnumeric, it is also one of the most -statistically accurate spreadsheets around. To install gnumeric on SliTaz: -

 # tazpkg get-install gnumeric
-

- - -

Homebank - Finance management

-Homebank is a handy program to manage and compare bank accounts. Lightweight, -fast and comprehensive, homebank is a good addition to Abiword and Gnumeric -for an office suite that's light and easy to use. -Website: homebank.free.fr. -To install homebank, you can use the graphical package manager or the command: -

 # tazpkg get-install homebank
-

- - -

Notecase - Notes manager

-Notecase is software designed to organize and manage notes. It allows -you to link pages, import or export notes and format text (bold, italics, -etc). Notecase is installed by default in the heart of the system and is -located in the Menu → Office → Notecase notes manager. -

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/packages.html --- a/en/doc/handbook/packages.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,181 +0,0 @@ - - - - SliTaz Handbook (en) - Packages - - - - - - - - - - - - - - - -

- -

Packages

- -

Tazpkg - Package manager.
List of packages - Display or generate a list - of packages.
Install packages - Get and install new - packages.
Upgrade - Keep your system secure.
Tazwok & the wok - Package format and build - tools.

- - -

Tazpkg - Package manager

-SliTaz provides a tiny package manager which can easily install more software -on the system. Tazpkg is a lightweight package manager for .tazpkg -files, completely written in SHell script. It works well with Busybox ash shell and -bash. Tazpkg lets you list, install, remove, download, extract, pack, search, -or get information about available or installed packages. You can also repack -an installed package and automatically upgrade all installed packages. On SliTaz -you can type tazpkg usage in a terminal to get a list of all the -commands with a short description in English. -You can also read the manual. -

- - -

List of packages

-Tazpkg lets you list all installed packages, installed -packages by category or it can display the list of available packages on the mirror. -To display a single list of all installed packages on the system, just type: -

- $ tazpkg list
-

-To display all categories or packages sorted by category, you must specifiy -cat or category. - Examples: -

- $ tazpkg list cat
- $ tazpkg list base-system
-

-Tazpkg can also generate a nice xHTML list (default: installed-packages.html) in the local directory of all installed packages on the system: -

-$ tazpkg xhtml-list
-

-To get a single list of all available packages on the mirror you can use -the command list-mirror. You can then examine the list in your favorite editor -or use the Web site interface. -

- - -

Install packages

-To install some new applications such as The Gimp, AbiWord, ePDFView, Perl or -Python, you first need to recharge the list of available packages on the -mirror and then install. If the package dependencies are not installed -Tazpkg will install them for you. For example, the installation of Gparted a -GTK+ partition editor using GNU parted: -

- # tazpkg recharge
- # tazpkg get-install gparted
-

- - -

Upgrade installed packages

-To keep your system up-to-date and secure after recharging the packages list, -you can automatically install all new versions and security updates from the -mirror with the command: -

- # tazpkg upgrade
-

- - -

Tazpkg Manual

-The Tazpkg Manual contains a lot more useful information. -

- - -

Tazwok & the wok

-All SliTaz packages are built with a tool named Tazwok and a receipt found -in the wok. The receipt provides all the necessary information to build a suitable -package for Tazpkg including variables to give us the package name, source tarball format, -download URL, etc. Given a receipt, the compile_rules function has all of -the necessary commands to configure, make, and install the package in a specific directory. -After compilation, Tazwok will execute the function genpkg_rules -to pick up only the needed/wanted files and generate a pkg.tazpkg (cpio archive). -On SliTaz you will find all installed package receipts in the directory -/var/lib/tazpkg/installed, feel free to examine them or even use one as an -example. -

-Tazwok will search by default for a wok in /home/slitaz/wok and -put generated packages in /home/slitaz/packages. These paths are -set by a Tazwok configuration file which can be located in -/etc/tazwok.conf or in the current directory, which is useful if you -want to work with multiple woks. Now, if the slitaz-toolchain is -installed, you can start to create and build a package which doesn't need many -dependencies. Small example: -

- # tazwok new-tree pkgname --interactive
-

-When a new package tree and receipt has been created in the wok, you can edit the -receipt with your favorite editor (Geany provides nicely colored code), modify -the rules, functions, add dependencies to the DEPENDS variable -if needed and try a first cook: -

- # tazwok cook pkgname
-

-Note that you can now browse the generated files, modify the cooking receipt again or -just rebuild the package with tazwok genpkg. When you are happy with -your work you can install the package with tazpkg install and -test the application or library. -

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/secure-server.html --- a/en/doc/handbook/secure-server.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,134 +0,0 @@ - - - - SliTaz Handbook (en) - Secure SHell (SSH) - - - - - - - - - - - - - - - -

- -

Secure SHell (SSH)

- -

About Dropbear.
Connecting to a remote host - (dbclient).
Transfer files - (scp).
Generate keys rsa/dss - (dropbearkey).
Start, stop, restart SSH server.

- - -

About Dropbear

-Control and administer remotely with the Dropbear SSH secure server. Dropbear is a small SSH client/server -supporting SSH 2. It's compatible with OpenSSH and uses ~/.ssh/authorized_keys for the management of public keys. -Dropbear also provides its own version of scp, allowing you to copy files -between machines in a secure manner. -

-Project website: -matt.ucc.asn.au/dropbear/dropbear.html -

- - -

Connecting to a remote host with dbclient

-The configuration files for the SSH client are located in the ~/.ssh directory of each user, this contains -the authorized_keys and known_hosts files. The directory ~/.ssh and known_hosts file are automatically created -the first time you run the Dropbear client (dbclient). -

-To connect to a remote host employing the user and machine name: -

 $ dbclient user@machine.org
-

-You can also connect using the IP address of the machine: -

 $ dbclient user@192.168.0.2
-

- - -

Transfer of remote files with scp

-To copy a file from one computer to another, scp can be utilized in the following ways. To copy a file -named page.html to a remote directory of the user (don't forget the : after the machine name or -IP address): -

 $ scp page.html user@machine.org:path/remote/directory
-

-Copy a file from a remote machine to your local machine: -

 $ scp user@machine.org:path/remote/directory/page.html /path/your/directory
-

- - -

Generate rsa/dss keys with dropbearkey

-Dropbear provides dropbearkey to generate the protected rsa and -dss keys. Note that when you start the server for the first time, secure keys will be -automatically generated if they don't already exist. You can use dropbearkey with -the following arguments: -

 # dropbearkey -t rsa -f /etc/dropbear/dropbear_rsa_host_key
- # dropbearkey -t dss -f /etc/dropbear/dropbear_dss_host_key
-

- - -

Start, stop, restart the SSH server

-By default SliTaz will not start the SSH server at boot. To be launched automatically, dropbear -must be added to the variable RUN_DAEMONS in the /etc/rcS.conf file. To start, stop or restart -the SSH server, use the following commands: /etc/init.d/dropbear [start|stop|restart]. -Example to start the server: -

 # /etc/init.d/dropbear start
-

-Note that the server supports the passing of various options when launched. To change the default values, -simply modify the daemons configuration file /etc/daemons.conf. -

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/security.html --- a/en/doc/handbook/security.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,161 +0,0 @@ - - - - SliTaz Handbook (en) - Security - - - - - - - - - - - - - - - -

- -

SliTaz and System Security

- -

Security Policy.
Root - The system administrator.
Passwords.
Busybox - Configuration file /etc/busybox.conf.
LightTPD web server - Disable the LightTPD web server.
SSH server - Default options.
Pscan - Scan for open ports.
Firewall (Iptables) - - The network firewall.

- - -

Security Policy

-SliTaz has given a lot of consideration to system security. Applications are tested for many months before being -included in the distribution. At boot time, a minimum of services are launched by the rc scripts. For a complete -lists of daemons enabled, you can look at the RUN_DAEMONS variable in the /etc/rcS.conf configuration -file: -

 $ cat /etc/rcS.conf | grep RUN_DAEMONS
-

-To view the actual processes, their PID and memory usage, you can use the 'ps' command or the 'htop' -utility: -

 $ ps
- $ htop
-

- - -

Root - The system administrator

-In a GNU/Linux system, the root user is the system administrator. root has all the rights -to the system files and that of the users. It is advisable never to log in as root by using the command -su followed by the password to obtain absolute rights over the system. Never log in as root and surf the -internet for example. This allows you to create a double barrier in the case of an attack or intrusion after a -download and makes it harder for a cracker to take control of your machine - first he must crack your -password and then crack the root password of the system administrator. -

-A GNU/Linux system has secured at least two users, one to work and another to administer, configure -or update the system (root). It's also advisable to entrust the administration of the -system to a person. -

- - -

Passwords

-By default the SliTaz user tux doesn't have a password and the system administrator root -comes with the password (root). You can easily change these by using the passwd command: -

 $ passwd
- # passwd
-

- - -

Busybox

-The file busybox.conf configures the applets and their respective rights. On the SliTaz LiveCD the commands: -su, passwd, loadkmap, mount, reboot and halt can be initiated by all users - the owner and group of these -commands is root (* = ssx root.root). The busybox.conf file is readable by root, -using the rights 600. Note that the passwd command will not allow users to change their own password -if it is not ssx. -

- - -

LightTPD web server

-On SliTaz the LightTPD web server is enabled by default at system startup, if you don't intend to use SliTaz in a server -environment, you can safely disable it by removing it from the RUN_DAEMONS variable in the -/etc/rcS.conf configuration file or to stop it manually: -

 # /etc/init.d/lighttpd stop
-

- - -

SSH Server

-This small section is a compliment to the -Secure SHell (SSH) page. -On SliTaz the Dropbear SSH server is not run by default, we must add it to the variable -RUN_DAEMONS in the configuration file /etc/rcS.conf for it to be -enabled at system boot. Or to start the server manually: -

 # /etc/init.d/dropbear start
-

-By default, Dropbear is launched with the following options: -

 -w   Disallow root logins.
- -g   Disallow logins for root password.
-

-You can add new options by editing the daemons configuration file: /etc/daemons.conf. -For all options, you can type: dropbear -h. -

- - -

Pscan - Ports scanner

-Pscan is a small utility of the Busybox project that scans the ports of your machine. You can use -pscan to scan the localhost or a remote host using the name or IP address of the machine. -Pscan will test all the ports from 1 - 1024 by default and list those that are open, their protocol -and associated service (ssh, www, etc): -

 $ pscan localhost
-

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/simple-gen-livecd.html --- a/en/doc/handbook/simple-gen-livecd.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,121 +0,0 @@ - - - - SliTaz Handbook (en) - Gen LiveCD flavor - - - - - - - - - - - - - - - -

- -

Generate a LiveCD flavor (Simple Guide)

- -

Tazlito - SliTaz Live Tool.
Get a flavor - Download a flavor file.
Gen your own distro - Generate a Live distro in - one single command.

- - -

Tazlito - SliTaz Live Tool

-Tazlito is a tool to help generate and configure SliTaz LiveCD ISO images. -You can create a custom distro in two commands from a list of packages and a -flavor file, extract an existing ISO image to hack it, create a new initramfs -and/or a new ISO. Most commands must be run by root, except the stats and the -configuration file manipulation. Like other SliTaz tiny utils, you can simply -type tazlito usage in a terminal to get a list of all -commands with a short description in English. -

- - -

Get a flavor

-SliTaz LiveCD can easily be rebuilt using Tazlito flavor support. A special -LiveCD flavor can be built from the LiveCD/RAM itself or from an installed -system. If you want to rebuild SliTaz from the LiveCD you need at least 256 Mb -of RAM and we recommend that you store the file on persistent media (USB key, HD, -etc). To start you need to get a flavor file from a SliTaz mirror; open a Xterm, -become root administrator and get the default core system: -

- # tazlito get-flavor core
-

- - -

Generate your own distro

-The command get-flavor will download the core flavor, giving you a description -and a list of packages in the current directory with some additional files in -/home/slitaz/distro/addfiles (JWM menu, wallpapers, hacker files). From now on -you can add or remove packages in the list (distro-packages.list), -modify configuration files (tazlito.conf) and optionally modify -additional files. Then simply generate a LiveCD ISO image: -

- # tazlito gen-distro
-

-The LiveCD ISO image, root filesystem (rootfs) and the content of the CD -(rootcd) are in /home/slitaz/distro. All repacked or downloaded packages are -stored by default in /home/slitaz/packages. If you want to chroot into the -rootfs to preconfigure the system, add more files in the rootcd directory or -add users, you just have to rebuild the initramfs and ISO image to generate -your new LiveCD: -

- # tazlito gen-initiso
-

- -

Burn ISO and gen a flavor file

-Tazlito can also burn the LiveCD and/or create a flavor file to keep your -modifications: -

- # tazlito burn-iso
- # tazlito gen-flavor
-

- - - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/system-admin.html --- a/en/doc/handbook/system-admin.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,301 +0,0 @@ - - - - SliTaz Handbook (en) - System administration - - - - - - - - - - - - - - - -

- -

System administration

- -

- - -

Devices and disk access

-With Linux your disks and USB media are seen as devices. To access them you must -first mount a device on a mount point (directory). On SliTaz you can graphically -mount devices by using mountbox or the command line. To mount the -first disk of a local hard disk on /mnt/disk: -

- # mkdir -p /mnt/disk
- # mount /dev/hda1 /mnt/disk
-

-To mount a cdrom or an USB media you should use mount points located in -/media. Note that for a cdrom, you just have to specify -the device path. For a flash key, the mount point already exists: -

- # mount /dev/cdrom
- # mount /dev/sda1 /media/flash
-

ntfs filesystem

-If you need read/write access to Windows ntfs filesystems you must install a -few additional packages from the mirror. The ntfs-3g driver -provides stable access to ntfs partitions and ntfsprogs provides -manipulation tools dependent on fuse. Note that you can format, move or resize -ntfs partitions graphically with Gparted. -

- - -

Users, groups and passwords

-To manage users and groups on your SliTaz system you must use the command line, -but file permissions can be changed graphically using the PCmanFM file manager. To -add or remove users and groups you must be root. Root can also change all -user passwords and a single user can only change his/her own password. To add -or remove a user named linux: -

- # adduser linux
- # deluser linux
-

-To add or remove a group you must use addgroup or -delgroup. To change the current user password or change the -password of a specific user, you must use the passwd command: -

- $ passwd
- # passwd username
-

Audio group

-If you want a new user to be able to listen to music he must be in the -audio group. To add an existing user to the audio group: -

- # adduser -G audio user_name
-

- - -

Language and keyboard layout

-SliTaz saves the configuration of the default locale in /etc/locale.conf -which is read by /etc/profile on each login and the keyboard -setting is stored in /etc/kmap.conf. These two files can be -edited with your favorite editor or configured respectively with -tazlocale and tazkeymap. You can modify the settings -you chose on the first boot by typing as root administrator: -

- # tazlocale
- Or:
- # tazkeymap
-

-To check all available locales or your current configuration, you can use the -command locale as a single user or root (C for English): -

- $ locale -a
- $ locale
-

- - -

Bash Shell

-On SliTaz you have the ash and sh shell with a link to Ash, this shell is -provided by Busybox. If you wish to use the Bash (Bourne Again SHell), first -as root install bash, copy the .profile found in your -home directory and rename it .bashrc, then edit the -/etc/passwd file with your favorite text editor and change your -shell to :/bin/bash -

- # tazpkg get-install bash
- # cp /home/hacker/.profile home/hacker/.bashrc
- Note root user: cp /home/hacker/.profile ~/.bashrc
- # nano /etc/passwd   ~ :/bin/bash
-

-The next time you login bash will be your default shell, you can confirm this -by typing env on the command line. -

- - -

Editors

-Busybox supplies a clone of vi for normal text editing, but it does have its limitations. -You can install the full vim editor with the command: -

 # tazpkg get-install vim
-

-Or alternatively if you prefer emacs, SliTaz offers a tiny version: -

 # tazpkg get-install emacs
-

- - -

Sudo

-The sudo command can be applied on SliTaz: -

 # tazpkg get-install sudo
-

-Note that the configuration file /etc/sudoers, should always be edited by the visudo command -which locks the file and checks for errors. -

- - -

System Time

-To know the current system time, you can simply type date. On -SliTaz, the timezone configuration file is saved in /etc/TZ, you -can edit with your favorite text editor or simply echo the changes. -To view the available timezones, you can look in the -/usr/share/zoneinfo directory. -Here's an example using the timezone Europe/London: -

- # echo "Europe/London" > /etc/TZ
-

Rdate

-To syncronize the system clock with a network time server, you can (as -root) use the rdate -s command: -

- # rdate -s tick.greyware.com
-

-To display the time on the remote server, use the rdate -p command. -

 $ rdate -p tick.greyware.com
-

Hwclock

-Hwclock allows you to syncronize the time of your hardware clock to the system -clock or vice versa. -

-Syncronize the system clock to the hardware clock ( --utc = universal time, --l = local time): -

- # hwclock -w --utc
-

-Syncronize the hardware clock to the system clock: -

- # hwclock -s --utc
-

- - -

Execute scheduled commands

-The daemon 'crond' allows you to run commands automatically at a scheduled specific date or time. This is very -useful for routine tasks such as system administration. The directory cron uses is -/var/spool/cron/crontabs. -

-Each user of the system can have his/her own tasks, they are defined in the file: /var/spool/cron/crontabs/user. -The crontab utility allows you (amongst other things), to list the tasks specific to the user. The syntax of the -files is as follows: -

mm hh dd MMM DDD command > log
-

-We will create a file with root priviledges and test the daemon 'crond' with a task performed every minute - -writing the date to a file /tmp/crond.test. It should be noted that the utility has an option -crontab for editing cron file using 'vi', this is not provided by SliTaz. In its place you can use -GNU nano (<Ctrl+X> to save & exit): -

 # nano /var/spool/cron/crontabs/root
-

* * * * * date >> /tmp/crond.test
-

-Launch crond with the option -b (background), -configured via /etc/daemons.conf and using the startup script: -

 # /etc/init.d/crond start
-

-You can wait a few minutes and view the contents of the file: /tmp/crond.test... OK: -

 # cat /tmp/crond.test
-

-To stop or restart the daemon crond: -

 # /etc/init.d/crond stop
- Or :
- # /etc/init.d/crond restart
-

Invoke the daemon crond on every boot

-To launch the daemon 'crond' each time you boot the system, just add it to the variable START_DAEMONS -in the configuration file /etc/rcS.conf, either before or after the web server or SSH server. -

- - -

Add commands to be executed at boot

-During the boot process, various scripts are executed to configure services, such as the start of the -web server, networking, etc. On SliTaz there is a script /etc/init.d/local.sh which allows -you to add commands to be launched at system startup. You can also create new scripts in /etc/init.d, -their links in /etc/rc.scripts for shell scripts and use /etc/rc.d for links to the startup script daemon in -/etc/rcS.conf: -

 # nano /etc/init.d/local.sh
-

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/system-tools.html --- a/en/doc/handbook/system-tools.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,139 +0,0 @@ - - - - SliTaz Handbook (en) - System Tools - - - - - - - - - - - - - - - -

- -

System Tools

- -

Clex - Command line File Manager.
PCmanFM - File Manager.
Htop - View system processes.
Mountbox - Mount devices.
Gparted - Partition a hard drive.
Netbox - Configure network.

- - -

Clex - Command line File Manager

-To navigate through your folders and directories you can use cd -on the command line or launch the 'Clex File Manager'. Using ncurses, -clex is fast and easy to use and can be configured through the files -~/.clexrc and ~/.clexbm (bookmarks) or via the panel (ctrl -g). -To start clex from a terminal or console: -

- $ clex
-

- - -

PCmanFM - File Manager

-PCmanFM is a file manager providing many useful functions for daily tasks -such as managing devices, opening terminals in the current directory, -tabbed browsing, drag and drop, creating directories or managing file -permissions. It contains bookmarks to allow you to browse faster, search -functions and much more. PCmanFM can be launched with some command line -options - you can set the wallpaper to display or open folders in new -tabs, etc. For a full list of options: $ pcmanfm --help-all. -

-PCmanFM supports hotkeys (firefox) and the context menu -(right click on file/directory) makes it easy to unpack -.taz .gz archives, compress and create archives. -

- - -

Htop - View system processes

-Htop is a system process viewer that displays cpu load, memory state (RAM) -and swap used. It can also display the number of tasks, uptime and PIDs -of active processes. Htop can be used with the keyboard in console mode, -the mouse with a X terminal (xterm) and provides configuration options (F2). -Htop can also kill processes - you can select items with the up/down -arrows or a mouse click. Note htop also functions via SSH and can be used -to monitor a remote server: -

- # tazpkg get-install htop
-

- - -

Mountbox - Mount devices

-Mountbox is a small GTK+ application to quickly mount media such as a -USB drive, hard drive or cdrom. Mountbox can be launched from a terminal -or via the Tools menu (System Tools). Simply specify the peripheral -(Device) and the mount point, ie. the directory where you want to access -the media in question. Typically a CD is mounted on /media/cdrom, a USB -key on /media/flash and disk drives on the local machine on /mnt. Note -the Handbook also contains more -information. -

- - -

Gparted - Partition a hard drive

-Gparted is a graphical application making it possible to manage the -partitions of a local hard drive or USB media. It allows you to reformat, -resize or check a partition on a hard drive and is the tool of choice if -you need to prepare a partition to install SliTaz. Gparted supports proper -GNU/Linux filesystems (ext2 and ext3) via mkfs, and Parted automatically -handles dependancies. -

- -

Support FAT and NTFS filesystems

-To have the support of FAT16 or Windows FAT32 filesystems, you must -install the package dosfstools. To enable read/write support -for NTFS partitions: fuse, ntfs-3g and -ntfsprogs. -

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/template.html --- a/en/doc/handbook/template.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,57 +0,0 @@ - - - - SliTaz Handbook (en) - Template - - - - - - - - - - - - - - - -

- -

Template

- -

-CONTENT -

- - - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/utilities.html --- a/en/doc/handbook/utilities.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,190 +0,0 @@ - - - - SliTaz Handbook (en) - Utilities - - - - - - - - - - - - - - - -

- -

Utilities

- -

Bc - Calculator.
Cdrkit - Burn and manipulate CD/DVD-R or RW.
Nano - GNU nano, default text editor.
LeafPad - Lightweight GTK+ editor.
ISO Master - Edit ISO images.
Xpad - Mini note-taking application.

- - -

Calculator

-Mathematical operations can be done with the text mode calculator bc. Open a terminal and directly type -bc. To exit, simply type quit: -

 $ bc
- 23+45 <ENTER>
- 68
-
- quit
-

- - -

Cdrkit - Burn and manipulate CD/DVD-R or RW

-To burn and handle CD/DVD-R or RW, SliTaz provides the Cdrkit utility -and a graphical interface burnbox which you will find in the menu. -The tools in wodim make it possible to burn CD/DVD and erase -CD/DVD-RW. When used with genisoimage, it can also create images in the -ISO 9660 format. Burning on the command line requires us to know the device/writer (dev) -name and wodim provides several possibilities to know which drive to use and specify it when burning -to optical media. If you run wodim with the -devices option, it will automatically -search for a good device and display it, the -checkdrive option allows you to check the -recognized device and -scanbus will display in relation to the system bus. -Examples (as root): -

 # wodim -devices
- Or:
- # wodim -checkdrive
- For the bus: 
- # wodim -scanbus
-

Create an ISO 9660 image

-To burn data on to a CD/DVD, you must first have an ISO image. To begin we must create a directory to -contain all the files to be burned. You can copy your files on the command line with cp, -the file manager Clex or graphically with emelFM2. To create a directory named iso/ -in the root of user space and copy all the files contained in Documents/: -

 $ mkdir ~/iso
- $ cp -a Documents/* ~/iso
-

-Create an ISO image named image.iso, using the genisoimage tool and -specify the root directory containing the files to be included in the ISO: -

 $ genisoimage -o image.iso ~/iso
-

-Note that there are many options that you can use to create ISOs, one of the most widely used is the -extension -R, signifying Rock ridge, this allows the use of names of up to 255 characters -(with a few exceptions), it also supports symlinks and file permissions. To see all the available options, -simply type -help. Example of creating an ISO image using the -R option: -

 $ genisoimage -o image.iso -R ~/iso
-

Burn an ISO image

-To burn an ISO image in the 9660 format either created by yourself or downloaded from the web, -you must use wodim specifying the proper device (dev) to burn -the CD/DVD. Example using the verbose mode (-v), with the device hdc -and data contained in an ISO image named image.iso: -

 # wodim -v dev=/dev/hdc image.iso
-

-Another example setting the (speed) to burn as 8x : -

 # wodim -v speed=8 dev=/dev/hdc image.iso
-

Erase CD-RW/DVD-RW

-You can quickly erase a CD-RW/DVD-RW using wodim with the blank=fast option. Example using the -device hdc in verbose mode: -

 # wodim -v blank=fast dev=/dev/hdc 
-

-Or you can have a full erase using the blank=all option (this will take a bit longer): -

 # wodim -v blank=all dev=/dev/hdc 
-

- - -

Nano

-The default text editor in SliTaz is nano. Once launched you can use <Ctrl + g> for the help menu. -To start nano, you can type nano from a console, a xterm terminal, or from the menu ---> Editors --> Nano. -

-The initialization file /etc/nanorc includes the files of colored syntax found in /usr/share/nano. -The user configuration file is ~/nanorc. To edit a file directly, just launch nano proceeded by the name of the -file. Example (<Ctrl+x> to save & quit): -

 $ nano Templates/script-shell.sh
-

- - -

LeafPad

-Leafpad is an ultra light and quick graphical text editor, handy for taking notes or editing configuration -files. You will find it in the menu or you can run it directly on a file via a terminal: -

 $ leafpad Templates/script-shell.sh
-

- - -

ISO Master - Create and edit ISOs

-ISO Master is a graphical tool allowing you to edit, manipulate and create ISO images which you can later store -and burn, It's simple and intuitive and lets you create ISO images the size you want. -

-Site Web : http://littlesvr.ca/isomaster/ -

- - -

Xpad - Mini note-taking application

-Xpad is a small application that can take quick notes via a 'sticky note' displayed on the desktop. Each -consists of a note pad that you can hide and customise via a right click on the window in question. -Once launched you can close Xpad via the dock located on the window manager taskbar. The notes are stored in -your local directory and are available at each session (if you use USB media with the LiveCD or on an -installed system). -

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/web-server.html --- a/en/doc/handbook/web-server.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,219 +0,0 @@ - - - - SliTaz Handbook (en) - LightTPD web server - - - - - - - - - - - - - - - -

- -

LightTPD Web Server

- -

About LightTPD.
/var/www - Root directory of documents.
~/Public - Public directory of users.
lighttpd.conf - LightTPD Configuration File.
Start, stop, restart the server.
Scripts CGI and Perl - CGI scripts using Perl.
Scripts CGI and Python - CGI scripts using Python.
Authentication - Protect directories using username and password.

- - -

About LightTPD

-This chapter describes the configuration and use of the LightTPD web server. It's a fast, secure, flexible HTTP -server, using a small memory footprint. It enables intelligent management of the cpu load and offers -FastCGI support, CGI, Auth, Output compression and the rewriting of URLs, etc. LightTPD is a cheap way to host your -own site on an old machine. -

-On SliTaz the server is automatically launched at system startup and is preconfigured with PHP. The root -documents served by default are in /var/www, this contains the default page index.html, -images are stored in the images/ directory. -LightTPD website: http://www.lighttpd.net/ -

- -

/var/www - Root directory of documents

-The /var/www folder is the root directory of documents - you can access this via the URL -http://localhost/. If you want to host a site, you can save all your documents -in here. If you want to host multiple sites, you'll need to create virtual hosts. Note you can also check the -http://localhost/server-status. - -

- -

~/Public - Public directory of users

-SliTaz provides the users of the system a public space to place documents, HTML in general. -This directory is named Public and must be within the root of your user space, such as /home/hacker/Public. -To create this directory, use the mkdir command: -

 $ mkdir ~/Public
-

-You can then have access via the URL: -http://localhost/~hacker/. You can also use the machine name or IP -address if you connect from another computer. -

- -

/etc/lighttpd/lighttpd.conf - LightTPD configuration file

-The main configuration file for LightTPD (lighttpd.conf) is located in /etc/lighttpd/. This file provided by -SliTaz is self-explanatory, just browse. You can find other examples on the LightTPD website. On -SliTaz you'll also find a vhosts.conf file for the configuration of any virtual hosts (hosting -several sites on the same server). -

- -

Start, stop, restart the web server

-By default, SliTaz starts the server automatically at boot, to prevent this you need to remove -lighttpd from the variable RUN_DAEMONS located in the system file -/etc/rcS.conf. To start, stop or restart the server, you can use the commands: -/etc/init.d/lighttpd [start|stop|restart]. Example to restart the server after -changing the configuration file: -

 # /etc/init.d/lighttpd restart
-

- - -

CGI scripts using Perl

-To configure the LightTPD server to locate the path of the perl binary and use CGI/Perl, you'll need to -install perl and modify the server configuration file. Example using Geany: -

 # tazpkg get-install perl
- # geany /etc/lighttpd/lighttpd.conf &
-

# CGI module. You can install Perl and assign .pl and .cgi scripts
-# to /usr/bin/perl
-$HTTP["url"] =~ "/cgi-bin/" {
-  cgi.assign = (
-    ".sh" => "/bin/sh",
-    ".cgi" => "/usr/bin/perl,
-    ".pl" => "/usr/bin/perl
-  )
-}
-

- - -

CGI scripts using Python

-To configure the LightTPD server to locate the path of the python binary and use CGI/Python, you'll need to -to install python and modify the server configuration file. Example using Geany: -

 # tazpkg get-install python
- # geany /etc/lighttpd/lighttpd.conf &
-

# CGI module. You can install Python and assign .py and .cgi scripts
-# to /usr/bin/python
-$HTTP["url"] =~ "/cgi-bin/" {
-  cgi.assign = (
-    ".sh" => "/bin/sh",
-    ".cgi" => "/usr/bin/python,
-    ".py" => "/usr/bin/python
-  )
-}
-

-For the changes to be taken into effect and to use your first CGI scripts on SliTaz, just -restart the LightTPD server: -

 # /etc/init.d/lighttpd restart
-

- - -

Authentication - Protection for the directories

-LightTPD provides authentication modules that can for example, protect a directory. The server -offers several authentication methods, but we will begin by using the basic method without encrypting any -passwords. In order to be able to use the module mod_auth, you must install the lighttpd-modules -package (tazpkg get-install lighttpd-modules). Once installed mod_auth -must be added to the list of modules: -

# Modules to load.
-# See /usr/lib/lighttpd for all available modules.
-#
-server.modules = (
-  "mod_access",
-  "mod_auth",
-  "...",
-)
-

-Now you can configure the modules by specifying the debug level and method (plain) and the -path to the file containing a list of names using a protected password to access the directories. You must also -define the directories that require authorization. In this example we'll protect the admin/ directory -and authorize its access to user hacker (user=hacker): -

# Authentication for protected directory.
-auth.debug = 2
-auth.backend = "plain"
-auth.backend.plain.userfile = "/etc/lighttpd/plain.passwd"
-auth.require = ( "/admin/" =>
-(
-"method" => "basic",
-"realm" => "Password protected area",
-"require" => "user=hacker"
-)
-)
-

-Finally, we now create the file containing the passwords, add a user and restart the server for testing. -The basic syntax for the file is user:password. You can create the file and add a user with the -echo command or edit with your favorite text editor. To add hacker:root -to the password file /etc/lighttpd/plain.passwd: -

 # echo "hacker:root" > /etc/lighttpd/plain.passwd
- Or :
- # nano /etc/lighttpd/plain.passwd
-

-To test the address: http://localhost/admin/, just restart the server: -

 # /etc/init.d/lighttpd restart
-

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/handbook/x-window.html --- a/en/doc/handbook/x-window.html Thu Jan 06 18:15:14 2011 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,273 +0,0 @@ - - - - SliTaz Handbook (en) - X Window System - - - - - - - - - - - - - - - -

- -

X Window System

- -

X Window System.
Tazx - SliTaz X configuration tool.
Slim - Simple Login Manager.
Xorg - X server.
Use Xvesa as X terminal - Launch a - graphical session from a remote machine.
Fonts - System Fonts.
Openbox - Window Manager.
Enlightenment (e17). - Desktop - environment.
JWM - Window Manager.

- - -

X11 - X Window System

-The X Window System or X11 provides a window manager running on -top of a X server. SliTaz by default uses the lightweight X server called -Xvesa from the Xorg project (www.x.org). -Xvesa can be started with the Slim login manager or directly from a Linux console -with the command startx, but for this you must first disable the -Login Manager. To reconfigure your X session you can use tazx -as root or as the current user if you start X from the command line. -

- - -

Tazx - SliTaz X configuration tool

-Tazx is the configuration tool to manage your X window sessions on a -SliTaz box. Simply select a resolution and press OK. You can also select a -(Xorg) session by selecting a video driver best suited to your hardware. -After you first run 'startx', the configuration is saved in the executable -files ~/.xsession and ~/.xinitrc. These files are then used to start a -X session with 'startx' or via the Slim login manager and can be easily -altered with a text editor. Tazx can also be used to change your default -window manager. Example: tazx jwm. -

- - -

Slim - Simple Login Manager

-Slim is a lightweight session manager that is very easy to configure and is -customizable using system themes. The configuration file is found in -/etc/slim.conf. It defines window managers available via the -F1 key, the default user or theme, and the X window system parameters. -Slim offers special user commands like console to help manage -the session. -

-In LiveCD mode you can disable Slim with the boot option screen=text. -On an installed system you can remove the package or delete slim from the -RUN_DAEMONS variable in /etc/rcS.conf. -

-More details and themes can be found on the -website -

Default user

-Slim offers a way to pre-load a user login name, by default tux is configured -for convenience. You can change this by editing the Slim configuration file -/etc/slim.conf and modifying the line default_user or just -leave the line blank to avoid pre-loading a user name. Example: -

default_user        tux
-

- - -

Xorg

-By default, SliTaz provides the graphical mini-server Xvesa. Xorg server is available -in the packages on the mirror. Xorg is a very comprehensive server, but uses a lot more -resources than Xvesa. If your resolution is supported by the mini-server and you're happy -with the refresh rate, then there's no reason to use Xorg. -

-There is no GUI configuration which means having to use the command line in console mode. The installation -and configuration of the server is relatively simple and you can always go back and reuse Xvesa at any time. -Xorg is distributed in modular form, which means that you'll need to install the server, a few configuration -files and the right driver for your graphics card. However the xorg-server package has all -the correct dependancies to work directly with the vesa driver. Minimal install: -

 # tazpkg get-install xorg-server
-

-Once installed, you can go directly to the configuration or you can install the correct driver for your card -(provided you know it). Example using the Nvidia driver and listing all available drivers: -

 # tazpkg get-install xorg-xf86-video-nv
- List:
- # tazpkg search xorg-xf86-video
-

Automatic configuration of the server

- -

To configure the Xorg server you have two options: Xorg -configure -or the script xorgconfig. It is recommended that you start by using Xorg with -the -configure option. The automatic configuration of Xorg must be done in console -mode without an X-server running, this is achieved by closing all applications and windows and hitting -the alt-ctrl-del buttons. You should now be in console mode. Now you need to run Xorg with the --configure option and copy the newly generated file to /etc/X11: -

 
- # Xorg -configure
- # cp /root/xorg.conf.new /etc/X11/xorg.conf
-

-Finally you then change the configuration of Slim to use Xorg instead of Xvesa -and restart the window manager. -

Using Xorg with Slim

-In the Slim configuration file (/etc/slim.conf), we need to comment out -(#) the lines pertaining to Xvesa and change Xorg to the default_xserver: -

-default_xserver     /usr/bin/Xorg
-#default_xserver     /usr/bin/Xvesa
-#xserver_arguments   -ac -shadow dpms +extension Composite -screen 1024x768x24
-

-Now we can start Slim to return us to an X server session. -Slim works likes a daemon, it can be stopped or started from the console: -

 
- # /etc/init.d/slim start
-

xorg.conf - Configuration file

-Xorg uses the configuration file /etc/X11/xorg.conf. This file can be -automatically generated and edited with your favorite text editor. It is divided into -several sections, including the specification of paths, modules to be loaded, default screen, -mouse, keyboard, etc. This document provides only a few examples, it is advisable to run -xorgconfig once to generate a complete file to use as an example. - -

-Keyboard (en): -

-Section "InputDevice"
-	Identifier  "Keyboard0"
-	Driver      "kbd"
-	Option      "XkbRules"	"xorg"
-	Option      "XkbModel"	"pc105"
-	Option      "XkbLayout"	"en"
-	Option      "XkbVariant"	"en"
-EndSection
-

-Mice with auto detection protocol: -

-Section "InputDevice"
-	Identifier  "Mouse0"
-	Driver      "mouse"
-	Option	    "Protocol" "auto"
-	Option	    "Device" "/dev/input/mice"
-	Option	    "ZAxisMapping" "4 5 6 7"
-EndSection
-

-Composite extensions: -

-Section "Extensions"
-	Option      "Composite" "1"
-EndSection
-

- - -

Use Xvesa as X terminal

-You can use Xvesa as X terminal, if you have a machine on -the network that accepts Xdmcp connections. To enable this, -you can start the server with the option -query followed by -the machine name or IP address. Example of machine 192.168.0.2 -on a local network: -

 $ Xvesa -ac -shadow -screen 1024x768x24 -query 192.168.0.2
-

-The use of a graphical remote server can be of great use, although -reponse times of applications depend greatly on Internet -speed and the remote machine's power. This technique works -very well within a local area network (LAN) and allows you -to control applications installed on the remote machine directly -from the screen of the local machine from which you work. -Note that the distant remote machine may have -multiple accounts in use simultaneously and/or direct access. -

- - -

Fonts

-The management of Fonts (fonts) is powered by the package Fontconfig. -This package provides tools to add, list and manipulate fonts. The fonts -can be installed in user space or at the system level, this means that each user can use his/her own -fonts or the system adminstrator (root) can install fonts available to all users of the system. -If you use USB media associated with the SliTaz LiveCD, -you can easily install fonts and retain them the next time you use the cdrom. -

Installing fonts

-At the system level fonts are installed in the directory: -/usr/share/fonts, core SliTaz provides TTF Vera fonts, -they take up little space and are rendered correctly. At the root of user space ~/, -fonts are found in the hidden directory: .fonts. To create a home -directory to accomodate new fonts, you can use the graphical window manager emelFM2, -Clex or the command line: -

 $ mkdir ~/.fonts
-

-Once you have installed the fonts you need to run the fc-cache tool to generate -configuration files, this ensures that your fonts are available for use in applications: -

 $ fc-cache
-

- - -

- - - - -

- Copyright © SliTaz - - GNU General Public License;
- Documentation is under - GNU Free Documentation License - and code is valid xHTML 1.0. -

- - - - diff -r 111e058c9eff -r 18040398d744 en/doc/index.html --- a/en/doc/index.html Thu Jan 06 18:15:14 2011 +0100 +++ b/en/doc/index.html Thu Jan 06 23:01:09 2011 +0100 @@ -9,102 +9,115 @@ - + - - + - - -

- -

Navigation

- -

- - -

SliTaz Network

- + +

+ Deutsch | + Español | + Français | + Português | +

+ +

#!/GNU/Linux

- +

English documentation

Handbook & Cookbook

+ +

Navigation

+ +

English documentation

+ Most of SliTaz documentation is avalaible on the community Wiki + site. Manuals and a getting started guide is provided by each + SliTaz LiveCD, installed in /usr/share/doc/slitaz + and also available through the "Documentation" menu. +

Community Wiki
Getting started guide

+ +

Handbook - SliTaz Handbook. LiveCD usage, - package management, network or system administration +
Handbook & Cookbook
+ +
+ SliTaz Handbook - + LiveCD usage, package management, network or system administration and specific instructions. This Handbook is a community effort to provide high quality documentation for SliTaz users. It will help you get started with SliTaz GNU/Linux and show you how to configure the system to your own needs and preferences. This is the documentation that we advise you to read, - learn and consult first.
Cookbook - SliTaz Cookbook. + learn and consult first. +
+
+ SliTaz Cookbook - Information regarding the management, operation and development of the distribution. Instructions on how to use the wok and package receipts, descriptions of boot scripts - and rootcd files, and various tools.
Scratchbook - SliTaz Scratchbook. Describes the stages - of creating the very first SliTaz distribution commencing with instructions on compiling - the Linux kernel, installing the graphical server (Xvesa) and GTK applications, etc. - It contains techniques requiring time and motivation that enable you to build a GNU/Linux - system from source.

+ and rootcd files, and various tools. +

+ +

Scratchbook

+ Historicaly the Scratchbook was written when SliTaz was created and wasn't + made to be updated. By the time some SliTaz fellows migrated the book the + Wiki and have made some update: + Comunity Scratchbook +

+ SliTaz Original Scratchbook - + Describes the stages of creating the very first SliTaz distribution + commencing with instructions on compiling the Linux kernel, installing + the graphical server (Xvesa) and GTK applications, etc. It contains + techniques requiring time and motivation that enable you to build a + GNU/Linux system from source. +

Manuals

Tazpkg manual - SliTaz Package Manager.

New Wiki documentation

-All SliTaz documentation is migrating; more information, books and manuals can be found -at: doc.slitaz.org -

- -

Release Notes

SliTaz Release Notes provide detailed information about the stable version -and give a few useful tips to help you start using the system. On the core LiveCD, -Release Notes are installed and available through the "Documentation" menu. +and give a few useful tips to help you start using the system. On the core +LiveCD, Release Notes are installed and available through the "Documentation" +menu.

@@ -138,34 +146,35 @@ Release Notes - -

- -

-Last modification : 2010-03-28 17:00:00 - -Top of the page -

- -

- - -

- -

+ + diff -r 111e058c9eff -r 18040398d744 en/get/flavors.html --- a/en/get/flavors.html Thu Jan 06 18:15:14 2011 +0100 +++ b/en/get/flavors.html Thu Jan 06 23:01:09 2011 +0100 @@ -9,94 +9,83 @@ - + - + + - - -

- -

Navigation

- -

- - -

SliTaz Network

- + +

+ Deutsch | + Español | + Français | + Português | +

+ +

#!/GNU/Linux

- +

Get flavors

LiveCD to taste

+ +

Navigation

+ +

Get flavors

+ The system of LiveCD flavors is a simple means for the community + to generate ISO images for certain tasks by offering a selection + of specific packages. There are two possibilities to create a + flavor, use a flavor made by the community or create your own + via a simple to use graphical interface. +

+ +

-The system of LiveCD flavors is a simple means for the community to generate -ISO images for certain tasks by offering a selection of specific packages. -There are two possibilities to create a flavor, use a flavor made by the -community or create your own via a simple to use graphical interface. -

LiveCD ISO Image to taste

For convenience, the SliTaz team propose some ISO flavors for the stable and cooking versions:

- +

slitaz-3.0-xvesa.iso [29.0M] - Fully-featured desktop environment using the tiny Xvesa graphical @@ -117,19 +106,22 @@
slitaz-3.0-3in1.iso [30.0M] - 3in1 flavor containing the base, justx and core ISOs

Browse flavors directory on the mirror: - Stable | - Cooking

Getting and generating a flavor

+ Browse flavors directory on the mirror: + Stable | + Cooking +

+ +

Getting and generating a flavor

A flavor is a (.flavor) file to generate a special flavor. The graphical tool Tazlitobox can create a flavor in a few -mouse clicks. The Tazlito manual -and documentation provide -detailed instructions on the generation of flavors. On the +mouse clicks. The Tazlito +manual +and documentation +provide detailed instructions on the generation of flavors. On the command line, you can get a list of available flavors via tazlito list-flavors.

@@ -139,8 +131,8 @@ The stable and cooking versions offer the flavor core on the mirror, it can be used as a basis to create your own flavor. The documentation in the Handbook provides all the necessary -instructions to create -your own LiveCD flavor. +instructions to create your own LiveCD flavor.

If you have created your own flavor to taste, you can send it on the @@ -148,34 +140,35 @@ tested and included in the official flavors.

- -

-Last modification : 2008-03-25 10:30:00 - -Top of the page -

- -

- - -

- -

+ + diff -r 111e058c9eff -r 18040398d744 en/get/index.html --- a/en/get/index.html Thu Jan 06 18:15:14 2011 +0100 +++ b/en/get/index.html Thu Jan 06 23:01:09 2011 +0100 @@ -9,87 +9,85 @@ - - + + - + + - - -

- -

Navigation

- -

- - -

SliTaz Network

- + +

+ Deutsch | + Español | + Français | + Português | +

+ +

#!/GNU/Linux

- +

Get SliTaz

Downloads

+ +

Navigation

+ +

Get SliTaz

+ Download the latest stable version for production purpose or + a solid desktop environment. Use the Cooking version to test + and help us improve the distribution. +

LiveCD Stable version - + Bootable ISO image of the current stable version.
LiveCD Cooking version - + Bootable ISO image of the cooking version.
Floppy disk - Bootable + startup disk to launch the LiveCD, a USB stick, etc.
LiveCD to taste - Flavors and loram.

+ +

LiveCD Stable version - Bootable ISO image of - the current stable version.
LiveCD Cooking version - Bootable ISO image of - the cooking version.
Floppy disk - Bootable startup disk to launch - the LiveCD, a USB stick, etc.
LiveCD to taste - Flavors and loram.

Downloads

General information

@@ -231,34 +229,35 @@ is also available for people who can't use a CD-ROM, USB key or Ethernet card.

- -

-Last modification : 2010-03-14 22:30:00 - -Top of the page -

- -

- - -

- -

+ + diff -r 111e058c9eff -r 18040398d744 en/index.php --- a/en/index.php Thu Jan 06 18:15:14 2011 +0100 +++ b/en/index.php Thu Jan 06 23:01:09 2011 +0100 @@ -25,15 +25,14 @@

- Deutsch | - Español | - Français | - Português | -

| - i18n +

+ Deutsch | + Español | + Français | + Português | +

Deutsch | Español | - Français | + Français | Português

diff -r 111e058c9eff -r 18040398d744 en/news/2007.html --- a/en/news/2007.html Thu Jan 06 18:15:14 2011 +0100 +++ b/en/news/2007.html Thu Jan 06 23:01:09 2011 +0100 @@ -16,76 +16,67 @@ - - + - - -

- -

Navigation

- -

- - -

SliTaz Network

- + +

+ Français +

+ +

#!/GNU/Linux

- +

News archives

+ +

Navigation

+ +

News archives

+ Website news archives by year. Note that some links may be broken + due to website structure changes (mainly the doc who moved to its + own domain). +

News by year

+ 2007 | 2008 | 2009 +

+ +

2007

- -

-Archives: 2007 | 2008 | 2009 -

2007

16 Dec 2007 - SliTaz English forum
@@ -139,30 +130,32 @@ from TuxFamily mirror. Download.

- -

- - -

-Last modification : 2010-03-30 21:45:00 - -Top of the page -

- -

- - -

- -

+ + diff -r 111e058c9eff -r 18040398d744 en/news/2008.html --- a/en/news/2008.html Thu Jan 06 18:15:14 2011 +0100 +++ b/en/news/2008.html Thu Jan 06 23:01:09 2011 +0100 @@ -16,76 +16,68 @@ - - + - -

Navigation

- -

+ +

+ + +

+ +

Navigation

+ +

News archives

+ Website news archives by year. Note that some links may be broken + due to website structure changes (mainly the doc who moved to its + own domain). +

News by year

+ 2007 | 2008 | 2009 +

+ +

- -

SliTaz Network

- -

- - -

News archives

- -

2008

- -

-Archives: 2007 | 2008 | 2009 -

2008

31 Dec 2008 - Cooking 20081231 - Wifi and NTFS support
@@ -202,31 +194,32 @@ LiveCD.

- + + - - -

-Last modification : 2010-03-30 21:45:00 - -Top of the page -

- -

- - -

- -

- diff -r 111e058c9eff -r 18040398d744 en/news/2009.html --- a/en/news/2009.html Thu Jan 06 18:15:14 2011 +0100 +++ b/en/news/2009.html Thu Jan 06 23:01:09 2011 +0100 @@ -16,76 +16,68 @@ - - + - - -

- -

Navigation

- -

- - -

SliTaz Network

- + +

+ Français +

+ +

#!/GNU/Linux

- +

News archives

+ +

Navigation

+ +

News archives

+ Website news archives by year. Note that some links may be broken + due to website structure changes (mainly the doc who moved to its + own domain). +

News by year

+ 2007 | 2008 + | 2009 +

+ +

In the past...

- -

-Archives: 2007 | 2008 | 2009 -

2009

4 November 2009 - New Cooking 20091104 @@ -200,30 +192,32 @@

- -

- - -

-Last modification : 2010-03-30 21:45:00 - -Top of the page -

- -

- - -

- -

+ + diff -r 111e058c9eff -r 18040398d744 en/news/index.html --- a/en/news/index.html Thu Jan 06 18:15:14 2011 +0100 +++ b/en/news/index.html Thu Jan 06 23:01:09 2011 +0100 @@ -16,103 +16,96 @@ - - + - - -

- -

Navigation

- -

- - -

SliTaz Network

- +

+ Français +

+ +

#!/GNU/Linux

- +

News archives

- -

In the past...

- -

- - + +

+ +

Navigation

+ +

News archives

+ Website news archives by year. Note that some links may be broken + due to website structure changes (mainly the doc who moved to its + own domain). +

News by year

+ 2007 | 2008 + | 2009 | +

+ +

- -

-Last modification : 2010-03-30 21:45:00 - -Top of the page -

- +

- -

+ + diff -r 111e058c9eff -r 18040398d744 en/packages/index.html --- a/en/packages/index.html Thu Jan 06 18:15:14 2011 +0100 +++ b/en/packages/index.html Thu Jan 06 23:01:09 2011 +0100 @@ -4,93 +4,84 @@ SliTaz - Packages - - + + - + - + + - - -

- -

Navigation

- -

- - -

SliTaz Network

- +

+ Deutsch | + Español | + Français | + Português | +

+ +

#!/GNU/Linux

- +

Packages

# tazpkg get-install pkg

+ +

Navigation

+ +

Packages

+ This part of the site allows you to view all of the software packages + available on the SliTaz mirror. The pages are automatically updated + daily via a cron job. All packages are installable via the package + manager Tazpkg using the GUI or the command tazpkg get-install + pkgname. +

+ +

-This part of the site allows you to view all of the software packages -available on the SliTaz mirror. The pages are automatically updated daily via -a cron job. All packages are installable via the package manager Tazpkg using -the GUI or the command tazpkg get-install pkgname. -

Search packages

+ Web interface: Stable | + Cooking +

Stable

+ Raw packages.list: + Stable list | + Cooking list +

+ Main mirror: + http://mirror.slitaz.org/packages/ +

+ +

Documentation

-Stable packages Web interface: -Stable packages -

-Raw Stable packages lists on the mirror: packages.list | packages.txt +The SliTaz project provide a large documentation +to let you learn install and manage packages on your SliTaz GNU/Linux distribution. +The support forum members will help you +in case of trouble and is also the place to request a new package.

Cooking

-Cooking packages Web interface: -Cooking packages -

-Raw Cooking packages lists on the mirror: packages.list - | packages.txt -

- - -

- -

-Last modification : 2008-07-16 23:00:00 - -Top of the page -

- -

- - -

- -

+ + diff -r 111e058c9eff -r 18040398d744 en/search.html --- a/en/search.html Thu Jan 06 18:15:14 2011 +0100 +++ b/en/search.html Thu Jan 06 23:01:09 2011 +0100 @@ -22,15 +22,14 @@

- + + - - - -

- -

About SliTaz

-SliTaz is an open source and free operating system providing a fully featured -desktop or server in less than 30 Mb. SliTaz is simple to use, fast and stable. -More information about SliTaz... -

- - -

SliTaz Network

- -

- - -

+ +

#!/GNU/Linux

- +

SliTaz i18n project

Internationalization

+ +

Community

Join us on SCN
Labs i18n project

PO files

SliTaz Tools
Tazpkg

+ +

SliTaz i18n project

+ The main goal of SliTaz is to provide full support for a given + language, including the website, official Wiki documentation, + a dedicated forum and all SliTaz related project such as the + LiveCD GUI builder. +

+ Traduction is a community effort and everyone can help. You + welcome to join the team! You can find more pot files on + Hg, just pick up one, + translate it and sent it to the mailing list or upload it to + SliTaz Community Network aka SCN. +

+ +

Internationalization

SliTaz project Website is available in the following languages:

- -

- -Deutsch - -English - -Español - -Français - -Indonesian - -Português - -

+ Deutsch - + English - + Español - + Français - + Indonesian - + Português - +

-The main goal of SliTaz is to provide full support for a given language, including -the website, official documentation, Wiki community and a dedicated forum. -

Information

The website and documentation has been translated and is kept up-to-date by several contributors. For now, the actively maintained languages are @@ -104,6 +96,7 @@ Mailing List and the Labs.

Some additional languages can be installed through the Package Manager, but we are not able to provide support and documentation. SliTaz is a @@ -111,34 +104,35 @@ join us.

- -

-Last modification : 2010-01-10 22:00:00 - -Top of the page -

- -

- - -

- -

+ + diff -r 111e058c9eff -r 18040398d744 index.php --- a/index.php Thu Jan 06 18:15:14 2011 +0100 +++ b/index.php Thu Jan 06 23:01:09 2011 +0100 @@ -42,16 +42,15 @@

Language

@@ -69,7 +68,7 @@

Boot baby... boot!

diff -r 111e058c9eff -r 18040398d744 pics/website/header-img.png Binary file pics/website/header-img.png has changed diff -r 111e058c9eff -r 18040398d744 slitaz.css --- a/slitaz.css Thu Jan 06 18:15:14 2011 +0100 +++ b/slitaz.css Thu Jan 06 23:01:09 2011 +0100 @@ -40,6 +40,10 @@ color: #b64b22; } +#access img { + vertical-align: middle; +} + /* Header and title */ #header { @@ -213,7 +217,7 @@ /* Box and block. */ .infobox { - margin: 10px 60px; + margin: 20px 60px; padding: 12px; background: #f8f8f8; } @@ -497,6 +501,14 @@ color: black; background: #F3F3F3; border: 1px solid #DEDEDE; + border-radius: 4px; + -moz-border-radius: 4px; + -webkit-border-radius: 4px; +} + +p.get a { + font-weight: bold; + text-decoration: none; } .year:after {

Navigation

SliTaz Network

About

SliTaz project

Navigation

About us

Introduction

Introduction to the project

Overview

Overview

Web site & i18n

Web site & i18n

Reviews

Reviews

3.0 - March 2010

3.0 - March 2010 & Cooking - Jan 2010

2.0 - April 2009

2.0 - April 2009

1.0 - March 2008

1.0 - March 2008

Cooking - January 2010

SliTaz Network

SliTaz Website

Navigation

SliTaz Network

Association

Infrastructure and services

Navigation

Association

Infrastructure and services

Bank Transfer

Postal Address

SliTaz Network

SliTaz Website

Navigation

SliTaz Network

Articles of the Association

Statutes

Navigation

Articles of the Association

Statutes

General

Article 1: Name, location and duration

SliTaz Network

SliTaz Website

Navigation

SliTaz Network

Development

SliTaz Developers corner

Navigation

Development

SliTaz Developers corner

KISS and comply to standards

KISS and comply to standards

Tank - Build host & home

Tank - Build host & home

Mercurial repositories

Mercurial repositories

~/.hgrc

~/.hgrc

Implementation of iconv()

Implementation of iconv()

Tazpkg Packages

Tazpkg Packages

Website Management and Books

Website Management

xHTML coding style

Diff and patch

Diff and patch

SliTaz Network

SliTaz Website

SliTaz Cookbook (en)

Boot scripts

SliTaz and startup

/etc/init.d/* - Directory of scripts and daemons

/etc/init.d/rcS - Primary initialization script

Specific scripts and daemons

bootopts.sh - LiveCD mode options

network.sh - Initializing the network

i18n.sh - Internationalization