# HG changeset patch # User Christopher Rogers # Date 1298722638 0 # Node ID 70b5f3ae5339e1fbde52cc09e28ac3f6ecc7ca0b # Parent a779af7ea2b85e2727d99f557e2609a4a3bf1086 Add pages/en folder. diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/cookbook/advancedhg.txt --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/pages/en/cookbook/advancedhg.txt Sat Feb 26 12:17:18 2011 +0000 @@ -0,0 +1,127 @@ +====== Advanced usage of Mercurial ====== + +==== Use an external tool to merge ==== + +If you want to use tools presented on this page, MQ particularly has a tool to manage merges (when several commits overwrite each other and you have to edit the result manually) which will probably be useful to you. SliTaz proposes Meld, a light software that can do that well. After installation, tell Mercurial to use it if necessary by putting it in your ~/.hgrc: + + +[ui] +merge = meld + + +==== Useful extensions ==== + +To add an extension, you can use the ~/.hgrc file: + +[extensions] +name = adress + +Some extensions are packed within Mercurial, so it's not necessary to give them addressess. It's the case of the four following: + +**color** +Add color in Mercurial. Useful when displaying differences between several versions of a file. + +**hgext.fetch** +Add the command hg fetch, which regroups hg pull && hg merge && hg update. + +**hgext.graphlog** +Add the command glog, which displays the revision tree along with the log. It's advised to limit the length of the log with option -l (i.e.: -l 10). Option -p displays the detail of differences introduced at each commit. + +**mq** +This tool is explained in detail below. It allows you to manage a patch-list for a Mercurial repository: apply them, unapply, update, etc. This extension adds several commands which generally start with 'q'. Some webpages detail this tool, search: mercurial mq. + + +==== Basic functionality of MQ ==== +In a mercurial repository, create a patch repository with a controlled revision; it's a repository of patches into which the changes can be committed using Mercurial, like a repository within a repository: +hg qinit -c + +Après avoir procédé à des modifications, les enregistrer en temps que patch plutôt que les commiter : +After modifications, save them as a patch instead of committing them: +hg qnew nom_du_patch + +List applied/unapplied patches: +hg qseries -v + +Add changes to the current patch (the last one applied): +hg qrefresh + +Apply the next patch from the queue: +hg qpush + +Apply all patches: +hg qpush -a + +Unapply current patch: +hg qpop + +Unapply all patches: +hg qpop -a + +Go to a given patch in the queue: +hg qgoto patch + +Add a message to the current patch (before committing it): +hg qrefresh -m "Message" + +Transform a patch into a commit: +hg qfinish patch + +Commit changes made in the patch repository: +hg qcommit -m "Message de commit" + +Note: Patches are saved into .hg/patches. The file .hg/patches/series can be manually edited to change the application order of the patches; but take care if several patches have the same target file: it can create problems. + +==== MQ & Merge ==== + +**General idea** + +Patches can be updated using the merge tool of Mercurial: it's easier than editing them manually. To do this, it's necessary to have two heads in the repository. One being the repository with patches applied ontop; the other the repository with the new commits/updates/etc: + + +o New repository revision +| +| +| o Patches +| | +| / +| +o Repository before patch application + + +The patches branch will next be merged into the new branch and MQ will use the merge function from Mercurial to update the patches. Please note that using an external merge tool (such as meld proposed previously) is highly recommended. + +Create the head patches: + +qpush -a +hg tags # Remember/Note the number of the revision qparent +qsave -e -c # Save the status of the patches, this save will be used during the merge. (Remember/Note the number at the end of patches.N; it's generally 1) + + +Create the new head: + +hg update -C # Go to the revision noted before. + +# Next, do what you planned to: +# Update: +hg pull -u +# Commit new changes, make the modifications then: +hg commit -m "message" +# Edit a patch: +hg qgoto patch # Then do the modifications and: +hg qrefresh + +To launch the merge: +hg qpush -a -m + +Clean the repository: + +hg qpop -a +hg qpop -a -n patches.N +rm -r .hg/patches.N + + +Save the changes made into the patch repository: +hg qcommit -m "Updated to match rev???" + +Re-apply the patch queue: +hg qpush -a \ No newline at end of file diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/cookbook/bootscripts.txt --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/pages/en/cookbook/bootscripts.txt Sat Feb 26 12:17:18 2011 +0000 @@ -0,0 +1,89 @@ +====== 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 any commands placed for the system to start. + +===== /etc/init.d/* - Directory of scripts/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 learn 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 enables you to use a USB key or external hard disk ///home// partition with the option //home=usb// or //home=sda[1-9]//. Note that 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... " + + +=== wpa_action.sh - Wireless network === + +This script is applied by //network.sh// to start/restart the DHCP server if you use a dynamic IP. + +=== 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//), virtual terminals (ttys) and actions in the event of a reboot or disruption. You will find a complete example with accompanying notes in [[en:cookbook:slitaztools|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 + diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/cookbook/buildbot.txt --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/pages/en/cookbook/buildbot.txt Sat Feb 26 12:17:18 2011 +0000 @@ -0,0 +1,59 @@ +====== 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 [[http://labs.slitaz.org/wiki/distro/Tazbb|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 any 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 diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/cookbook/buildhost.txt --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/pages/en/cookbook/buildhost.txt Sat Feb 26 12:17:18 2011 +0000 @@ -0,0 +1,89 @@ +====== 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 + \ No newline at end of file diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/cookbook/devcorner.txt --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/pages/en/cookbook/devcorner.txt Sat Feb 26 12:17:18 2011 +0000 @@ -0,0 +1,182 @@ +====== Developer's 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 something to do, i.e. proof-reading or writing documentation, sending bugs or patches to the [[http://www.slitaz.org/en/mailing-list.html|Mailing List]], gaining access to the wok and pushing some new packages or simply to help others on the [[http://www.slitaz.org/en/mailing-list.html|Mailing List]] or [[http://forum.slitaz.org/|forum]]. SliTaz has got [[http://hg.slitaz.org/|Mercurial repositories]] hosted on a SliTaz system. Developers can ask for a new repo if needed and contributors have write access to correct typos, scripts, etc. + +SliTaz is a tiny community and listens to its users. There are several developers who are active on the [[http://forum.slitaz.org/|forum]] and the [[http://www.slitaz.org/en/mailing-list.html|Mailing List]]. + +For artists there is a dedicated [[http://community.slitaz.org/image|website]] -- simply create an account and post your graphics or pictures. The site is managed by the community. If you want to lend a hand to administer the site, please contact a contributor or e-mail the discussion list. + +\\ + +===== KISS & Comply to Standards ===== + + * First and foremost: keep it simple! + * Follow the most reliable standards in coding, documenting and all other areas of development. + * Carefully draft and write high quality documentation, including summarising complicated sections or processes, as well as detailed and informative tutorials. + * Provide a stable and robust system, and aim to keep the rootfs on the LiveCD light enough to run on machines with as little as 128 MB RAM. + * Use the range of tools available where possible; there is GTK+2, Dialog, SHell scripts and even PHP coding tools on the distribution and these are instantly available to everyone. + * The idea is to think small and not to duplicate. + +\\ + +===== 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. Developers can compile packages and maintainers of the mirror can handle synchronization. [[http://tank.slitaz.org|Tank]] also hosts the website, web boot and mercurial repositories. + +[[en:cookbook:buildhost|Instructions]] on using the build host are described in the Cookbook. + +\\ + +===== SliTaz Packages ===== + +The TazPkg packages in SliTaz are automatically created via TazWok and a receipt in the wok. The Cookbook [[en:cookbook:wok|describes]] the use of tools and the format of [[en:cookbook:receipt|receipts]]. These are required reading before creating SliTaz packages! + +In terms of package selection, the idea is to offer a package by task or functionality, i.e. the lightest application in the field and not to provide another just on preference. Note that the current packages are not immutable, if you find an alternative that is lighter, with more features or more sexy for a few extra KB, you can suggest it on the [[http://www.slitaz.org/en/mailing-list.html|Mailing List]]. Particular attention is given to packages for the LiveCD, these should be stripped, removing unnecessary dependencies and compiler options. In general candidate packages for the core LiveCD are discussed on the [[http://www.slitaz.org/en/mailing-list.html|Mailing List]]. + +Before you begin to compile and create packages for SliTaz, be sure that the work doesn't already exist in the [[http://hg.slitaz.org/wok-undigest/|undigest wok]]. Don't forget that the members of the mailing list are there to help you and that the documentation of the [[en:cookbook:wok|wok and tools]] exists to help you get started. + +\\ + +===== Naming of Packages ===== + +In most cases the package name is the same as the source, except for Python, Perl, PHP, Ruby and Lua modules. For example, the package providing a //Kid// template system written in Python and XML is named: //python-kid//. + +\\ + +===== Mercurial Repositories ===== + +Mercurial, or Hg, repos can be browsed or cloned by anyone using the URL: [[http://hg.slitaz.org/|hg.slitaz.org]]. People with write access can directly use [[http://repos.slitaz.org/|repos.slitaz.org]] which requires authentication. 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 that you are not root. Personal ~/.hgrc file example: + + +[ui] +username = FirstName LastName + + +\\ + +=== Clone, Modify, Commit, Push === + +You must be in the repository to be able to use 'hg' commands. + + * Clone a repo, example for wok: + + $ hg clone http://repos.slitaz.org/wok + + * Check all logs, or just the last log: + + $ hg log + $ hg head + + * Add or modify one or more files and commit: + + $ hg add + $ hg status + $ hg commit -m "Log message..." + $ hg log + +You can use the command //rollback// to roll back to the last transaction. + + * Before pushing changes to the server, it is safe to pull once: + + $ hg pull + $ hg push + +Done! Your changes, code or corrections are now on the server. + +\\ + +=== Updating a Local Wok === + +To update your working directory with the changes that others have since committed to the server (//pull// the changes): + + $ hg pull + $ hg update + +\\ + +=== Useful Commands === + +There are a number of commands that you may find useful: + * **hg help** -- Display the full list of commands. + * **hg rollback** -- Undo the last action performed (commit, pull, push). + * **hg log ////** -- Display a package log. + * **hg head** -- Display the last log. + +\\ + +===== Implementation of iconv() ===== + +SliTaz uses iconv() provided by GNU glibc - any packages that offer libiconv must use the library contained in glibc-locale. There is therefore no longer a libiconv package (1.2 MB) in SliTaz. + +\\ + +===== Website Management and Books ===== + +The website and books (Handbook and Cookbook) are managed via a Mercurial repository, they can be cloned by: + + $ hg clone http://hg.slitaz.org/website + +Or if you have the proper permissions: + + $ hg clone http://repos.slitaz.org/website + +\\ + +===== xHTML Coding Style ===== + +The website must have a consistent look-and-feel; this is also used in the wiki pages and local documentation. To achieve this: + + * The pages and books are written in xHTML 1.0 Transitional. + + * The colours for the body and the titles are placed directly on the page so the links are easy to follow. + * The title, a Level 1 heading, is used only once (at the top); + * Level 2 is the title of the document; + * Levels 3 and 4 are then used for the subtitles. + + * If a list is used instead with smart anchors, it starts at the top just after the title of level 2. + + * Paragraphs are always contained in

tags. + + * For indentation, we use tabs. The reasons being semantics and to take up less space in terms of octets (bytes). + + * To put code, like the name of a command inside a paragraph, tags is the preferred method. + + * Commands and terminal output are displayed with 

 tags -- example:
+
+   $ command
+
+  * To view text that can be copied and pasted, such as scripts, bits of code, sample configuration files etc., use 
 tags but with a CSS class named "script". Example: 
+
+
+
+code...
+

+
+
+  * To emphasize words, use  tags.
+
+  * Internal links are relative.
+
+  * Remember to check the validity of the code with the online validator of the W3C.
+
+\\
+
+===== The diff and patch Commands =====
+
+The utilities //diff// and //patch// are command-line tools for creating and implementing a file containing differences between two files. This technique is often used for collaboration and the changes made to the original file can be clearly extracted. To create a diff file readable by humans in a simple text editor, you must supply the -u option: 
+
+   $ diff -u file.orig file.new > file.diff
+
+To apply a patch:
+
+   $ patch file.orig file.diff
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/cookbook/receipt.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/cookbook/receipt.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,158 @@
+======= Recipes ======
+
+
+This document describes the opportunities offered by the recipes used by Tazwok to compile and generate packages for SliTaz and Tazpkg through The wok and tools. The recipe for a package is also used by Tazpkg to install/uninstall and provide information about a .tazpkg package. Each recipe 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 recipe 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 recipe states 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 recipe 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 recipe 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 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 recipe 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 recipe; 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 recipe 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's 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 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..."
+}
+
+
+=== pre_remove() and post_remove() ===
+
+These functions are initiated by Tazpkg when removing 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 remove commands for Tazpkg.
+pre_remove()
+{
+	echo "Processing pre-remove commands..."
+}
+post_remove()
+{
+	echo "Processing post-remove 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
+}
+
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/cookbook/releasetasks.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/cookbook/releasetasks.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,18 @@
+====== 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.
+
+    * [[http://hg.slitaz.org/slitaz-doc/ | SliTaz Doc repo]]
+    * [[http://labs.slitaz.org/wiki/slitaz-doc | SliTaz Doc on the Labs]]
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/cookbook/rootcd.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/cookbook/rootcd.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,115 @@
+====== Rootcd ======
+
+Descriptions of files contained on the cdrom. 
+
+===== Syslinux/isolinux =====
+
+Syslinux and the (SliTaz) main bootloader - 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 uses the configuration file isolinux.cfg. Here's an example of an 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 [[:en:cookbook:slitaztools|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. 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 find in [[:en:cookbook:slitaztools|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 the 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 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. Example using a 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. 
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/cookbook/slitaztools.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/cookbook/slitaztools.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,19 @@
+====== SliTaz Tools ======
+
+The SliTaz Toolbox
+
+    * Mercurial repository.
+    * *box  - dialog/GTKdialog.
+    * Archives source: [[http://download.tuxfamily.org/slitaz/sources/tools/|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. They accompany the [[http://doc.slitaz.org/en:scratchbook:start|Scratchbook]] and help the SliTaz developers. 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. 
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/cookbook/start.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/cookbook/start.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,32 @@
+====== 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 [[en:scratchbook:start|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. 
+
+==== Table of contents ====
+
+    * [[en:cookbook:devcorner|Developer's Corner]]  - ReadMe page for Developers.
+    * [[en:cookbook:receipt|Receipts]]  - Receipts (recipes) for creating (cooking) SliTaz packages.
+    * [[en:cookbook:wok|Wok]]  - Creating SliTaz packages from source using Tazwok. (Uses a receipt.)
+    * [[en:cookbook:buildbot|Build Bot]] - Automated cooking, testing and reporting of Wok packages.
+    * [[en:cookbook:buildhost|Build Host]]  - The SliTaz host.
+    * [[en:cookbook:slitaztools|SliTaz Tools]]  - The Toolbox.
+    * [[en:cookbook:advancedhg|Advanced usage of Mercurial]] - Add extensions to Mercurial and use MQ.
+    * [[en:cookbook:releasetasks|Release Tasks]]  - List of things to do before publishing a new version.
+    * [[en:cookbook:bootscripts|Boot Scripts]]  - The start-up and shut-down scripts.
+    * [[en:cookbook:rootcd|Root cdrom (rootcd)]]  - Descriptions of files contained on the cdrom.
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Medium  |
+|Review| Minor Updates FIXME |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Make all pages in cookbook current as of 3.0|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/cookbook/wok.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/cookbook/wok.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,145 @@
+====== Wok & Tools ======
+
+===== Overview =====
+
+[[http://hg.slitaz.org/tazwok/raw-file/tip/doc/tazwok.en.html|Tazwok]] is used to compile and generate code (cooking) via instructions found in a receipt. It places compiled files in to a directory and calls upon Tazpkg to package said directory. The receipt found in a wok has a different "bottom half" to that of a Tazpkg; Tazwok has rules for compilation //and// packaging (which it forwards to Tazpkg), whereas Tazpkg is only concerned with packaging.
+
+Tazwok is one of many small utilities the SliTaz project uses to automatically rebuild the distribution from source. The project also offers an archive of [[en:cookbook:slitaztools|tools]] containing various small utilities, examples and configuration files. The distribution generator [[http://hg.slitaz.org/tazwok/raw-file/tip/doc/tazwok.en.html|Tazlito]] is designed for users and developers; it can 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 [[http://doc.slitaz.org/en:cookbook:devcorner|development]] page that provides information on SliTaz project management.
+
+=== Wok Structure and Organisation ===
+
+The //wok// is a directory structure that houses all the available packages. Each directory contains at least one receipt to download, unpack, compile and generate a package. Tazwok also needs to create a directory to store downloaded sources (//$SOURCES_REPOSITORY//, usually ///home/slitaz/src//) and a repository of generated packages (//$PACKAGES_REPOSITORY//, usually ///home/slitaz/packages//); these values can be configured in the ///etc/tazwok.conf// file.
+
+There is more than one Wok on the [[http://hg.slitaz.org|Mercurial repositories]]:
+
+  *  **wok-undigest**: //contributions awaiting testing/bug-fixing for inclusion in the unstable Wok//
+  *  **wok**: //packages for the unstable, Cooking release//
+  *  **wok-stable**: //packages for the stable SliTaz release//
+
+Initially, any contributions will be committed to the //undigest// repository. When the package has seen sufficient testing with regards to automatic generation, it can be moved to the Wok.
+
+
+===== Preparation =====
+
+The [[en:cookbook:devcorner#mercurial-repositories|Developer's Corner]] provides invaluable background information. Please ensure you have read and understood it before continuing.
+
+To begin using the Wok, [[http://hg.slitaz.org/tazwok/raw-file/tip/doc/tazwok.en.html|Tazwok]] must already be installed on the system along with the main development tools (binutils, compiler, libraries-dev, make). This requires you to install the meta-package //slitaz-toolchain//:
+
+
+ # tazpkg recharge
+ # tazpkg get-install slitaz-toolchain
+
+
+To access the SliTaz repositories, you will need to install the //mercurial// package:
+
+
+ # tazpkg get-install mercurial
+
+
+More information on the use of the Mercurial VCS is available from its [[http://mercurial.selenic.com/|website]] and the "[[http://hgbook.red-bean.com/|Hg Book]]".
+
+=== Cloning the Wok ===
+
+If you are to generate a package for inclusion in the SliTaz repositories, it is necessary to first obtain the current wok by using Mercurial. This is called //cloning// the Wok, a procedure that downloads the entire Wok and all its history to a working directory. **If you wish to only use Tazwok to build packages for personal use, this is not necessary.** See the [[#creating-a-personal-wok|Personal Wok]] section below instead.
+
+The usual destination for a Wok clone is ///home/slitaz/wok//:
+
+
+ $ hg clone http://hg.slitaz.org/wok/ /home/slitaz/wok 
+
+
+This download may take some time; you will have a complete directory structure of the [[http://hg.slitaz.org/wok/|Cooking wok]] as a working directory.
+
+The Wok is one of many projects hosted in the [[http://hg.slitaz.org|Mercurial repositories]]. Individual packages are grouped as a large project (the Wok, Wok-Stable or Wok-Undigest) and is not its own sub-project but merely a sub-directory; Mercurial cannot (yet) clone specific parts of a project thus you cannot clone an individual package.
+
+=== Creating a Personal Wok ===
+
+If your packages are only for personal use and are not intended for inclusion in the SliTaz repositories, a wok can be created from scratch. 
+
+ # tazwok gen-clean-wok 
+
+
+===== Compiling and Generating Packages =====
+
+Before compiling your first package, Tazwok must know where your working directory is. By default the path is ///home/slitaz/wok// but you can change this or rename the wok that you want to download. To view and check Tazwok paths that will be used, and the number of packages in the wok, you can ask Tazwok for statistics:
+
+ # tazwok stats 
+
+The process for generating a SliTaz package from source can be summarised thus: [[http://www.tuxfiles.org/linuxhelp/softinstall.html#s2|configure]], [[http://www.tuxfiles.org/linuxhelp/softinstall.html#s3|compile]] & [[http://linux.die.net/man/1/strip|strip]].
+
+We do not carry out the '//make install//'-style step ourselves; the built files are not to be installed in the system but left in the output directory (_pkg), ready for packaging.
+
+When generating your first package, it is advisable to [[http://doc.slitaz.org/en:cookbook:devcorner#kiss-comply-to-standards|keep it simple]] and build your package without changing its receipt or seeking dependencies. M4 is an ideal candidate for your first //cook//:
+
+ # tazwok cook m4 
+
+When Tazwok has finished building M4, its package is placed in the directory specified by the configuration file (///home/slitaz///packages by default). If all went well, you can install the package on the host system or use it to generate a LiveCD distribution via Tazlito!
+
+When you are familiar with [[en:cookbook:receipt|receipts]] and the compilation process, you can use the following command to create a new package (and a wok, if you don't have one) before interactively writing its receipt:
+
+ # tazwok new-tree  --interactive 
+
+Be sure to read the documentation on the options provided by the [[en:cookbook:receipt|receipt]] and the [[en:guides:tazwoktips|Tazwok Tips]] to avoid frustration!
+
+
+=== Cooking Multiple Packages with cook-list ===
+
+Tazwok can compile several packages with a single command. This is achieved with a //cooking list//, a text file of one package per line. Tazwok can accept a cook-list with the command of the same name; for example, to cook the //mypkgs// cook-list:
+
+ # tazwok cook-list mypkgs.cooklist 
+
+There are example lists in ///usr/share/examples/tazwok/cooklists//.
+
+
+===== Package Compilation Options =====
+
+While you are free to use any options you want, it is necessary to respect the FSH, the documentation in ///usr/share/doc// and follow the FreeDesktop standards (.desktop).
+
+
+=== Package-Specific ===
+
+Package-specific options are your 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 to Include/Exclude ====
+
+Generally, the base packages contain no //man//, //info// or //doc// files, nor static libraries; we have to create them via a package-doc or a package-dev. Note that SliTaz does not intend 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. By contrast, writing documentation in the Handbook is more appreciated as it is widely-available and can be updated and improved easily.
+
+In terms of configuration, the aim is to offer basic configuration files to run the package directly. Special cases exist such as the web server //LightTPD//, for example, where SliTaz supplies configuration files and start-up scripts 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 best for the end-user. The ///usr/share/examples// directory has example configurations and other kinds of useful information.
+
+
+===== Package Categories =====
+
+The categories of packages exist only for informational purposes and are not fixed. The idea is to classify packages so that a web page that recovers data in the package receipt, can be generated each night. For the short term, place development packages in 'devel', Xorg in 'x-window' and the variety of new packages in 'extra'
+
+
+===== Structure of a Wok Package =====
+
+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);
+    * **receipt**: The ever-present [[en:cookbook:receipt|receipt]];
+    * //**description.txt** : (optional) The description of the package is included in the final package, copied to its root. Once installed, Tazpkg identifies this file as the description and can display it via //tazpkg desc pkgname//.//
+    * //**taz/** : Directory tree containing the package Tazpkg generated, the compressed package is stored in the directory specified by $PACKAGES_REPOSITORY in the Tazwok configuration file.//
+
+Tazwok will automatically call upon Tazpkg to package the //taz// directory. It also forwards any packaging instructions found in the receipt.
+
+===== Structure of a Tazpkg =====
+
+The SliTaz packages are cpio archives containing files and a file-system compressed with gzip:
+
+    * **fs/**: //Pseudo-file-system containing all the files to install.//
+    * **receipt**: //The [[en:cookbook:receipt|receipt]].//
+    * **files.list**: //A list of files in the package.//
+    * //**description.txt**: The description of the package (optional).//
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/devnotes/ash-benchmarks.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/devnotes/ash-benchmarks.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,174 @@
+Some tips to speed-up scripts... Add yours, and put the better ones on the top of page :)
+
+==== Sed substitution vs Variable substitution ====
+
+**Information**
+
+In some case, both tools can do the same job. As a build-in ash/bash command, variable substitution is a faster.
+Note: this is always true - you can compare each type of variable substitution with an equivalent using an external tool.
+
+**Benchmark**
+
+$ echo '#!/bin/sh
+for i in $(seq 1 1000); do
+	echo "slitaz" | sed 's/slitaz/SliTaz/'
+done' > /tmp/slow
+$ echo '#!/bin/sh
+for i in $(seq 1 1000); do
+	A=slitaz
+	echo "${A/slitaz/SliTaz}"
+done' > /tmp/speed
+$ chmod +x /tmp/slow /tmp/speed
+$ time /tmp/slow
+> real	0m 12.40s
+$ time /tmp/speed
+> real	0m 0.04s
+
+
+==== Group command vs. Sub-process ====
+
+**Information**
+
+Group command "{}" group several commands into one (as a function). So, output can be grouped too: "{ com1; com2; } | com3". Sub-process "()" achieve something similar, but create a shell sub-process; which cost a lot more resources. Another difference is that, when you kill an application using CTRL^C, sub-process is killed instead of main application - while CTRL^C on grouped commands kill the application itself. Finally, changing directory or variables into sub-process will not affect main script while it does with grouped commands. Conclusion: always use group command instead of sub-processes, and take care ;D
+
+//Note:// group command need a newline before closing - or "; }".
+
+**Benchmark**
+
+$ echo '#!/bin/sh
+for i in $(seq 1 10000); do
+	( echo yo )
+done' > /tmp/slow
+$ echo '#!/bin/sh
+for i in $(seq 1 10000); do
+	{ echo yo; }
+done' > /tmp/speed
+$ chmod +x /tmp/slow /tmp/speed
+$ time /tmp/slow
+> real	0m 5.36s
+$ time /tmp/speed
+> real	0m 0.23s
+
+
+==== Grep vs Fgrep ====
+
+**Information**
+
+fgrep is exactly the same thing that grep if you don't use patterns (^,$,*,etc.). Fgrep is optimized to handle such case, particularly when you look for several different plain patterns. A difference can be found even if you look of only one pattern.
+
+**Benchmark**
+
+$ echo -e "line1\nline2\nline3" > /tmp/file
+$ echo '#!/bin/sh
+for i in $(seq 1 1000); do
+	grep 3 /tmp/file
+done' > /tmp/slow
+$ echo '#!/bin/sh
+for i in $(seq 1 1000); do
+	fgrep 3 /tmp/file
+done' > /tmp/speed
+$ chmod +x /tmp/slow /tmp/speed
+$ time /tmp/slow
+> real	0m 11.87s
+$ time /tmp/speed
+> real	0m 3.21s
+
+
+==== [ -n "text" ] vs [ "text" ] ====
+
+**Information**
+
+The two commands test if "text" exists. Using -n slow the process a little and weight the script a little too.
+
+**Benchmark**
+
+$ echo '#!/bin/sh
+for i in $(seq 1 1000000); do
+	[  -n "$i" ]
+done' > /tmp/slow
+$ echo '#!/bin/sh
+for i in $(seq 1 1000000); do
+	[ "$i" ]
+done' > /tmp/speed
+$ chmod +x /tmp/slow /tmp/speed
+$ time /tmp/slow
+> real	0m 15.56s
+$ time /tmp/speed
+> real	0m 14.11s
+
+
+==== [ -z "text" ] vs [ ! "text" ] vs ! [ "text" ] ====
+
+**Information**
+
+Theses three commands test if text doesn't exist. [ ! "text" ] and [ -z "text" ] have a similar processing time, while ! [ "text" ] is speeder.
+
+**Benchmark**
+
+$ echo '#!/bin/sh
+for i in $(seq 1 1000000); do
+	[  -n "$i" ]
+done' > /tmp/slow1
+$ echo '#!/bin/sh
+for i in $(seq 1 1000000); do
+	[  -n "$i" ]
+done' > /tmp/slow2
+$ echo '#!/bin/sh
+for i in $(seq 1 1000000); do
+	[ "$i" ]
+done' > /tmp/speed
+$ chmod +x /tmp/slow1 /tmp/slow2 /tmp/speed
+$ time /tmp/slow1
+> real	0m 15.53s
+$ time /tmp/slow2
+> real	0m 15.60s
+$ time /tmp/speed
+> real	0m 14.27s
+
+
+==== Awk vs Cut ====
+
+**Information**
+
+Awk, as cut, can be used to cut a field of a line. Awk can do many other things, while cut is a tool dedicated to this usage; it's why cut is a little faster for this task.
+ 
+**Benchmark**
+
+$ echo -e "field1\tfield2\tfield3" > /tmp/file
+$ echo '#!/bin/sh
+for i in $(seq 1 5000); do
+	awk '"'"'{ print $2 }'"'"' /tmp/file
+done' > /tmp/slow
+$ echo '#!/bin/sh
+for i in $(seq 5000); do
+	cut -f2 /tmp/file
+done' > /tmp/speed
+$ chmod +x /tmp/slow /tmp/speed
+$ time /tmp/slow
+> real	0m 16.61s
+$ time /tmp/speed
+> real	0m 15.90s
+
+
+==== [ condition1 -a condition2 ] vs [ condition1 ] && [ condition2 ] ====
+
+**Information**
+
+While && is a fast built-in function, in this case it uses two process (two test functions) instead one. So, using -a is a little faster, as the "AND" function itself is slower but make possible to use only one process.
+
+**Benchmark**
+
+$ echo '#!/bin/sh
+for i in $(seq 1 1000000); do
+	[ "$i" ] && [ "$i" ]
+done' > /tmp/slow
+$ echo '#!/bin/sh
+for i in $(seq 1 1000000); do
+	[  "$i"  -a "$i" ]
+done' > /tmp/speed
+$ chmod +x /tmp/slow /tmp/speed
+$ time /tmp/slow
+> real	0m 23.94s
+$ time /tmp/speed
+> real	0m 22.29s
+
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/devnotes/cook-flavor-from-scratch.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/devnotes/cook-flavor-from-scratch.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,186 @@
+====== Cook a flavor from scratch ======
+
+===== Introduction =====
+
+Welcome to this howto! it's the base for a second scratchbook which explains how to recompile SliTaz entirely from scratch including the toolchain. All jobs will be done using tazwok-experimental (actually in Alpha state). Even if the scripts have some major issues, the steps explained here should do the job without too many problems. Please report any problems to the author (tazpkg info tazwok-experimental gives you my mail).
+
+Having some knowledge about how the legacy SliTaz tools and basic commands work will help you to understand what's going on in this howto. However, simply copying/pasting the given command lines will probably work.
+
+==== Explanation ====
+
+Tazwok now provides tools to cook the [[en:terms:W?&#wok|wok]] from scratch using a minimal chroot. You have to use a special version of the wok called wok-experimental. It contains the needed patches which should be applied on top of the cooking wok. Explanations about how to obtain the wok experimental are here:  [[en:devnotes:prepare-experimental|Prepare experimental wok]].
+
+**Tools needed**
+  * A functional cooking system (live or installed), you also can use the [[http://people.slitaz.org/~gokhlayeh/experimental/iso/slitaz-experimental-base.iso|slitaz-experimental-base]] ISO.
+  * tazwok-experimental-0.0.2, tazchroot-0.0.1 and libtaz-0.0.1. Note: installing tazwok-experimental removes tazwok legacy.
+  * An internet connection to download sources.
+
+**Steps**
+  * Make the chroot (in this how-to we use the packages of the new toolchain from the experimental repository; but this should work with the cooking toolchain).
+  * Cook a temporary toolchain: it's a cross-compiled toolchain which will cook the "real" toolchain (the packaged one) without linking anything to the host system.
+  * Cook the definitive toolchain.
+  * Cook some of the other packages of one of the SliTaz flavors.
+  * Create the iso.
+  * Burn, boot & enjoy :).
+
+
+==== Install the tools ====
+
+Note: all the following commands should be executed as root. You don't have to add the experimental repository if you wish to use the cooking toolchain.
+
+Add the cooking-experimental repository as undigest:
+
+tazpkg add-undigest experimental http://people.slitaz.org/~gokhlayeh/experimental/packages
+
+
+Give it priority over the main repository:
+
+echo experimental > /var/lib/tazpkg/priority
+
+
+Install the cooking tools:
+
+tazpkg get-install tazwok-experimental
+tazpkg get-install tazchroot
+
+
+==== Cook toolchain ====
+
+The following command-lines work for a wok at: /home/slitaz/experimental/wok. If you put the wok elsewhere, you can use the option --SLITAZ_DIR=address; where the address is equivalent to /home/slitaz. This option must be used each time --SLITAZ_VERSION is used. You can also define SLITAZ_VERSION & SLITAZ_DIR globally using /etc/slitaz/slitaz.conf.
+
+Configure the //chroot//:
+
+tazwok configure-chroot --SLITAZ_VERSION=experimental
+
+
+If you have at least 1GB RAM free you can put the minimal chroot in RAM speeding-up the cooking process:
+
+sed 's~chroot_dir=.*~chroot_dir=/tmp/chroot-experimental~' -i /home/slitaz/experimental/tazchroot.conf
+
+
+All-in-one command to cook the toolchain packages:
+
+tazwok cook-toolchain --SLITAZ_VERSION=experimental
+
+
+At the end of this operation the chroot should be removed. If you have modified its address before, you have to do this manually:
+
+rm -r /tmp/chroot-experimental
+
+
+Toolchain packages are now ready to be used. They're actually are in the packages-incoming repository. If all was cooked fine it's possible to push them to the classical packages directory using:
+
+tazwok check-incoming --SLITAZ_VERSION=experimental
+
+
+You need to tell to tazpkg that you now have a local version of experimental:
+
+# If you had already defined the experimental repository:
+echo "/home/slitaz/experimental/packages" > /var/lib/tazpkg/undigest/experimental/mirror
+tazpkg recharge
+# Else:
+tazpkg add-undigest experimental /home/slitaz/experimental/packages
+echo experimental > /var/lib/tazpkg/priority
+tazpkg recharge
+
+
+Recook the toolchain packages except core (linux-api-headers/glibc/binutils/gcc) over themselves to consolidate it; in fact it's not really needed with an actual configuration but it's generally good to do to solve loop dependencies. It warrants consistency of the toolchain before and after an update of non-core toolchain packages. Note that core-toolchain should never be updated in this way - but by reusing the cook-toolchain script:
+
+tazwok chroot --SLITAZ_VERSION=experimental
+tazwok build-depends toolchain-cooklist | sed '1,/^gcc$/d' > /tmp/consolidate.list
+tazwok cook-list /tmp/consolidate.list
+rm /tmp/consolidate.list
+
+
+As packages has been re-cooked, you have to update the packages repository once again:
+
+tazwok check-incoming
+
+
+Still in the chroot for the next step.
+==== Cook packages of a flavor ====
+
+First you need data about cooking flavors:
+
+cd /home/slitaz/experimental/flavors
+hg clone http://hg.slitaz.org/flavors .
+
+
+Generate the cooklist for a given flavor. Note: for the next step, use the chosen flavor name instead of FLAVOR in the command line:
+
+tazwok gen-cooklist --list=/home/slitaz/experimental/flavors/FLAVOR/packages.list > /tmp/FLAVOR.list
+
+
+This list contains some already cooked packages, remove them:
+
+cat /tmp/FLAVOR.list | while read p; do
+	grep -q ^$p$ /home/slitaz/experimental/packages/packages.txt && \
+		sed "/^$p$/d" -i /tmp/FLAVOR.list
+done
+
+
+
+The cooklist is now ready to create the packages:
+
+tazwok cook-list /tmp/FLAVOR.list
+
+
+Update packages repository:
+
+tazwok check-incoming
+
+
+You can repeat these steps each time you wish to add new packages to your repository.
+
+Still in chroot for the next step.
+
+==== Create the ISO ====
+
+Actually tazlito uses /home/slitaz/flavors. Create a symbolic link:
+
+ln -s /home/slitaz/experimental/flavors /home/slitaz
+
+
+Set release as experimental for the future ISO:
+
+cd  /home/slitaz/flavors/FLAVOR
+mkdir -p rootfs/etc
+echo experimental > rootfs/etc/slitaz-release
+
+
+Configure your ISO to use your local repository:
+
+mkdir -p rootfs/var/lib/tazpkg
+echo /home/slitaz/experimental/packages > rootfs/var/lib/tazpkg/mirror
+
+
+Use tazwok-experimental instead of tazwok and add tazchroot:
+
+sed 's/tazwok/tazwok-experimental/' -i packages.list
+echo tazchroot >> packages.list
+
+
+Pack FLAVOR:
+
+tazlito pack-flavor FLAVOR
+
+
+Get FLAVOR:
+
+tazlito get-flavor FLAVOR
+
+
+Generate ISO:
+
+tazlito gen-distro
+
+
+Save ISO in your home dir:
+
+mv /home/slitaz/distro/slitaz-FLAVOR.iso /home/slitaz/distro/slitaz-FLAVOR.md5 /home/slitaz/experimental/iso
+
+
+Exit chroot:
+
+exit
+
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/devnotes/new-tazwok-illustrated.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/devnotes/new-tazwok-illustrated.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,270 @@
+====== The new tazwok illustrated! ======
+
+Some items in revenue no longer needed with the new version of tazwok. During migration, a number of problems appear.The information on these two points are available below, with examples.
+
+By simplifying the writing of recipes, we simplify the work and contribution that benefits everyone! 
+
+==== DEPENDS/BUILD_DEPENDS : ====
+Tazwok now uses the dependent variable for finding the necessary compilation dependencies. 
+Here's how it works:
+
+	* Tazwok tree list of all dependencies from the dependent variable
+	* For each package, if there is a shareholder *-dev package, it adds it to the dependencies
+	* Tazwok done the same for BUILD_DEPENDS.
+
+So far, when a packet was both dependency and build dependency, the recipe looked like this:
+
+
+DEPENDS="pkgX"
+BUILD_DEPENDS="pkgX pkgX-dev"
+
+Now that is enough:
+
+DEPENDS="pkgX"
+
+Where there were trees more complex dependencies, the recipe looked like this:
+
+# pkgY depend's on pkgX
+DEPENDS="pkgY"
+BUILD_DEPENDS="pkgY pkgY-dev pkgX pkgX-dev"
+
+Now that is enough:
+
+DEPENDS="pkgY"
+
+
+The recipes also contain many redundancies in the definition of addiction, for example:
+
+# pkgY depend's on pkgX
+DEPENDS="pkgY pkgX"
+
+Here, needless to say since pkgX will be installed along pkgY anyway (Tazpkg manages dependencies automatically!).
+
+By following these three councils, it appears that about half the packages in DEPENDS / BUILD_DEPENDS can be removed without changing the revenue system behavior, it is not nothing!
+
+An automated cleaning using some scripts is expected, after all recipes have been compiled at least once successfully using the new version of tazwok; In the meantime, these tips can be applied to writing new recipe for simplicity or manually with existing revenues when updating / corrections.
+
+**Examples:**
+	* graveman: http://hg.slitaz.org/wok/rev/7f0604e0bde0
+	* enlightenment & cie: http://hg.slitaz.org/wok/rev/85cd798d6997
+
+==== TARBALL/WGET_URL/SOURCE/download from the VCS ====
+
+This is important: always put the necessary tools to download / decompression sources in DEPENDS or BUILD_DEPENDS. This allows to define tazwok right firing order (do not try to cook a package that needs wget wget before himself).
+
+//The packets affected by this://
+	* wget url for https, ftps and some URLs that busybox does not include
+	* mercurial/subversion/git: they are used to obtain the source
+	* tar/unzip: sometimes necessary to unpack the sources.
+
+By default, tazwok re-sources in compact format .tar.lzma. He calls PACKAGE-VERSION.tar.lzma or SOURCE-VERSION.tar.lzma if SOURCE is defined. Note: Choose the name of the archive is now the only function of the variable SOURCE!
+
+Tazwok now supports files or "weird" URL (download.php?version=foo&blah=Idontknowwhat). The logic is: if WGET_URL does not end with tarball, then names the file downloaded tarball.
+
+Tazwok also supports the use of mercurial/subversion/git in WGET_URL. The syntax is:
+WGET_URL="subversion|svn://svn.mplayerhq.hu/mplayer/trunk
+An optional variable is BRANCH: it allows to specify the revision /tag/branch to use (see examples below). Where BRANCH is used, it is important that $VERSION is part of its definition.
+
+Note that the sources will be obtained through the requested tool, then packaged in .tar.lzma. The archive will be named as explained above. This means that the variable source can be used to ensure that many recipes use the same repository without creating multiple archives.
+
+First, it helps to know what revision is installed when using the package manager. Second, it allows to differentiate tazwok compressed sources. Indeed, if the archive keeps the same name, it will not be re-downloaded, which is undesirable when trying to update the package.
+
+**Examples:**
+	* Here was necessary wget: http://hg.slitaz.org/wok/rev/012847ddd0cb
+	* Tinyproxy did not report the URL of its source code is corrected: http://hg.slitaz.org/wok/rev/25967da0e1af
+	* WGET_URL now supports xpi: http://hg.slitaz.org/wok/rev/37738b3ee08f
+	* WGET_URL with a "weird" URL:  http://hg.slitaz.org/wok/rev/102de15fea8d
+	* WGET_URL using git: http://hg.slitaz.org/wok/rev/e06d60ae03eb
+	* WGET_URL using subversion: http://hg.slitaz.org/wok/rev/c4c54646489a
+	* WGET_URL using mercurial: http://hg.slitaz.org/wok/rev/756ed4b1daac
+	* It was difficult to choose how to define BRANCH and VERSION for aufs: http://hg.slitaz.org/wok/rev/67231cfc5475
+	* Here are two sources of records were in conflict, resolved by SOURCE: http://hg.slitaz.org/wok/rev/b891cba4f48e
+	* slitaz-dev-tools contains the sources for SliTaz tools that contain very little code, using SOURCE="slitaz-dev-tools" in recipes that use this deposit to avoid having duplicate tarballs: http://hg.slitaz.org/wok/rev/808826645cc2
+
+==== Exceptions dependencies cooking ====
+In some cases, no dependence cooking is installed:
+	* For recipes with WANTED
+	* For recipes without compile_rules()
+
+Note that packets may be required to obtain / decompressing the source code will still be installed if they are in DEPENDS / BUILD_DEPENDS. These are wget, mercurial, subversion, git, tar and unzip.
+
+If you do not compile_rules() but want to force the installation of all dependencies of cooking, there is a little hack:
+
+compiles_rules()
+{
+	:
+}
+
+
+**Examples:**
+	* Removal of compiles_rules() to avoid installing unnecessary dependencies Cooking: http://hg.slitaz.org/wok/rev/f579356b437f
+	* Remove a hack with fake compiles_rules was useless ... http://hg.slitaz.org/wok/rev/5b4581f8e476
+
+==== Define src/_pkg & move in the right place (hacks in the recipe) ====
+
+By default, the new sources in place tazwok $WOK/$PACKAGES/$PACKAGE-$VERSION: it renames the parent directory of sources if necessary. So far, $src was not properly defined for recipes using both SOURCE and WANTED. Many recipes implement their own solution in different ways, which is difficult to consider a standardized way and can cause compatibility problems.
+
+If tazwok detects src=/_pkg= in a recipe, it continues to use the old behavior to ensure compatibility (this produces errors in some cases). It is no longer necessary and not ideal.
+
+The hacks in the recipe source that move in the right place are no longer needed either, and can also cause problems.
+
+In conclusion, it is better to consider that $src/$_pkg are defined by default and try to rely as much as possible.
+
+** Examples: **
+	* Removing src= by Godane: http://hg.slitaz.org/wok/rev/a1c1d35d9f92
+	* src=/_pkg= can / should also be removed from WANTED: http://hg.slitaz.org/wok/rev/07adb7cbd0c8
+	* Here, an old hack was the problem: http://hg.slitaz.org/wok/rev/62f6142d9fb3
+	* Sources are now //always// placed in a sub-directory $src http://hg.slitaz.org/wok/rev/e64069568fe7
+	* Another case: call the configure script from a folder separate compilation (*-build): http://hg.slitaz.org/wok/rev/7461a0c31d62
+	* Fixed dmraid: http://hg.slitaz.org/wok/rev/f5b7e0c47763 http://hg.slitaz.org/wok/rev/59ea9409ad8a
+
+==== Set the default paths in configure: ====
+See /etc/slitaz/slitaz.conf, /etc/config.site and the new revenue model in place by New tazwok tree
+
+The new version of tazwok attempts to pass the default paths to configure using the environment variable CONFIG_SITE calling /etc/config.site, which works in most cases. Nevertheless configure scripts are specific to each source and sometimes CONFIG_SITE not be supported. For this reason, the best way to remove the definitions of paths is unnecessary to do so on a case by case, when the updated recipe, and make sure everything works.
+
+In rare cases, this new product functionality problems. It happens that some recipes that did not use the default paths used by CONFIG_SITE now, and an update function genpkg_rules() is then mandatory.
+
+** Examples: **
+	* A file or did not install properly in acl is corrected by CONFIG_SITE: http://hg.slitaz.org/wok/rev/f831ecb652a6
+	* Another example: http://hg.slitaz.org/wok/rev/259214792e30
+
+CONFIG_SITE= can be used in recipes to use a different file than the default (can be useful for packages gnome or something like that ...)
+
+==== DESTDIR=$PWD/_pkg ====
+
+DESTDIR is passed to make install using the environment variable of the same name. The new path for installation is $ WOK/$PACKAGE/install. This will remove the source folder after packaging, it does not contain any file used by a recipe in his genpkg_rules().
+
+Most recipes still use DESTDIR=$PWD/_pkg. However, if no revenue is redefining the variables src/_pkg, automatically move to the tazwok $WOK/$PACKAGE/install.
+
+In some cases, as with other variables, DESTDIR is not taken into account or the package is not installed by make. In these cases, the variable $DESTDIR is available to define the installation directory in the recipe.
+
+In rare cases, this behavior causes incompatibilities. This happens when revenues define the path to the installation folder without using src/_pkg. The solution is not to set these paths in revenue (that calling the main recipe with WANTED included), make sure the installation is done well in $WOK/$PACKAGE/install and trust the variables provided by tazwok.
+
+** Examples: **
+	* Remove _pkg= & DESTDIR= same time for this to work: http://hg.slitaz.org/wok/rev/cf088243a4a5
+	* Remove references "useless" to $src to the sources are withdrawn: http://hg.slitaz.org/wok/rev/0731792c3994 http://hg.slitaz.org/wok/rev/5d6340961543
+	* Bash does not take into account DESTDIR environment variable: http://hg.slitaz.org/wok/rev/fa7b7514e1d8
+ 	* acl attr does not include DESTDIR (in this installation the destination was still $PWD/_pkg): http://hg.slitaz.org/wok/rev/fa7b7514e1d8
+
+==== MAKEFLAGS ====
+
+MAKEFLAGS also increased to make using environment variables, and again this does not always work. In most cases, -j4 can be removed. In some cases it is necessary to use MAKEFLAGS directly to make the recipe:
+make $MAKEFLAGS
+
+Tazwok automatically sets the value for $MAKEFLAGS in the number of heart that contains the processor -j4 should be removed from all the recipes can be compiled on computers that have more resources (4 cores can use -j5)
+
+**Problems MAKEFLAGS:**
+
+So far, only recipes with-j4 compiled using the multi-threaded, whereas now all make and make install use. This behavior can cause errors. Some sources do not support multi-threaded compilation but do not disable. This is the most common problem associated with the changes explained here.
+
+//Problem in compiling://
+
+During compilation, it happens that rely on other libraries compiled with the same sources. If they are compiled at the same time, this causes an error about a missing library. In this case, we see in the compilation text that the library in question has begun to be built few lines earlier, but that this process was not finished yet. To resolve this problem, add -j1 to make. It is the most common mistake, there are other more rare that take a similar form.
+
+//Problem in installation://
+
+The characteristic of this error is that the installation stops and an error message says that it is impossible to create a folder because it already exists: a parallel process is actually creating it. In this case, add-j1 to make install.
+
+** Examples: **
+	* Several changes explained here in the recipe for gettext: http://hg.slitaz.org/wok/rev/9411655af0e2
+
+==== Variables $stuff, $wanted_stuff and $fs ====
+
+Now the variable $stuff is available and returns the record stuff in the recipe, it uses an absolute path. The variable $wanted_stuff refers to the file defined in the package stuff WANTED, if any. The variable $fs refers to the future content of the package in taz/*/fs, as before, the difference is that now $fs uses an absolute path
+
+** Examples: **
+	* A commit with several changes regarding the variable $stuff: http://hg.slitaz.org/wok/rev/be13f25e790b
+	* A correction necessary when we have made an absolute path $fs: http://hg.slitaz.org/wok/rev/8c897d2542ab
+
+==== Do not use 'exit' but 'return' ====
+
+Now when cooking several packages with a list tazwok does not call for new tazwok cook. There is only one session tazwok so that the execution is faster. If a recipe uses exit, it leaves tazwok and following list is not cooked.
+
+**Example:**
+	* Removing all exit the wok recipes: http://hg.slitaz.org/wok/rev/0b4cf0d9e1b5
+
+==== Conclusion - What to do when updating a recipe: ====
+
+	* Remove src=/_pkg= recipe and those who declare as WANTED.
+	* Remove DESTDIR=$PWD/_pkg and if it does not work, or if the means to define the installation directory is not + make DESTDIR, rather than using $ DESTDIR $PWD/_pkg.
+	* Remove the definition of default paths and see if it works, otherwise leave.
+	* Remove-j4 and see if it works; If the mutli-threaded does not work, re-activate using $MAKEFLAGS; if multi-threading causes problems, add-j1 to the right place.
+	* Remove BUILD_DEPENDS / DEPENDS redundant.
+	* Check that packages are created correctly, otherwise update the paths in genpkg_rules().
+	* Try to declare all sources of revenue in that SliTaz can be compiled without internet connection (requires to download any source before).
+	* Check that the package needed to download / extract the source code are defined in BUILD_DEPENDS.
+	* Check as EXIT is not used in the recipe.
+
+==== Some more complex cases ... ====
+
+I put them there in the end because there are already too many to be integrated:)
+The items below correspond to specific cases.
+
+== Variable COOK_OPT ==
+
+This new variable can contain options that alter the behavior of tazwok. They are useful in very special cases.
+
+**genpkg=**
+
+In the recipe PACKAGE defines a priority order for the revenue package containing WANTED="PACKAGES" (and only them!). If you include multiple packages, separate them with double points ':'. If packets are not defined in this option, they will be packaged later, in alphabetical order (default)
+
+Used in glibc: http://hg.slitaz.org/wok/file/tip/glibc/receipt
+
+**!repack_src**
+
+Disable re-compression format sources .tar.lzma.
+
+Ruby-pkgconfig used for the sources remain in gem: http://hg.slitaz.org/wok/file/tip/ruby-pkgconfig/receipt
+
+**!unpack**
+
+Prevents decompression of the archive-source in the wok.
+
+This is used by ruby-pkgconfig as well (see link above)
+
+This is the only case yet!
+
+==== Cooking the toolchain ====
+
+To cook the toolchain SliTaz, we use a temporary toolchain. Some recipes use specific rules in this step. When cooking this toolchain temporarily affected software packaged but are not directly installed in the chroot purpose built. The affected packages are listed in the variable SLITAZ_TOOLCHAIN configuration file /etc/slitaz/slitaz.conf
+
+Additional features are:
+	* Precook_tmp_toolchain() - Used only by gcc & binutils for the moment, because they are cooked twice during the preparation of the temporary toolchain.
+	* Cook_tmp_toolchain() - Used by the most packets SLITAZ_TOOLCHAIN to define how they should be compiled for the temporary toolchain. When cook_tmp_toolchain() is absent, compile_rules() is used instead. This avoids writing two identical functions. Note that in this case. ./configure does not set the default paths in the recipe, because the temporary toolchain must be able to do it via the environment variable CONFIG_SITE. Indeed, packets compiled during this stage are not installed in the usual place but in /tools.
+
+** Examples: **
+	* Binutils: http://hg.slitaz.org/wok/file/tip/binutils/receipt
+	* Gettext: http://hg.slitaz.org/wok/file/tip/gettext/receipt
+	* Bash: http://hg.slitaz.org/wok/file/tip/bash/receipt
+	* Patch does not need cook_tmp_toolchain(): http://hg.slitaz.org/wok/file/tip/patch/receipt
+	* Autoconf either: http://hg.slitaz.org/wok/file/tip/autoconf/receipt
+
+== tazwok get-src / report in recipes ==
+
+Report is a module libtaz for organizing the display commands in the terminal and create logs available including http://bb.slitaz.org interface. It can be used in recipes, as follows (that is abstract, the following examples of actual application):
+
+
+compile_rules() # Per example
+{
+	report open-bloc #compiles_rules is a step, declaring that there will substeps
+	report step "Action machin"
+		...
+	report step "Action truc"
+		.. 
+	report close-bloc #Close the open block previously
+}
+
+
+Specifically, there is one case where we use it: when using get-src tazwok PACKAGE --target=... . This command creates a new step (postponement step). We need to open a block before and after the close, as well as adding several other deferral step "..." to log and display in the terminal is correct. Each farm deferral step the previous step, if we do not open the block, get-src shut tazwok step "Executing compiles rules"
+
+Delaying closed block must be completely executed, otherwise the log/display will be broken. That's why we use { report-block closed; return 1; } return rather than alone.
+
+The practical use of this tazwok get-src is that you can unpack the sources of designated PACKAGE at target.
+
+In the examples below, observe the correlation between the delay step and displayed in the log. Observe also the correlation between tazwok get-src and the message "Checking for source tarball ..." in the log. You learn how to carry report open-bloc/closed block create a subset in genpkg_rules (named "Executing compile_rules" in the log). If it were not for open-bloc/close-bloc, the new steps would be posted to the result of "Executing compile_rules" This is not what we wanted.
+
+** Examples (recipe + log): **
+	* Linux needs patches contained in the sources of aufs, Godane took the opportunity to improve the log. Recipe: http://hg.slitaz.org/wok/file/tip/linux/receipt; log: http://bb.slitaz.org/log.php?version=cooking&package=linux
+	* Gcc uses several other sources of packages during the cooking of the temporary toolchain. Recipe: http://hg.slitaz.org/wok/file/tip/gcc/receipt; log: http://bb.slitaz.org/log.php?version=cooking&package=tmp-toolchain-gcc
+	* mingw32-gcc was corrected using this approach, it also allowed to declare all sources used. Commit: http://hg.slitaz.org/wok/rev/fd43246b4613; log: http://bb.slitaz.org/log.php?version=cooking&package=mingw32-gcc
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/devnotes/prepare-experimental.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/devnotes/prepare-experimental.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,88 @@
+====== Prepare the experimental wok ======
+
+==== Warning ====
+
+Before using the experimental wok, it's advisable to read and understand the [[en:cookbook:advancedhg|Advanced usage of Mercurial]] as the experimental wok uses MQ to handle the patch queue.
+
+Please note that the source code, wok & packages use a lot of space, don't store all of that in your RAM unless you're sure that it will run fine. If you use a live system, you can use a physical disk to store data using the boot option home=. You can also mount the disk (i.e.: on /mnt).
+
+==== Enabling Mercurial Queue ====
+
+The experimental wok is shared as patches which can't be integrated into the cooking wok for now. To use them, you need the extension MQ. So your ~/.hgrc should contain these lines:
+
+
+[extensions]
+mq =
+
+
+==== Download cooking wok & patch it ====
+
+First check that the destination disk is mounted. In the directory which contains the data, create a repository called experimental and enter in it:
+
+cd destination
+mkdir experimental
+cd experimental
+
+
+
+Download the wok:
+
+hg clone http://hg.slitaz.org/wok wok
+
+
+If you were root, enable read/write permissions to your normal account; then exit the root one:
+
+chown tux.tux -R wok
+
+
+The patches will apply well on the revisions for which they was created, but problems can appear with the other revisions. The revisions correlated to the last update of the patches can be found here: http://hg.slitaz.org/wok-experimental.
+Update the wok to the good revision:
+
+hg update -C rev
+
+
+Download experimental patches:
+
+cd .hg
+hg clone http://hg.slitaz.org/wok-experimental patches
+
+
+Apply patches:
+
+cd ..
+hg qpush -a
+
+
+==== Update the experimental wok ====
+
+Go into the wok:
+
+cd ?/wok
+
+
+Unapply patches (doesn't work if modifications are uncommitted):
+
+hg qpop-a
+
+
+Update cooking wok:
+
+hg pull
+
+
+Check the revision to use at http://hg.slitaz.org/wok-experimental and update the working directory to this revision:
+
+hg update -C rev
+
+
+Update patches repository:
+
+cd .hg/patches
+hg pull -u
+
+
+Apply the new patches:
+
+cd ../..
+hg qpush -a
+
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/devnotes/start.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/devnotes/start.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,14 @@
+====== Development Notes ======
+
+This page contains development information about the cooking version. Some pages will go into the guides or books when the next stable version is released. Others are temporary pages which coordinate development work.
+
+===== Information for users ===== 
+
+  * [[xorgserver-user|xorg-server-1.8]] - Update configuration
+
+===== Information for contributors =====
+
+  * [[xorgserver-contrib|xorg-server-1.8 ]] - Drivers pre-configuration
+  * [[en:devnotes:prepare-experimental|Prepare the experimental wok]] - Howto use the experimentals patches with MQ
+  * [[en:devnotes:ash-benchmarks|Ash benchmarks]] - How-to optimize ash scripts ?
+  * [[en:devnotes:new-tazwok-illustrated|New Tazwok]] - How the new tazwok works ?
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/devnotes/xorgserver-contrib.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/devnotes/xorgserver-contrib.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,63 @@
+====== xorg-server-1.8 ======
+
+===== Introduction =====
+
+With xorg-server-1.8, the file ///etc/X11/xorg.conf// is deprecated. Though we can actually reserve it for user modifications, it's no longer edited automatically. 
+
+The configuration files are now in ///etc/X11/xorg.conf.d//. To ensure that the users configuration will not be erased by a system upgrade, here's a suggestion of numbers and content. The configuration files are read in alphanumerical order and their names must end with .conf :
+
+  * 00 - ServerFlag
+  * 05 - ServerLayout Tweaks
+  * 10 - ServerLayout
+  * 15 - Files Tweaks
+  * 20 - Files
+  * 25 - Modules Tweaks
+  * 30 - Modules
+  * 35 - InputClass/InputDevice Tweaks
+  * 40 - InputClass/InputDevice
+  * 45 - Monitor Tweaks
+  * 50 - Monitor
+  * 55 - Device Tweaks
+  * 60 - Device
+  * 65 - Screen Tweaks
+  * 70 - Screen 
+  * 75 - Modes Tweaks
+  * 80 - Modes
+  * 85 - DRI Tweaks
+  * 90 - DRI
+  * 95 - Extension Tweaks
+  * 100 - Extension
+
+Some of the x0 sections are configured by tazx xorg-config using a template //xorg.conf// file (generated with Xorg -configure). You can find more information about this in the function [[http://hg.slitaz.org/slitaz-tools/file/ca6804d9b56b/tinyutils/tazx#l27|xorg_conf_d]] of tazx. 
+
+If you want add a configuration file to a package, please take care to use a name different from those specified by tazx or this file will be erased when booting in live mode. You can use the same number (x0) with a different name if this configuration doesn't conflict with those used by default. Otherwise, use (x-1)5 for that configuration overwriting the default one.
+
+Examples :
+
+  * [[http://hg.slitaz.org/wok/file/c29991cef110/xorg-xf86-input-evdev/stuff/40-evdev.conf|40-evedev.conf]] - Default configuration for all devices
+  * [[http://hg.slitaz.org/wok/file/c29991cef110/xorg-xf86-input-synaptics/stuff/35-synaptics.conf|35-synaptics.conf]] - Advanced configuration for touchpad devices, overwriting the default configuration for these devices
+  * hwsetup, section [[http://hg.slitaz.org/slitaz-tools/file/ca6804d9b56b/tinyutils/hwsetup#l685|nvidia]] and [[http://hg.slitaz.org/slitaz-tools/file/ca6804d9b56b/tinyutils/hwsetup#l753|ati]] - Add a file 55-DeviceTweaks.conf configuring a graphic driver other than vesa
+
+===== Configuration files list =====
+
+This avoid naming two files identically, you can use these in the ///etc/X11/xorg.conf.d/readme// for users with the 4.0 release.
+
+tazx :
+  * 10-ServerLayout.conf
+  * 20-Files.conf
+  * 30-Module.conf
+  * 40-Keyboard.conf
+  * 50-Monitor.conf
+  * 60-Device.conf
+  * 70-Screen.conf
+tazhw :
+  * 55-DeviceTweaks.conf
+xorg-xf86-input-evdev :
+  * 40-evdev.conf
+xorg-xf86-input-synaptics :
+  * 35-synaptics.conf
+
+===== TODO =====
+
+  * Improve the auto-configuration tool in tazx : some fonts and modules don't need to be loaded by default or don't exist. Some of these elements can be configured by their original package.
+  * Pre-configure some drivers to make them work out-of-the-box.
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/devnotes/xorgserver-user.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/devnotes/xorgserver-user.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,29 @@
+======= xorg-server-1.8 ======
+
+===== Upgrade Xorg configuration =====
+
+
+Upgrade Slitaz :
+# echo 'y' | tazpkg upgrade
+Backup xorg.conf :
+# mv /etc/X11/xorg.conf /etc/X11/xorg.conf-backup
+Re-configure Xorg with tazx :
+# tazx config-xorg
+
+==== User tweaks ====
+
+If you have tweaked the //xorg.conf// file, then you have two possibilities. In both cases the tweaks will be read before the default configuration and will not be erased by an upgrade :
+
+  * Put your modifications (examples) in the file ///etc/X11/xorg.conf.// This file is now reserved for users, it's the first read by Xorg when X boots.
+
+  * You put them in the correct file in the directory ///etc/X11/xorg.conf.d.// SliTaz use two files for each Xorg section : 
+          * n0-Section.conf for the default configuration and : 
+          * (n-1)5-SectionTweaks.conf for the configurations which overwrite the default one.
+
+Example :
+
+//40-evdev.conf// contains the default configuration for all devices.
+
+//35-synaptics.conf// is installed with the package xorg-input-xf86-synaptics and contains the configuration file for touchpad. It overwrites the default one (evdev).
+
+If you wish to modify this section manually, take care to rename the file with a lower number like //31-MyDevices.conf//. And don't use a file named x5 or x0 to ensure that it will not be overwritten by an upgrade.
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/forum/start.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/forum/start.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,3 @@
+====== Forum posts ======
+
+[[http://forum.slitaz.org/index.php?p=/discussion/comment/5404/#Comment_5404|How to build your own kernel modules]]
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/alsaequal.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/alsaequal.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,84 @@
+====== Alsaequal ======
+
+===== Installation (cooking only) =====
+
+First download alsaequal:
+
+# tazpkg get-install alsaequal
+
+Then create a /home/tux/.asoundrc file:
+
+
+ctl.equal {
+  type equal;
+}
+
+pcm.plugequal {
+  type equal;
+  # Modify the line below if you don't
+  # want to use sound card 0.
+  # slave.pcm "plughw:0,0";
+  # or if you want to use with multiple applications output to dmix
+  slave.pcm "plug:dmix"
+}
+
+pcm.equal {
+  # Or if you want the equalizer to be your
+  # default soundcard uncomment the following
+  # line and comment the above line.
+# pcm.!default {
+  type plug;
+  slave.pcm plugequal;
+}
+
+
+===== mpg123 =====
+
+Change (cd) into your music directory and then run:
+
+$ mpg123 -a equal *
+
+Or
+
+$ mpg123 -a equal track1
+
+Now you should be able to open up a separate terminal and use:
+
+$ alsamixer -D equal
+
+===== mpd =====
+
+Just edit the audio_output section of your /etc/mpd.conf:
+
+
+audio_output {
+	type		"alsa"
+	name		"equal"
+	device		"plug:plugequal"
+##	format		"44100:16:2"	# optional
+##	mixer_device	"default"	# optional
+##	mixer_control	"PCM"		# optional
+##	mixer_index	"0"		# optional
+}
+
+
+And start/restart mpd and you should be able to use //$ alsamixer -D equal//
+
+===== moc =====
+
+Copy the config.example file in /usr/share/doc/moc to your ~/.moc folder:
+
+$ cp /usr/share/doc/moc/config.example ~/.moc/config
+
+Then change the alsa output device line to: 
+
+
+# ALSA output device
+AlsaDevice    = equal
+		
+
+And then start/restart moc.
+
+===== References =====
+
+http://www.thedigitalmachine.net/alsaequal.html
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/bluetooth.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/bluetooth.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,131 @@
+====== Bluetooth ======
+
+===== Introduction =====
+
+This guide will help you to configure bluetooth, e.g. to use your phone as a modem.
+Do following steps as root.
+First of all you must install Slitaz packages related to bluetooth:
+  # tazpkg get-install bluez
+  # tazpkg get-install linux-bluetooth
+The first package contains the Official Linux Bluetooth protocol stack www.bluez.org and the second contains the kernel modules related to bluetooth.
+Now you can launch the bluetooth daemon:
+  # bluetoothd
+And load the module required by your local bluetooth device, this is very likely btusb:
+  # modprobe btusb
+If btusb is the module you need the command "hcitool dev" to show you the local device address:
+  root@slitaz:/home/tux# hcitool dev
+  Devices:
+          hci0    00:02:72:xx:xx:xx
+If the command "hcitool dev" does not show you any hci* device you must detect which module you need and repeat the previous step until you have a hci* device.
+Now that you have hci* you can run the "hcitool scan" command to show you if there is any discoverable device nearby.
+So if you are searching, e.g. your phone, remember to put it in discoverable mode:
+  root@slitaz:/home/tux# hcitool scan
+  Scanning ...
+          00:18:C5:xx:xx:xx       Nokia 6151
+  root@slitaz:/home/tux#
+Now you can pair your locale device with your remote device. You use bluez-simple-agent to do that.
+
+If you want to start the pairing from the remote device you need to put your local device in discoverable mode:
+  # hciconfig hci0 piscan
+
+Now launch bluez-simple-agent, start the pairing from the remote device and wait for bluez-simple-agent to ask you for the pin code needed to pair.
+This code will be the same one you typed on the phone. When you are done you need to kill bluez-simple-agent with Ctrl-c:
+  root@slitaz:/home/tux# hciconfig hci0 piscan
+  root@slitaz:/home/tux# bluez-simple-agent
+  Agent registered
+  RequestPinCode (/org/bluez/2944/hci0/dev_00_18_C5_xx_xx_xx)
+  Enter PIN Code: 1234
+  ^CTraceback (most recent call last):
+    File "/usr/bin/bluez-simple-agent", line 113, in 
+      mainloop.run()
+  KeyboardInterrupt
+  root@slitaz:/home/tux#
+Put your local device back in undiscoverable mode:
+  # hciconfig hci0 pscan
+
+If you want to start the pairing from your local device you can do it using bluez-simple-agent with the hci* of your local device and the address of the device you discovered with "hcitool scan". In this case you will choose the pin in bluez-simple-agent and type the same pin on the remote device:
+  root@slitaz:/home/tux# bluez-simple-agent hci0 00:18:C5:xx:xx:xx
+  RequestPinCode (/org/bluez/3078/hci0/dev_00_18_C5_xx_xx_xx)
+  Enter PIN Code: 1234
+  Release
+  New device (/org/bluez/3078/hci0/dev_00_18_C5_xx_xx_xx)
+  root@slitaz:/home/tux# 
+Be fast because bluez-simple-agent has a timeout which I don't know how to set (suggestions?)
+
+===== Use a phone as a modem =====
+
+Now you have your two devices paired, i will go on with the phone as a modem example, I don't have other experiences with bluetooth devices.
+To use your phone as a modem you need the rfcomm module. At the moment I am writing this guide the rfcomm module of Slitaz is compiled without tty support. You can check if this is the case with the following commands:
+  root@slitaz:/home/tux# zcat /proc/config.gz | grep RFCOMM                    
+  CONFIG_BT_RFCOMM=m
+  # CONFIG_BT_RFCOMM_TTY is not set
+  root@slitaz:/home/tux#
+If CONFIG_BT_RFCOMM_TTY is not =y you must recompile the module with tty support. Install linux-source:
+  # tazpkg get-install linux-source
+cd in /usr/src/linux-`uname -r`/ and give this command:
+  # make CONFIG_BT_RFCOMM=m CONFIG_BT_RFCOMM_TTY=y M=net/bluetooth/rfcomm
+This will build only the rfcomm module with tty support. You will find it in /usr/src/linux-`uname -r`/net/bluetooth/rfcomm/rfcomm.ko.
+Now you can delete the old rfcomm module and replace it with your module:
+  # rm /lib/modules/`uname -r`/kernel/net/bluetooth/rfcomm/rfcomm.ko.gz
+  # cp /usr/src/linux-`uname -r`/net/bluetooth/rfcomm/rfcomm.ko /lib/modules/`uname -r`/kernel/net/bluetooth/rfcomm/ 
+  # depmod -a
+Now that we have a working rfcomm module we must detect the channel where the phone dialup service is listening:
+  # sdptool browse 00:18:C5:xx:xx:xx
+Where 00:18:C5:xx:xx:xx is the address of your phone, it will give a list with the services available on your phone. The one you are looking for is Dial-up networking or DUN:
+  Service Name: Dial-up networking
+  Service RecHandle: 0x10000
+  Service Class ID List:
+    "Dialup Networking" (0x1103)
+    "Generic Networking" (0x1201)
+  Protocol Descriptor List:
+    "L2CAP" (0x0100)
+    "RFCOMM" (0x0003)
+      Channel: 1
+  Language Base Attr List:
+    code_ISO639: 0x656e
+    encoding:    0x6a
+    base_offset: 0x100
+  Profile Descriptor List:
+    "Dialup Networking" (0x1103)
+      Version: 0x0100
+      
+===== rfcomm.conf =====
+
+As you can see it is listening on channel 1, so you edit ///etc/bluetooth/rfcomm.conf// this way:
+
+  #
+  # RFCOMM configuration file.
+  #
+  rfcomm0 {
+  #       # Automatically bind the device at startup
+          bind yes;
+  #
+  #       # Bluetooth address of the device
+          device 00:18:C5:xx:xx:xx;
+  #
+  #       # RFCOMM channel for the connection
+          channel 1;
+  #
+  #       # Description of the connection
+  #       comment "Example Bluetooth device";
+  }
+
+Now with:
+  # modprobe rfcomm
+  # rfcomm bind all
+You can use /dev/rfcomm0 as a modem in a wvdial script.
+You may want to check this guide http://doc.slitaz.org/en:guides:dialup
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Add tazhw setup bluetooth ; Please create "sections" for toc|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/boottime.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/boottime.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,40 @@
+====== Boot time ======
+
+SliTaz boots fast! But most likely you haven't turned super fast boot on yet. To do this, just edit your ///etc/rcS.conf// :
+ FAST_BOOT_X="yes" 
+
+Remove dbus, hald and slim from the RUN_DAEMONS array. That's all. Note, on some machines, FAST_BOOT_X may not boot properly. However, if Xvesa/Xorg works after you enable this feature, it's safe to leave it on. 
+
+Now, how do you measure the boot time? SliTaz logs time that rcS scripts take to run in the ///var/log/boot-time// file. In my case, it shows 5 secs. 
+
+But, how do you graph your full boot process (including the kernel-boot time)? Its quite easy on SliTaz. Just do and install the following:
+
+ # tazpkg get-install pybootchartgui 
+
+Pybootchartgui will then create a chart automatically in ///var/log//. 
+
+Now, just edit your //menu.lst// file for grub and add init=/sbin/bootchartd. In my case, it's like this:
+
+
+title slitaz with bootchart
+root (hd0,8)
+kernel /boot/vmlinuz-2.6.30.6-slitaz root=/dev/sda9 init=/sbin/bootchartd quiet
+
+
+Here's my boot chart with WPA2 wifi (under 10 secs boot time on a laptop with hard disk). This is out-of-the-box!!!:
+
+{{ :en:guides:image:bootchart.png?100 |My bootchart}}
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/bugs.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/bugs.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,19 @@
+====== BUGS ======
+
+The problems listed in this page refer to the Slitaz 3.0 environment.
+
+===== Burning a CD with Burnbox =====
+
+To burn a CD, you have to be root (it will NOT work from your default TUX account, even if TUX has been added to the cdrom group). 
+
+In Burnbox; enclose the file and folder names between quotes if they contain a space (eg "My Documents"), otherwise it will fail to find the document.
+
+===== Abiword =====
+
+With AbiWord you MUST install glibc-locale too, it was forgotten as a dependency, but it is needed for AbiWord to work properly.
+
+===== Chat entry of the Internet menu =====
+
+This should install pidgin and skype. Practically it has sometimes (but not always) installed pidgin, and always failed to install Skype.
+Install Pigin and Skype (well, get-skype) from the package manager.
+ 
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/chroot.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/chroot.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,96 @@
+====== Chroot =======
+
+This guide explain how to setup a chroot to cook packages in a separate environment. The chroot can be built on a USB or HDD device to save RAM when using a live session. There is also a script which removes any packages installed during cooking on exit in order to keep the chroot light and also checks the build_depends.
+
+===== With Tazdev =====
+
+Over time the SliTaz developers created tools for the automation of various tasks. The slitaz-dev-tools package provides the tazdev utility and its configuration file /etc/slitaz/tazdev.conf; it can create a chroot to use:
+
+
+# tazpkg get-install slitaz-dev-tools
+# tazdev gen-chroot
+# tazdev chroot
+
+
+By default the chroot is created in ///home/slitaz/cooking/chroot// and is slitaz-based. For more info and available commands you can use 'tazdev usage' and/or take a look at the configuration file.
+
+===== Create the chroot =====
+
+#!/bin/sh
+mkdir /home/chroot
+# You can mount a device to /home/chroot
+# with mountbox or mount
+tazpkg get-install busybox --root="/home/chroot"
+echo "No" | tazpkg get-install bash --root="/home/chroot"
+tazpkg get-install slitaz-toolchain --root="/home/chroot"
+tazpkg get-install tazwok --root="/home/chroot"
+tazpkg get-install tazpkg --root="/home/chroot"
+tazpkg get-install lzma --root="/home/chroot"
+mkdir /home/chroot/home/slitaz
+
+Note, you can keep these lines in a script file if needed. Just add #!/bin/sh to the first line and make executable with:
+# chmod +x script_file
+
+===== Add a script file to automate some actions =====
+
+# cat > /home/chroot/chroot_script.sh << "EOF"
+
+#!/bin/sh
+/bin/sh --login
+for pkg in $(cat /var/log/tazpkg.log | grep -v Removed | sed 's/\(.*\)\(- Installed - \)\(.*\)\( (.*\)/\3/'); do
+	echo "y" | tazpkg remove $pkg
+done
+rm /var/log/tazpkg.log
+
+EOF
+
+# chmod +x "/home/chroot/chroot_script.sh"
+
+Note, /bin/sh --login logs you into the chrooted environment. The commands after that auto-remove any packages added when cooking on exit. You can hack this file to execute various automated actions when entering and exiting the chroot.
+
+===== Add a script to mount and umount chroot =====
+
+# cat > /usr/bin/tazchroot << "EOF"
+
+#!/bin/sh
+cat /etc/resolv.conf > /home/chroot/etc/resolv.conf
+if [ ! -d "/home/chroot/proc/1" ]; then
+	echo "Mounting virtual filesystems..."
+	mount -t proc proc /home/chroot/proc
+	mount -t sysfs sysfs /home/chroot/sys
+	mount -t devpts devpts /home/chroot/dev/pts
+	mount -t tmpfs shm /home/chroot/dev/shm
+	mount /home/slitaz /home/chroot/home/slitaz
+	chroot /home/chroot ./chroot_script.sh
+	until [ "$ps" = "2" ]; do
+		echo "Waiting for the end of all other chroot processes..."
+		ps=$(ps | grep `basename $0` | grep -v grep | grep -v basename | wc -l)
+		sleep 1
+	done
+	umount /home/chroot/home/slitaz
+	umount /home/chroot/dev/shm
+	umount /home/chroot/dev/pts
+	umount /home/chroot/sys
+	umount /home/chroot/proc
+else
+	echo "The chroot is already mounted"
+fi
+EOF
+
+# chmod +x /usr/bin/tazchroot
+
+Note, this script mounts ///home/slitaz// in your chroot, so you can use tazwok as if it was in your normal environment.
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/conspy.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/conspy.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,107 @@
+====== Conspy : tiny screen or VNC ======
+
+Slitaz core provides the 10Kb conspy to get remote control of Linux virtual consoles. See http://ace-host.stuart.id.au/russell/files/conspy/
+
+Slitaz opens 6 virtual consoles which you can access with Ctrl-Alt-F1 to Ctrl-Alt-F6. You can connect to console 1 with //conspy 1// and console n with //conspy n// or the current active console with //conspy// (root user only).
+
+To exit from conspy (and the virtual console) press the escape key three times in quick succession.
+
+===== Conspy as screen (session manager) =====
+
+Linux supports up to 63 virtual consoles. You can have up to 62 (63 - X11 on console 7) sessions. Six sessions are already opened by Slitaz.
+You can open a new console / new session (say console 28) with //openvt -c 28 /bin/login// or //openvt -c 28 /bin/ash//.
+You can free this virtual console with //deallocvt 28//.
+
+Example:
+
+home$ ssh tux@slitazbox
+box$ su
+box# openvt -c 28 /bin/ash
+box# conspy 28
+# some commands
+...
+# 
+box# exit
+box$ exit
+
+Later:
+
+home$ ssh tux@slitazbox
+box$ su
+box# conspy 28
+# more commands
+...
+#  
+box# exit
+box$ exit
+
+To close the session:
+
+home$ ssh tux@slitazbox
+box$ su
+box# conspy 28
+# exit
+
+box# deallocvt 28
+box# exit
+box$ exit
+
+If you prefer to use screen, see http://www.gnu.org/software/screen:
+
+# tazpkg get-install screen
+$ screen -S MySession
+
+
+===== Conspy as VNC (shared console) =====
+
+You can share a virtual console between two or more users.
+Say RemoteUser wants to show some commands to SlitazUser using SlitazBox.
+RemoteUser selects SlitazUser's console with //chvt//:
+
+home$ ssh SlitazBox
+SlitazBox$ su
+SlitazBox# chvt 1
+SlitazBox# conspy 1
+
+Now both users show the same terminal. A third user can do //conspy 1// too.
+
+If you prefer to share the X11 display, install x11vnc (VNC server) and x11vnc-extra (java VNC client) see http://www.karlrunge.com/x11vnc/:
+
+SlitazBox# tazpkg get-install x11vnc
+SlitazBox# tazpkg get-install x11vnc-extra
+SlitazBox# /etc/init.d/x11vnc start
+
+
+home$ su
+home# get-java-jre
+home# exit
+home$ firefox http://SlitazBox:5800/ultrasigned.vnc
+
+
+===== Conspy and slow connections =====
+
+Launch a very verbose command into a conspy and the output is displayed at full speed in the virtual console what ever your connection speed to the remote box is, even if your connection is broken. 
+===== Conspy and Busybox =====
+
+Conspy is a busybox applet since busybox 1.17.0. It adds 2.5Kb to busybox, has better terminal support and supports some new options:
+  * -c to create missing devices (/dev/vcsaXX and /dev/ttyXX)
+  * -d for screen shot# conspy -d 28 > screen28.txt
+  * -s to launch a shell# conspy -cs 28 (no more openvt)
+  * -x COL -y LINE upper left corner position
+  * -f follow cursor with automatic scrollings
+
+The conspy applet is enabled in the busybox package. The conspy package is no longer more useful than the recent busybox.
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/contributor.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/contributor.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,68 @@
+====== Contributing to SliTaz ======
+
+There are so many ways you can help out with the SliTaz community. If you have a little free time, anything from artwork to package testing would be greatly appreciated!
+
+Post a quick message to the forum or mailing list if you're unsure about anything. We don't bite!
+
+We have a [[http://scn.slitaz.org/|Community Network]] where you can write blog posts, share wallpapers and images, and more. We encourage anyone that contributes to SliTaz to use this platform to show off their hard work!
+
+\\
+
+===== Developers & Hackers =====
+
+=== Packaging ===
+
+If you are comfortable with the Linux compiling process (//configure, make, make install//), you can help by creating SliTaz packages. We have an automated tool to build packages from source called [[http://doc.slitaz.org/en:cookbook:wok|Tazwok]]. All SliTaz packages contain a [[en:cookbook:receipt|receipt]] - a text file where you control the building process using some variables and functions. You can browse the [[http://hg.slitaz.org/wok|wok]] to see some receipts and understand how they work. Please take time to read the [[en:cookbook:devcorner|Developer's]] page beforehand and practice locally with some new or existing packages.
+
+When you feel ready to start cooking, read the [[http://labs.slitaz.org/wiki/13/Pkgscooklist|packages cooklist]], pick one and test. You can submit your receipts to the Mailing List or contact a SliTaz dev, so that we can review the work and give you access to the repos.
+
+=== Package Testing and Debugging ===
+
+You can help SliTaz by testing packages and reporting bugs on the [[http://labs.slitaz.org/issues|Labs Issue Tracker]]. We have some [[http://labs.slitaz.org/wiki/packages|Package Testing Guidelines]]. You can use the testing project on the Labs, the forum or the mailing list to report any missing dependencies, unexpected package behavior, or wrong configurations, etc. 
+
+\\
+
+===== Writers & Translators =====
+
+Take a look at the [[:guidelines| SliTaz Documentation Guidelines]], pick your page and go! At this stage, we just need solid contributions which will then be reviewed and updated. We're undergoing a [[http://listengine.tuxfamily.org/lists.tuxfamily.org/slitaz/2010/04/msg00063.html|Summer of Documentation]], in which we're concentrating on all the docs. You'll be in good company.
+
+There's many areas in which you can help:
+
+  * **Are you experienced with SliTaz?**
+Go for the Guides. They take users through a process and range from customising your desktop to getting networking set-up. If you've had success with a procedure or feel one could be improved, this is the place for you!
+
+  * **Are you a general Linux user?**
+Take a look at the Handbook. A lot of general introduction to SliTaz, Linux or available software can be written there. Some people find it difficult to write technically, others struggle with more generically informative writing. Both are needed, in describing the topic and scope before brief instructions.
+
+  * **Do you speak non-English?**
+Translations are very important to the global audience SliTaz attracts. We need speakers of the above languages to ensure non-English readers experience better translations than automated services can provide! Those are the locales supported by the SliTaz system. We are aiming to add more in the future -- if you can help, please do!
+
+\\
+
+===== Artists & Designers =====
+
+[[http://community.slitaz.org/image/tid/2|Wallpapers]] make a huge impact on the first impression users receive. Some reviews barely comment further on artwork than the wallpaper!
+
+\\
+
+===== PR & Journalism =====
+
+//(Could we put together some blurbs or short pieces of writing for the press & community? Maybe contacts for them?)//
+
+\\
+
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Low  |
+|Review| Major Updates FIXME  |
+|Priority| High |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly, e.g.,|
+|::: | [[en:guides:start | Add link]]|
+|::: | Add new rows like this ;-)  |
+
+\\
+----
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/cpu-frequency.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/cpu-frequency.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,93 @@
+======= CPU Frequency Scaling =======
+
+==== Introduction ====
+
+To reduce power consumption is not only essential for portable computers: it is also essential to use it on desktop machines to reduce unnecessary CO2 emissions. You can save power by turning off not needed hardware components like WiFi, Bluetooth, etc., switching off or reducing the monitor backlight, spinning down HDDs and controlling the CPU frequency. 
+
+CPU frequency scaling is built into the 2.6 kernel and available; but because Slitaz is very small and light, you have to install some additional tools and set it up by yourself.
+
+==== Installation ====
+
+Install linux-cpufreq, linux-acpi, cpufrequtils and optional powertop (for easy controlling) - cpufrequtils and powertop we have to take from cooking, because cpufrequtils does not exist in 3.0 and powertop is buggy.
+
+# tazpkg get-install linux-cpufreq
+# tazpkg get-install linux-acpi,
+# wget http://mirror.slitaz.org/packages/cooking/cpufrequtils-008.tazpkg
+# wget http://mirror.slitaz.org/packages/cooking/powertop-1.13.tazpkg
+# tazpkg install cpufrequtils-008.tazpkg
+# tazpkg install powertop-1.13.tazpkg
+
+
+==== Cpu driver ====
+
+You have to load the correct CPU kernel driver for your CPU - if you don't know, which CPU is in your PC you can get it from:
+
+ $ cat /proc/cpuinfo
+
+Depending on the CPU, load one of the following modules - if you choose the wrong driver, you will get an error message, the module is not loaded and nothing goes wrong. 
+
+Generic ACPI P-States based driver:
+ # modprobe acpi-cpufreq
+AMD mobile K6-2/3+ PowerNow!:
+ # modprobe powernow-k6
+AMD mobile Athlon PowerNow!:
+ # powernow-k7
+AMD Cool&Quiet PowerNow!(up to AMD "K10" CPU):
+ # modprobe powernow-k8
+Intel SpeedStep using the SMI BIOS interface:
+ # modprobe speedstep-smi
+Intel SpeedStep on ICH-based chipsets:
+ # speedstep-ich
+Intel Enhanced SpeedStep (deprecated - use acpi-cpufreq):
+ # modprobe speedstep-centrino
+Intel Pentium4/Xeon - The kernel documentation says "This adds the CPUFreq driver for Intel Pentium 4 / XEON processors.  When enabled it will lower CPU temperature by skipping clocks. This driver should be only used in exceptional circumstances when very low power is needed because it causes severe slowdowns and noticeable latencies.  Normally Speedstep should be used instead." - the p4-clockmod supports only performance and powersave governors (due to the long transition latency of the module itself):
+ # modprobe p4-clockmod
+NatSemi Geode GX / Cyrix MediaGXm:
+ # modprobe gx-suspmod
+Transmeta Crusoe / Efficeon LongRun:
+ # modprobe longrun
+VIA Cyrix Longhaul:
+ # /sbin/modprobe longhaul
+nForce2 FSB changing cpufreq driver:
+ # modprobe cpufreq-nforce2
+Enhanced PowerSaver driver for VIA C7 CPUs:
+  # modprobe e_powersaver
+
+==== Scaling governors ====
+
+Governors can be thought of as pre-configured power schemes for the CPU. 
+
+Available governors:
+
+**cpufreq_performance (default in SliTaz)** \\
+The performance governor is built into the kernel and runs the CPU(s) at maximum clock speed 
+
+**cpufreq_ondemand (also built into the kernel)** \\ 
+Dynamically increases/decreases the CPU(s) clock speed based on system load 
+
+**cpufreq_conservative** \\ 
+Similar to ondemand, but more conservative (clock speed changes are more graceful) 
+
+**cpufreq_powersave** \\ 
+Runs the CPU at minimum speed 
+
+**cpufreq_userspace** \\ 
+Manually configured clock speeds by user 
+
+The built in governors must not be loaded - the others must be loaded with modprobe - you may load as many governors as desired (only one will be active at any given time). 
+
+Which poses the question, which governor saves most energy? The Powersave governor will only save you power if you're playing 3D games (it does not save power because application process completion times are prolonged at the lower processor frequency and the system does not enter a deep C-state. The greatest power savings occur at idle in deeper C-states) and the performance governor will basically never give you extra performance. Don't use them - therefore I am not happy that the performance governor is used by default in SliTaz. So you might choose between ondemand and conservative, which is a matter of taste.
+
+The userspace governor is necessary for third party applications - like cpupowerd http://www.themaxer.com/index.php?option=com_content&view=article&id=86:undervolting-your-cpu&catid=41:nas&Itemid=81 - unfortunately it does not work in SliTaz, because the kernel config for CONFIG_X86_MSR is not set.
+
+==== Select the governor ====
+
+At this point everything is prepared but no active governor selected - so no power saving yet.
+
+Use the 'cpufreq-set' command to activate one of the governors - for example:
+
+ # cpufreq-set -g ondemand
+
+Please note, if you have a dual-core or multiple-core CPU, you must explicitly specify the CPU. There are CPUs where each core can run with different settings! Example for a dual-core CPU:
+
+ # cpufreq-set -c 0 -c 1 -g conservative
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/cricket-a600.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/cricket-a600.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,111 @@
+====== Setting Up The Cricket A600 Broadband Modem ======
+
+===== Introduction =====
+
+First thing you need to do is download wvdial and all it's dependencies. It will do that automatically. From terminal as root:
+ # tazpkg get-install wvdial
+
+Download this:[[http://people.slitaz.org/~jozee/packages/3G_modem/usb_modeswitch-1.0.5.tazpkg|Jozee's USB_Modeswitch]] Then from terminal as root install it:
+ # tazpkg install /path/to/usb_modeswitch-1.0.5.tazpkg
+/path/to is where you downloaded it to. So you will need to adjust the above.
+
+Make a script called flipflop.sh You can place it anywhere but I am going to use where I have it as an example:
+///home/tux/scripts///
+
+If you use another name besides "tux" then adjust it accordingly. Now open up flipflop.sh with your prefered editor. Put the following in it and save the file:
+
+/usr/sbin/usb_modeswitch
+sleep 15
+usb_modeswitch -v 0x1f28 -p 0x0020 -R 1
+
+From terminal we need to chmod it so you can use the script: 
+ # chmod a+x /home/tux/scripts/flipflop.sh
+Again if you have it saved somewhere else then adjust accordingly. Sorry to repeat that lol.
+
+===== wvdial.conf =====
+
+We have now installed all that we need to install. There are just a few more steps involved. We need to edit wvdial.conf . As root from terminal enter this:
+ # leafpad /etc/wvdial.conf
+In wvdial.conf we need to make it look like this:
+
+[Dialer Defaults]
+Modem = /dev/ttyACM0
+Baud = 460800
+Stupid Mode = 1
+Auto DNS = 1
+Init1 = ATZ
+Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
+ISDN = 0
+Modem Type = USB Modem
+Phone = #777
+FlowControl = Hardware (CRTSCTS)
+Dial Command = ATDT
+Username = Your Cricket Number Goes Here.
+Password = Cricket
+
+
+Where it says "Your Cricket Number Goes Here" replace that with your cricket number. Your cricket number should be on your monthly bill if you don't know what it is. Once it is done save the file.
+
+Now again as root in terminal issue this command:
+ # /home/tux/scripts/flipflop.sh
+
+You should get something like this below:
+
+Looking for target devices ...
+ No devices in target mode or class found
+Looking for default devices ...
+ Found default devices (1)
+ Found a default device NOT in target class mode
+Accessing device 003 on bus 002 ...
+Using endpoints 0x08 (out) and 0x87 (in)
+Inquiring device details; driver will be detached ...
+Looking for active driver ...
+ OK, driver found ("dummy")
+ OK, driver "dummy" detached
+
+Received inquiry data (detailed identification)
+-------------------------
+  Vendor String: Cricket 
+   Model String: T-Flash Disk    
+Revision String: 2.31
+-------------------------
+
+Device description data (identification)
+-------------------------
+Manufacturer: Cal-comp E&CC Limited 
+     Product: USB Micro SD Storage
+  Serial No.: XXXXXXXXXXXXXXX
+-------------------------
+Setting up communication with interface 0 ...
+Trying to send the message to endpoint 0x08 ...
+ OK, message successfully sent
+ Device is gone, skipping any further commands
+-> Run lsusb to note any changes. Bye.
+
+
+Looking for target devices ...
+ No devices in target mode or class found
+Looking for default devices ...
+ No default device found. Is it connected? Bye.
+
+tux@slitaz:~$
+
+
+It looks like it totally failed but it didn't. It just doesn't know what the driver is. Again from root execute this command:
+ # modprobe cdc_acm
+That should be the last time you have to enter that command. We will now add it to to the LOAD_MODULES line in /etc/rcS.conf to load at boot.
+
+===== rcS.conf =====
+
+From terminal as root:
+ # leafpad /etc/rcS.conf
+Go down to the following line:
+LOAD_MODULES="snd_intel8x0 yenta_socket rtc agpgart intel-agp"
+Add this to the line: "cdc_acm" It should now look like this:
+LOAD_MODULES="snd_intel8x0 yenta_socket rtc cdc_acm agpgart intel-agp"
+Save it and exit.
+
+We are almost done. From terminal as root again give this command:
+  # wvdial
+
+It should now dial and connect. Do not close the terminal or it will disconnect. Everytime you poweroff or unplug the modem you have to do the flipflop.sh like I showed you above. If you just reboot your computer you don't have to do the flipflop.sh. Good Luck 
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/dialup.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/dialup.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,150 @@
+====== 3G-UMTS =======
+
+The # sign means that you do this command as root on your console:
+
+===== Automatic Installation =====
+
+The new hwsetup in SliTaz 3.0 now adds automatic installation for 3G (still in trial version).
+
+# tazhw setup 3g-modem
+
+Now open the wvdial box by typing y, enter your data (as described in wvdial.conf), save the configuration (if you don't save you risk breaking your pin), dial the pin (you have to do this only once you plug in your modem), then start dialing and you should be connected.
+
+===== Manual Installation =====
+
+
+# tazpkg get-install wvdial
+# tazpkg get-install linux-dialup 
+
+
+You have to bring down your network, otherwise you will have a route problem:
+
+
+# ifconfig eth0 down
+# ifconfig eth1 down
+
+
+You have to switch on the modem with:
+
+
+# modprobe option  (Huawei E220, E160g, Venus-VT12)
+
+
+Please help update which modem or phone is using which module using the forum post: http://labs.slitaz.org/issues/show/149. You will find if your modem is supported by linux-dialup.
+
+There is an extra guide for the [[http://doc.slitaz.org/en-guides:cricket-a600|Cricket-a600]]
+
+For automatization load the module at startup with your Slitaz Control Box.
+
+===== wvdial.conf =====
+
+Check the modem if it is /dev/ttyUSB* or /dev/ttyACM* (e.g. with #dmesg) and edit your wvdial.conf (here as an example):
+
+
+# leafpad /etc/wvdial.conf
+
+
+
+[Dialer pin]
+Modem = /dev/ttyUSB0
+Init1 = AT+CPIN=1234...................,.....!!here's your pin!!
+
+[Dialer umts]
+Modem = /dev/ttyUSB0
+ISDN = off
+Modem Type = USB Modem
+Baud = 460800
+Init = ATZ
+Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
+Dial Prefix =
+Dial Attempts = 1
+Dial Command = ATM1L3DT
+Ask Password = off
+Auto Reconnect = off
+Abort on Busy = off
+Carrier Check = on
+Check Def Route = on
+Abort on No Dialtone = on
+Stupid Mode = off
+Idle Seconds = 0
+Init3 = AT+CGDCONT=1,"IP","drei.at".....!!here's your string!!
+Username = drei.at...........................!!here's your Usern!!
+Password = drei.at...........................!!here's your Passw!!
+Phone = *99#.................................!!here's your Phone!!
+
+
+All the needed data can be found here:
+
+Austria, Germany,Switzerland: http://linux.frankenberger.at/Huawei_E220_Daten.html
+
+World:http://www.flexispy.com/Mobile%20APN%20Setting%20to%20use%20GPRS.htm
+
+But you can search the net with the name of your provider and wvdial.conf and I think you will need to.
+
+To connect do:
+
+
+# wvdial pin
+# wvdial umts
+
+
+You can put the pin also in Dialer umts, but I use my modem most of the time on the train, and you would get an error when you reconnect (when the connection breaks) - so use wvdial pin only the first time you plug in the modem.
+
+The only thing thats left is to put the DNS in resolv.conf (you will find the DNS in the two lists with all the data).
+
+
+# leafpad /etc/resolv.conf
+
+
+
+nameserver 213.94.78.16........................!!here's your DNS!!
+
+
+If you want to dial out as user - add yourself to the group "dialout" (cat /etc/group) and set the permissions for wvdial and wvdial.conf.
+
+For automatization you can put a script in /usr/local/bin called umts-connect (executable)! From here it's not proved, because I connect from the console, but it should work like this!
+
+
+#! /bin/bash
+ifconfig eth0 down
+ifconfig eth1 down
+wvdial pin
+wvdial umts
+
+
+But dont reconnect with this.
+
+===== Desktop entry =====
+
+You can also put a desktop entry in /usr/share/applications with the name umts.desktop 
+
+
+[Desktop Entry]
+Encoding=UTF8
+Name=UMTS connection
+Name[de]=UMTS-Verbindung
+Comment=UMTS-Verbindung
+Type=Application
+Exec=/usr/local/bin/umts-connect
+Icon=/usr/share/icons/.................whatever you want
+Categories=Application;Network;
+
+
+Please check Exec=/usr/local/bin/umts-connect for permissions.
+
+Here is the forum post about this: http://forum.slitaz.org/index.php/discussion/comment/440/#Comment_440
+
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/dvd.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/dvd.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,79 @@
+====== All Slitaz resources on one DVD ======
+
+A bootable DVD image of all available packages version is generated every day. See http://www.slitaz.org/en/get/ . Both cooking or stable versions are built; they contain:
+
+    * a Slitaz boot
+    * a copy of the website
+    * a snapshot of the wok
+    * all official packages
+
+It is designed to be used without an internet connection.
+
+===== Hybrid ISO =====
+
+The ISO image should be burned onto a DVD using:
+
+# wodim -v dev=/dev/dvd packages-cooking.iso
+
+It can also be written onto a USB key (say the key is /dev/usbkey). USE WITH CAUTION this will erase all your data.
+
+# dd if=packages-cooking.iso of=/dev/usbkey
+
+After writing the USB key, you can create partitions to get back the remaining storage.
+
+# fdisk /dev/usbkey
+
+The USB key is bootable. If your BIOS doesn't support USB boot, you can boot plop from http://www.slitaz.org/en/get/#floppy floppy.
+
+===== Burnable on CDROM =====
+
+The files on the ISO image are ordered in 5 groups:
+
+    - the boot files
+    - the loram boot files
+    - the website
+    - the wok
+    - the packages
+
+The four first groups fit in the first 100-200Mb of the ISO image. If you don't need the packages, you can burn it onto a mini-cdrom (8cm/210Mb)
+
+# wodim -v dev=/dev/cdrom packages-cooking.iso
+
+The packages are stored in alphabetical order. 915resolution should likely be present but zsh surely not. The directories are stored at the beginning of the image and are always present. If you try to load a non-present package (zsh) you will get an I/O error.
+
+===== Dual boot =====
+
+Both core and loram (loram-cdrom to be exact) boot files are stored in the ISO image. The default boot entry (slitaz) will select which to start according to your RAM size. You can force the choice with //core// or //loram// keyword:
+
+boot: loram screen=1280x1024
+
+With core boot you can:
+
+    * unmount the DVD (umount /cdrom)
+    * test (install) packages in RAM
+
+You can't do that with loram boot because it has /usr mounted read-only from the DVD. You can install slitaz on a hard disk with both boot files.
+
+===== Auto install =====
+
+During boot the following is performed:
+
+    * the DVD is mounted in /cdrom, the wok is onto /home/slitaz/wok
+    * a pseudo tazpkg recharge links packages from the DVD
+    * the slitaz web site is installed in file:///cdrom/website/index.html//
+
+Note: USB key users should read USB key instead of DVD
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/faq-dependency.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/faq-dependency.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,29 @@
+
+====== An Application Cannot Find Libraries/Files ======
+
+===== Symptoms =====
+
+  *  When run in a Terminal, an application fails with the message:
+ [name]: error while loading shared libraries: [library].so.*: cannot open shared object file: No such file or directory
+
+===== Explanation =====
+
+The program is missing some files it needs to run. This is caused by the package information missing a reference to another, or not including the file.
+
+===== Solution =====
+
+Check if the file required is available in another package. Use the package manager (TazPkg) to search for the file:
+  * start the package manager
+  * 'Recharge' the package lists, if necessary 
+  * click the "Search" tab 
+  * in the //Search// box, enter the file-name ([library].so) and click "Files"
+  * install the package (pick that with the closest name if there is more than one) by double-clicking the entry and clicking //Install Package//
+
+Alternatively, run the following command from a terminal:
+tazpkg search-pkgname library.so
+
+
+... and install the appropriate package with:
+ tazpkg get-install [package] 
+
+If no packages are given, report this as a bug over at the [[http://labs.slitaz.org|Labs]] as it needs to be included, or the dependency removed during the build.
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/faq-login.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/faq-login.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,37 @@
+====== Cannot Login to Desktop ======
+
+===== Symptoms =====
+
+  * Slim, the SliTaz Login Manager, fails with the message:
+ failed to execute login command 
+
+===== Explanation =====
+
+This is caused when files in the user's /home directory are not properly configured. The following files must exist, this can be verified with the ''ls -la'' command:
+  * .Xdefaults
+  * .xinitrc
+  * something else?
+
+===== Solution =====
+You should copy the default files from the template located in the /etc/skel directory. This happens automatically when a new user is created with the SliTaz Control Box, but not when using the command-line utilities. Occasionally users experience these files being removed or modified/broken.
+
+Switch to the root (super) user:
+ su root 
+Change to the affected users /home directory:
+ cd /home/USERNAME 
+Set the shell options to allow the dot (.) to be included in file names:
+ shopt -s dotglob 
+Copy all files, recursively:
+ cp -r /etc/skel/* /home/USERNAME 
+Change ownership of all files and directories in the user's home to that of the affected user:
+ chown -R USERNAME:USERGROUP /home/USERNAME/* 
+Restore the shell options:
+ shopt -u dotglob 
+The essential files should now be restored!
+
+EDIT:
+
+ shopt -u dotglob 
+is not working in slitaz-3.0.iso - instead of this run in addition:
+ chown -R USERNAME:USERGROUP /home/USERNAME/.[a-zA-Z0-9]*
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/faq-pkgconv.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/faq-pkgconv.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,21 @@
+====== Packages from Other Distributions ======
+
+===== Symptoms =====
+
+  * There is a useful package that is not yet available in the SliTaz repositories.
+  * Can I use packages from other distributions on my SliTaz installation?
+
+===== Explanation =====
+
+Packages in a general sense are simply a collection of files and meta-data, compiled from source code to suit a particular environment and installation. Software binaries from other distributions can sometimes run if the libraries that power it exist for SliTaz. It is an easy but not-always-accurate way of testing packages before writing SliTaz [[en:cookbook:receipt | Receipts]] for a SliTaz version of the package.
+
+The SliTaz Package Manager, Tazpkg, can [[http://hg.slitaz.org/tazpkg/raw-file/tip/doc/tazpkg.en.html#convert | convert]] packages from the Debian, RedHat, Slackware and Arch Linux formats, by unpacking them and using the meta-data information inside to create a Tazpkg.
+
+===== Solution =====
+
+Simply run the following command in a Terminal:
+''tazpkg convert //filename//''
+
+The converted Tazpkg will be created after auto-detection of the original format.
+
+There may be occasions where the generated package does not function. This could be a result of mismatching libraries or missing dependant software. Similarly, the binaries may under-perform as they may have been compiled for a different environment and have to adapt. For these reasons, it is highly advisable to compile the software from source code and create a Tazpkg proper.
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/faq-programfailstorun.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/faq-programfailstorun.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,17 @@
+====== A Program Doesn't Run or Quits Unexpectedly ======
+
+===== Symptoms =====
+
+  * Nothing happens when an application is run from the Launch menu.
+  * An application quits without warning.
+
+===== Explanation =====
+
+One or more of problems may have caused this. Run the program in a Terminal to see any error messages the program may deliver.
+
+===== Solution =====
+
+Launch a Terminal (command line) and run the application by typing in its name. See the following FAQs on solving common problems.
+
+
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/faq-terminal.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/faq-terminal.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,27 @@
+====== Overview ======
+
+There are a variety of terminal emulators available for SliTaz and even more for Linux. SliTaz comes with the venerable XTerm, a basic but functioning program.
+
+You may experience some problems with any graphical program, some more serious than others. By running them via a Terminal, any output will appear in the Terminal window so you can identify any problems. Just find its command, type it and press ''Enter''.
+
+\\
+----
+====== XTerm ======
+
+===== Cannot Copy/Paste =====
+
+=== Symptoms ===
+  * I cannot find the copy/paste feature
+  * Right-click for a menu does not work as expected
+ 
+=== Explanation ===
+
+XTerm does not have a right-click menu -- or any other menu for that matter -- but selection is activated by using the mouse buttons.
+
+=== Solution ===
+
+Selection, copy and paste is achievable using the mouse buttons. The three mouse buttons works thus:
+
+  * //left click// defines where the selection begins
+  * //middle click// defines where the selection ends & copies it to clipboard 
+  * //right click// pastes the clipboard contents to the current cursor, not mouse, position
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/faq.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/faq.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,68 @@
+====== Frequently Asked Questions ======
+
+Listed here are the most frequently asked questions from the user forums. Please check here to see if your problem has been fixed before starting a new forum thread.
+
+These are organised into per-scenario groups - from  system-level through to the desktop. Within each, a symptom describes a give-away identification of the problem; a widely-working solution is then outlined.
+
+\\
+===== General  =====
+  * [[faq-login|Log-In Problems]]
+  * [[faq-terminal|Terminals (Copy/Paste etc.)]]
+
+\\
+
+===== Package or Software  =====
+  * [[faq-dependency| An Application Cannot Find Libraries/Files ]]
+  * [[faq-programfailstorun | A Program Doesn't Run or Quits Unexpectedly ]]
+  * [[faq-pkgconv | Can I install a package on SliTaz from another distribution? ]] 
+
+\\
+
+===== Hardware  =====
+  * ...
+
+\\
+
+===== Questions Still Unanswered? =====
+
+No problem! We are happy to hear your question over at our [[http://forum.slitaz.org/|Support Forum]] -- or even the [[http://www.slitaz.org/en/mailing-list.html|Mailing List]] if it is a more lengthy discussion -- once you have looked through our [[http://doc.slitaz.org/en:start|documentation]]!
+
+Answering questions takes time however, to answer them well slightly longer. This time could be better spent for other necessary things, like improving SliTaz or writing documentation.
+
+** Your first post should include the following things: **
+
+  * detailed information about your hardware
+    *  e.g the manufacturer and model of your computer, motherboard or (even better) detailed chip information. The latter can be found by running the following command and uploading the generated //SysInfo.txt// file:
+ 
+
+echo '=== PCI Devices: ===' >> SysInfo.txt && lspci >> SysInfo.txt && echo '=== USB Devices: ===' \ 
+>> SysInfo.txt && lsusb >> SysInfo.txt && echo '=== Kernel Modules: ===' >> SysInfo.txt && lsmod >> SysInfo.txt
+
+
+  * precise information about your SliTaz installation:
+    *  which version to you have? Stable or Cooking?
+    *  are you using the standard ISO or a specific flavor (XVESA, Lo-RAM etc.)?
+    *  is it installed on a HD or on an USB stick?
+    *  do you know which file-system you used?
+
+  * identify when your problem appeared:
+    *  was it just after installation or after an update?
+    *  were there any changes to your normal usage pattern or configuration?
+
+This should provide enough system information for help to be provided.
+
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Low  |
+|Review| Major Updates FIXME  |
+|Priority| High |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly, e.g.,|
+|::: | [[en:guides:start | Add link]]|
+|::: | Add new rows like this ;-)  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/flash.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/flash.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,35 @@
+====== How-To install Adobe Flash Player ======
+
+Open a terminal. Become super-user:
+ $ su -
+
+The default password for the root account is **//root//** .
+
+Type the following as one command:
+
+ # tazpkg get-install get-flash-plugin && get-flash-plugin
+
+
+The package installs a get-flash-plugin command which creates a pseudo-package that downloads the source code from Adobe. It packages the build source code and pulls in any necessary dependencies.
+
+By using this method the Flash plugin can be managed through tazpkg; it will update itself as the repo package is updated.
+
+When you install Flash to SliTaz 3.0 and Midori is not recognizing the plugin - just reinstall Midori with
+ # tazpkg get-install midori --forced Thats it.
+
+
+// This was successfully tested in Midori, Firefox/Shiretoko & Opera, on Cooking 2010-03-14 (the v3 RC). //
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/frugal.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/frugal.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,123 @@
+====== Winboot ======
+
+===== Frugal install to Microsoft Windows partition =====
+
+Install [[http://grub4dos.sourceforge.net/wiki/index.php/Grub4dos_tutorial#Installation|Grub4dos]].
+
+This article will assume that your C: drive is //(hd0,0)//.
+You need at least 160MB to run Slitaz cooking (128MB for Slitaz 1.0).
+
+Tested with Windows XP on FAT32 and on NTFS.
+
+For Windows XP, 2000 or NT, copy http://mirror.slitaz.org/boot/grldr
+into C:\ and append to C:\boot.ini:
+
+C:\grldr="Grub4DOS"
+
+===== Traditional frugal install =====
+
+Copy http://download.tuxfamily.org/slitaz/boot/cooking/bzImage and
+http://download.tuxfamily.org/slitaz/boot/cooking/rootfs.gz (both <30MB)
+into C:\boot and append to C:\menu.lst the following text:
+
+
+title SliTaz cooking
+  kernel (hd0,0)/boot/bzImage rw root=/dev/null vga=normal
+  initrd (hd0,0)/boot/rootfs.gz
+
+Works fine with Windows XP on FAT32 and on NTFS.
+
+===== ISO image install =====
+
+Copy http://download.tuxfamily.org/slitaz/iso/cooking/slitaz-cooking.iso (<30MB)
+into C:\boot. Run defragmentation on C:. And append to C:\menu.lst the following text:
+
+
+title SliTaz cooking
+  map (hd0,0)/boot/slitaz-cooking.iso (hd1)
+  map --hook
+  kernel (hd1)/boot/bzImage rw root=/dev/null vga=normal
+  initrd (hd1)/boot/rootfs.gz
+
+
+Works fine with Windows XP on FAT32 and on NTFS. Using version 0.4.3.
+The file C:\boot\slitaz-cooking.iso MUST be defragmented.
+
+You need 160MB or 256MB of RAM to run the slitaz-cooking.iso.
+If you have less RAM try:
+http://mirror.slitaz.org/iso/cooking/flavors/slitaz-cooking-base.iso or
+http://mirror.slitaz.org/iso/cooking/flavors/slitaz-cooking-justX.iso or
+http://mirror.slitaz.org/iso/cooking/flavors/slitaz-loram.iso instead:
+
+
+title SliTaz cooking base
+  map (hd0,0)/boot/slitaz-cooking-base.iso (hd1)
+  map --hook
+  kernel (hd1)/boot/bzImage rw root=/dev/null vga=normal
+  initrd (hd1)/boot/rootfs.gz
+
+See http://community.slitaz.org/wiki/Loram
+
+===== Web boot install =====
+
+Copy http://download.tuxfamily.org/slitaz/boot/gpxe (<200KB)
+into C:\boot and append to C:\menu.lst the following text:
+
+
+title SliTaz web
+  kernel (hd0,0)/boot/gpxe
+
+
+Gpxe is provided by the SliTaz Live CD too:
+
+title SliTaz web
+  map (hd0,0)/boot/slitaz-cooking.iso (hd1)
+  map --hook
+  kernel (hd1)/boot/gpxe
+
+This will boot the latest available version of SliTaz. See http://boot.slitaz.org/.
+Works fine with Windows XP on FAT32 and on NTFS.
+
+===== Tuning the boot process =====
+
+Additional boot parameters may be appended. For example:
+
+
+title SliTaz cooking
+  map (hd0,0)/boot/slitaz-cooking.iso (hd1)
+  map --hook
+  kernel (hd1)/boot/bzImage rw root=/dev/null vga=extended lang=fr_FR kmap=fr-latin1 laptop autologin config=/dev/hda1,boot/slitaz.sh
+  initrd (hd1)/boot/rootfs.gz
+
+
+The file // /boot/slitaz.sh // in // /dev/hda1 // will be executed at the end of the boot script:
+
+
+  initrd (hd1)/boot/rootfs.gz (hd0,0)/boot/extra-softwares.gz (hd0,0)/boot/my-config-files.gz
+
+
+The compressed cpio archives // /boot/extra-softwares.gz // and // /boot/my-config-files.gz // will be loaded after the official initramfs //rootfs.gz//. This is faster than using the previous // /boot/slitaz.sh // script.
+
+===== Automated Graphical Approach using UNetbootin =====
+
+A SliTaz Frugal Install or a Live USB installation can be performed using [[http://unetbootin.sourceforge.net/|UNetbootin]].
+
+Either the standard version ([[http://unetbootin.sourceforge.net/unetbootin-windows-latest.exe|Windows]] | [[http://unetbootin.sourceforge.net/unetbootin-linux-latest|Linux]]) can be used (select SliTaz from the
+Distribution list), or a custom SliTaz version ([[http://unetbootin.sourceforge.net/unetbootin-windows-latest.exe|Windows]] | [[http://unetbootin.sourceforge.net/unetbootin-linux-latest|Linux]]) may also be used.
+
+To perform a Frugal Install, select “Hard Disk” under installation type;
+to create a Live USB, select “USB Drive” under installation type.
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: | Add new rows like this ;-)  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/kernel.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/kernel.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,86 @@
+====== Build your own custom Linux Kernel for SliTaz ======
+
+===== Prepare your system =====
+
+
+    * Install the slitaz-toolchain meta package. This package contains the required base files.
+        * binutils
+        * linux-headers
+        * glibc-dev
+        * gcc
+        * make
+
+
+# tazpkg get-install slitaz-toolchain
+
+
+    * Install the packages required to configure and compile the kernel sources.
+        * ncurses-dev
+        * perl
+
+
+# tazpkg get-install ncurses-dev
+# tazpkg get-install perl
+
+
+    * SliTaz provides a linux-source package. The kernel source tree will be downloaded from the mirror, installed to the /usr/src/linux- directory, and patched for SliTaz..
+
+
+# tazpkg get-install linux-source
+# /usr/bin/get-linux-source
+# ls -l /usr/src
+lrwxrwxrwx    1 root     root           21 Jul 21 21:27 linux -> linux-2.6.25.5-slitaz
+drwxrwxr-x   23 root     root         4096 Jul 21 22:41 linux-2.6.25.5-slitaz
+-rw-r--r--    1 root     root     48589640 Jul 21 21:28 linux-2.6.25.5.tar.bz2
+
+
+===== Configure and Compile =====
+
+The Linux kernel source tree is now ready to configure and compile.
+
+    * Go to the directory that contains the kernel source tree.
+
+# cd /usr/src/linux
+
+
+    * Prepare the build from the default configuration.
+
+# make oldconfig && make prepare
+
+
+     * Modify the kernel configuration to your needs, and compile.
+     * The //menuconfig// allows you to customise the kernel, which is built into the //bzImage// file. Any //modules// are built and then //install//ed in to the ///usr/include// directory. You should then copy the kernel itself to the ///boot// directory.
+
+# make menuconfig
+# make
+# make modules 
+# make modules_install
+# cp arch/x86/boot/bzImage /boot
+
+
+    * Configure the boot-loader (optional)
+
+# leafpad /boot/grub/menu.lst
+
+
+    * Add the new kernel to the list
+
+# My kernel:
+title 	SliTaz GNU/Linux (cooking) (Kernel )
+		root (hd0,1)
+		kernel /boot/bzImage root=/dev/sda2
+
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Medium  |
+|Review| Minor/Major Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Add "tazwok cook linux"|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/liveusb.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/liveusb.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,42 @@
+====== LiveUSB ======
+
+===== From SliTaz =====
+
+Download > Burn > Boot a SliTaz ISO image. Open Terminal > type in (change ///dev/sda// if needed):
+
+
+$ su root
+# tazusb format
+
+Enter a name such as /dev/sda1 or type 'list'... wait ...
+
+# tazusb gen-liveusb /dev/sda1
+
+
+Wait…. and then reboot!
+
+===== From Windows =====
+
+A SliTaz Live USB installation or a Frugal Install  can be performed using [[http://unetbootin.sourceforge.net/|UNetbootin]].
+
+You may either choose: 
+  * the standard version ([[http://unetbootin.sourceforge.net/unetbootin-windows-latest.exe|Windows]] | [[http://unetbootin.sourceforge.net/unetbootin-linux-latest|Linux]]) : select SliTaz ISO from the Distribution list in unetbootin, or 
+  * a custom SliTaz version ([[http://unetbootin.sourceforge.net/unetbootin-windows-latest.exe|Windows]] | [[http://unetbootin.sourceforge.net/unetbootin-linux-latest|Linux]]).
+
+To create a Live USB, select “USB Drive” under installation type.
+
+You can also choose to do frugal install. To perform a Frugal Install, select “Hard Disk” under installation type;
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Add tazusb.exe, a SliTaz alternative to unetbootin |
+|::: |   |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/lowramcd.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/lowramcd.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,143 @@
+====== Live CD for Low-RAM Systems ======
+
+The minimum RAM requirement for the SliTaz core Live CD is 160MB (128MB for 1.0). Many graphical applications won't run with such a low amount of memory; so, using the text-mode //screen=text// boot option is recommended.
+
+The packages //slitaz-loram//, //slitaz-loram-http// or //slitaz-loram-cdrom// can be used to build a LiveCD for systems with RAM larger than 64MB, 32Mb or 24MB respectively. These can be installed directly on the host system, rather than specified in the packages list for the LiveCD you are building.
+
+    * //slitaz-loram// will compress the ///usr// tree and the system will still run in RAM. It will not use a cdrom, harddisk or USB key
+    * //slitaz-loram-http// will get the ///usr// tree from an iso image stored in http://mirror.slitaz.org/ built using //slitaz-loram-cdrom//, and pass the 'tiny' keyword while booting from the web
+    * //slitaz-loram-cdrom// will move the ///usr// tree onto the cdrom
+
+///usr// will be read-only. If the package //funionfs// or //aufs// is installed you will have read-write access to ///usr//.
+
+These packages patch ///etc/init.d/rcS// to mount ///usr// and install two scripts in ///etc/tazlito//:
+
+    * //loram.rootfs// is called by //tazlito gen-distro// to compress or move ///usr//
+    * //loram.extract// is called by the //slitaz-installer// to uncompress or move ///usr// and install the same distribution as the SliTaz core LiveCD
+
+Let's build a //slitaz-loram-cdrom.iso// !
+
+===== slitaz-loram-cdrom =====
+
+We boot the LiveCD and install the slitaz-loram-cdrom package:
+
+ # tazpkg get-install slitaz-loram-cdrom 
+
+//tazlito gen-distro// will then create an ISO with the packages listed in ///etc/tazlito/distro-packages.list// or //./distro-packages.list//. Since some more packages are installed, we remove these files to force tazlito to use all of the installed packages.
+
+ # rm -f /etc/tazlito/distro-packages.list ./distro-packages.list 
+
+Now we can build the iso image…
+
+ # tazlito gen-distro 
+
+…and burn it.
+
+# wodim dev=1,0,0 /home/slitaz/distro/slitaz-hacked.iso 
+
+===== Variations of slitaz-loram & slitaz-loram-cdrom =====
+
+//slitaz-loram// compresses ///usr// with //cromfs// by default, which gives a higher compression ratio but is very slow. You can use //squashfs// instead:
+
+    * refuse to install cromfs during the slitaz-loram installation
+
+ # yes n | tazpkg get-install slitaz-loram 
+
+    * install squashfs with its dependencies
+
+ # yes y | tazpkg get-install squashfs 
+
+//slitaz-loram-cdrom// moves ///usr// uncompressed to the cdrom and produces a 90MB iso. If you install cromfs or squashfs, ///usr// will be compressed on the LiveCD and the ISO size will be around 30 megabytes.
+
+===== Let's build a slitaz-loram-cdrom-sqfs.iso!=====
+
+Install the package //slitaz-loram-cdrom// and //squashfs// (sqfs) on the host system:
+
+
+ # tazpkg get-install slitaz-loram-cdrom
+ # yes y | tazpkg get-install squashfs
+
+
+Now we repeat the latter points of the above process:
+
+ # rm -f /etc/tazlito/distro-packages.list ./distro-packages.list
+ # tazlito gen-distro
+ # wodim dev=1,0,0 /home/slitaz/distro/slitaz-hacked.iso
+
+
+===== slitaz-loram-cdrom and Large Memory Systems =====
+
+When the //slitaz-loram-cdrom// LiveCD detects enough memory during boot, ///usr// is copied from the CD-ROM to RAM. You can eject and/or use the CD drive. The system behaves as a regular LiveCD in this case:
+
+    * a slitaz LiveCD (/usr was not compressed on the cdrom)
+    * a slitaz-loram LiveCD (/usr was compressed on the cdrom by squashfs or cromfs)
+
+===== slitaz-loram-cdrom and Tiny Memory Systems =====
+
+The boot command line is usually:
+
+ boot: slitaz args... 
+
+Slitaz boots on a 9MB RAM system with the boot command:
+
+ boot: loram single root=/dev/hdc 
+
+Where ///dev/hdc// is the CD-ROM device, the loram boot entry avoids RAM disk creation and CD-ROM detection.
+
+Note that on a system with such a low amount of memory, the first thing to do is add swap!
+
+You need 10MB to use the boot scripts with:
+
+ boot: loram root=/dev/hdc 
+
+In this case you can add arguments like kmap=, config=, etc.
+
+===== slitaz-loram Auto-Extraction =====
+
+Each slitaz-loram* flavor can be extracted into RAM at boot time (if enough memory is available) by using the boot argument extract-loram. You will get a core flavor running without read-only restrictions for /usr.
+
+For example, assuming you boot the slitaz-loram-cdrom-sqfs:
+
+ boot: slitaz extract-loram 
+
+You will get:
+
+    * /usr read-only squashfs on a CD-ROM with a smaller RAM size
+    * /usr read-only squashfs in RAM with a medium RAM size (like slitaz-loram)
+    * /usr read-write tmpfs in RAM with a larger RAM size (like slitaz-core)
+
+===== Build a slitaz-loram with tazlitobox =====
+
+Since SliTaz 3.0, you can now build a slitaz-loram LiveCD more easily:
+    * launch tazlitobox
+    * click on the Low RAM tab
+    * select //The filesystem is always in RAM// (for slitaz-loram) or //The filesystem may be on a CDROM// (for slitaz-loram-cdrom)
+    * fill the ISO input with your Slitaz flavor (3.0 or more recent)
+    * update the ISO output
+    * click //build ISO//
+
+The filesystem root (/) is compressed (not /usr only) and mounted read-write thanks to the aufs package.
+The //mount// and //df// commands will show a strange output, handy to detect that this kind of loram is running.
+
+You can also use the following command in text mode:
+ # tazlito build-loram original.iso loram.iso
+or:
+ # tazlito build-loram original.iso loram-cdrom.iso cdrom
+
+Meta flavors are supported; you can loramize a slitaz-3in1.iso !
+
+===== And what to do with only 8MB RAM? =====
+Try Tiny Slitaz : http://pizza.slitaz.org/tiny/ !
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve|Needs a review by developers|
+|::: | Add new rows like this ;-)  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/manyinone.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/manyinone.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,48 @@
+======= Create many-in-1 flavors =======
+
+Slitaz LiveCDs run fully in RAM. The feature set depends on the available RAM size. You can build an auto adaptive LiveCD to ensure that the right feature set is launched according to the detected RAM size. You need to:
+
+    * define a flavor list (or an ISO list) where each flavor is nested in the previous one (like russian dolls),
+    * define the minimum RAM quantity necessary for each flavor.
+
+The many-in-1 ISO may be a little bit larger than the largest
+flavor. Sometimes the sizes are identical.
+
+We will build the official slitaz-3in1 flavor which boots:
+
+    * the core flavor with 160MB or more
+    * the justx flavor with 96MB to 160MB
+    * the base flavor with 32MB to 96MB
+    * and displays an error message with less than 32MB...
+
+The ISO images slitaz-3.0-3in1.iso and the largest flavor slitaz-3.0.iso share the same size : 31457280 bytes. (caused by the 1MB padding, it should be 123351 bytes larger otherwise).
+
+===== The best way: create a flavor =====
+
+A flavor holds all the necessary information to build a LiveCD.
+The [[http://bb.slitaz.org/|build bot]] will automagically keep the flavor file (.flavor) up to date and this tiny file will also be used by tazlito to (re)generate the ISO image.
+
+[[http://hg.slitaz.org/flavors|flavors]] are like software sources for the flavor file: the [[http://bb.slitaz.org/|build bot]] is a make tool and **tazlito pack-flavor** the compiler. Providing flavors is like providing source files and providing ISOs is like providing executables only.
+
+A meta flavor has no rootfs, rootcd or packages.list.
+The **ROOTFS_SELECTION** in the receipt (see http://hg.slitaz.org/flavors/file/324757d594ef/core-3in1) gives the nested flavors with the according ram sizes from the largest to the smallest.
+
+
+ROOTFS_SELECTION="160M core 96M justx 32M base"
+
+
+The rootfs and the rootcd are taken from the largest flavor.
+
+===== The easy way: using tazlitobox =====
+
+Launch **tazlitobox**, select tab **meta**. Enter the ISO file in **ISO input** and add the according necessary RAM size in **RAM needed** for each flavor with the **+** button. Fill the **ISO output** name and click **Build ISO**.
+
+===== The cmdline way: using tazlito =====
+
+Usage: tazlito merge size1 iso size2 rootfs2 [sizeN rootfsN]...
+
+The largest flavor is given as an ISO file to get the additional rootcd files and will get the resulting ISO.
+
+
+tazlito merge 160M slitaz-core.iso 96M rootfs-justx.gz 32M rootfs-base.gz
+
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/midori.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/midori.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,126 @@
+====== Midori Tips & Tweaks ======
+I am writing this guide since Midori is the default browser in Slitaz 3. Your first thought may be to install Firefox and not giving Midori a try because it lacks features. I thought it lacked features or Addon's also until I dug around some. If you want to know the history of Midori visit it's Wiki page: [[http://en.wikipedia.org/wiki/Midori_(web_browser)|Midori Wiki]]
+
+
+
+Things that I will cover:
+
+Ad Blocking
+Custom Search Engines
+Flash Blocking
+UserScripts
+Shortcuts
+
+
+===== Enabling Extensions =====
+
+Upon opening Midori click on the "Tools Menu", Go down to "Extensions" and click on it. This should open up a "panel" that displays boxes that you can check to enable different Extensions or Options. Check only the boxes you wish to enable. I would enable "Statusbar Features" and "Toolbar Editor" right now. Everything involving those two should be self explantory. So no need for a "HowTo". I would tell you what other things to enable right now, but if someone adds to this wiki then this paragraph would need to be edited. So if anything needs to be enabled it will be mention it as it go along.
+
+===== Ad Blocking =====
+In extensions enable: Advertisement blocker
+
+Most people like ad blocking that FireFox has through an extension called Adblock Plus(ABP). Well Midori has an adblocker that uses the well known "easylist" from ABP. Now that you have it enabled we need to edit it. Click on the "Tools Menu", now click on "Configure Advertisement filters". This should now open a box looking like this:
+
+{{http://img541.yfrog.com/img541/4508/beforeadded.png}}
+
+From the picture you can see that adding a ruleset is pretty self explanatory. As an example click on Add, then insert this url: http://easylist-downloads.adblockplus.org/easyprivacy.txt 
+
+
+{{http://img541.yfrog.com/img541/2485/added.png}}
+
+That is what it should now look like. Now to block a single image just right click the image on the page you want to block. Go down to Block Image and click Add. Now that image is blocked.
+===== Managing Search Engines ===== 
+No extension needs to be enabled for this feature.
+
+This is one of my favorite things in any browser. I use this for other things then just search engines. I will share that later. Click on the "Tools Menu", then click on "Manage Search Engines". Just like Ad blocking you should get a box to pop up that looks like this:
+
+{{http://img541.yfrog.com/img541/7471/manage.png}}
+
+Since I don't really use anything else but google I am just going to add Yahoo! as an example of how to add it and use it. Click add and fill it in to look like this:
+
+{{http://img542.yfrog.com/img542/4866/yahoo.png}}
+
+Once that is done go up to the URL bar in midori and type: "y slitaz linux" without the quotes. [[http://img30.yfrog.com/img30/6048/yslitazlinux.png|Example:y slitax linux]]. After pressing Enter you should now see the yahoo search results for slitaz. [[http://img402.yfrog.com/img402/2932/yslitazresults.png|Yahoo Results]] Typing "g slitaz" again without the quotes would give you the google results for SliTaz.
+
+Here is what I use it for besides search engines. In Opera when you bookmark something you can make a nickname for the site. I have the letters: fs for http://forum.slitaz.org. So I just type "fs" without the quotes in the urlbar to go to SliTaz's forum. Now I don't see this feature in Midori so I just make a custom search engine like I did for Yahoo!. I am not really adding a search just using it as a shortcut. I think for the pictures I added that it is self explanatory how to add any site you want to make a shortcut for.
+
+For all you twitter users or people that like shortened urls. Add this to custom searches: 
+http://is.gd/create.php?longurl=
+{{http://img260.yfrog.com/img260/7176/isgd.png}}
+
+I give mine the Token letter "u". When I have a big url I want to shorten, I go to the URL bar, go to the left of the "http" in the url, then I type "u". Then press space then enter it takes me to that site and shortens the url. Example:[[http://img260.yfrog.com/img260/6982/shorten.png|Shortening URL]]
+Result:[[http://img30.yfrog.com/img30/6563/shortened.png|Shortened URL]]
+
+For those who hate using the mouse like me and want to shorten url's you can do the same thing above like this: Ctrl-L, Left Arrow key, type u, spacebar, then enter If you have javascript enabled then the shortened url should already be highlighted. So a quick Ctrl-c should copy it for you.
+    
+
+===== Flash Blocking =====
+
+To flashblock you need to use a userscript. UserScripts are just custom javascripts to do a range of things. I will cover other UserScripts later in this wiki but flashblock is more then likely gonna be the only one anyone will use.
+
+First we need to make a folder if you don't already have it: /home/tux/.local/share/midori/scripts
+"tux" is just used as an example. If you have a different user name then change accordingly. 
+
+These pictures are kind of big so I am just linking to them. Example before FlashBlock:
+[[http://img180.yfrog.com/img180/7269/blocked.png|Flash Blocked]]
+
+Now go to: [[http://rightfootin.blogspot.com/2009/04/flashblock-wannabe.html|Flashblock Wannabe]] . Download FlashBlock.user.js.txt (remove the .txt extension) to the folder we just created. Go to the Tools Menu, and click on UserScripts. You should now see "FlashBlock Wannabe" Make sure there is a checkmark next to it. Sometimes the UserScripts show up right away and other times they don't so I just restart Midori to view the UserScripts. So if it isn't showing then just restart Midori. Now you should have flash blocked unless you click on it like the flashblocker addon for FireFox. It should look like this:
+
+[[http://img541.yfrog.com/img541/2801/notblocked.png|Flash Unblocked]]
+===== User Scripts =====
+
+If you already did the Flashblocking part then this should be as easy as downloading them and putting them in the correct folder. No big HowTo here I will just show you some examples of the ones I use and what they do.
+
+[[http://userscripts.org/scripts/show/1352|Linkify]]: If you have ever been to a site or forum and someone posted a link that is just text and not clickable then this is for you. It makes all "http" links clickable. It saves you from highlighting and copying and pasting links to a url bar. 
+
+[[http://userscripts.org/scripts/show/5059|Google Image Redirector]]: If you ever google search for images and click on an image you will notice that it take you to the page but the tiny image is in a frame. This userscript takes you directly to the actual image. Saves you a couple clicks of the mouse.
+
+[[http://userscripts.org/scripts/show/72270|Google Show Options]]: Last year google added advanced search options in results. You could click on the "Show Options" and it would list them. This bypasses clicking on it and it shows it right away without have to click it.  
+
+[[http://userscripts.org/scripts/show/54108|Just Show Images]]: If you have ever clicked on a link from a forum or anything to certain image hosting sites you would notice all the ads. This UserScript just shows the picture you want and little else. 
+
+[[http://userscripts.org/scripts/show/54790|Easy YouTube Downloader]]: If you would like to download the video from YouTube without going to a seperate site, you can use this script. It adds a download option for multiple video formats on the screen.
+
+===== Shortcuts =====
+In extensions enable: shortcuts
+
+I try to use the mouse as little as possible. So shortcuts come in handy. Here is how to view and/or edit them to your taste. Open up the "Tools Menu" go down to and click on "Customize Shortcuts." You will get a popup that looks like this:
+
+{{http://img21.yfrog.com/img21/1046/shortcuts.png}}
+
+In the picture you will see an action along with an assigned "shortcut". Some show an action but are disabled. I will show you how to change a "shortcut" or to enabled one that is disabled. To assign a "shortcut" click on what you would like to change to highlight. Now go to the right and click the mouse where the "shortcut" or word "disabled" is and click. It should change the text to "New accelerator..." Now all you have to do is press a combination of keys you would like to make up your shortcut. Popular choices to start your shortcut with are any of these:
+ Control, Alt, or either Winkeys
+Winkeys will be either "Super L" or "Super R" depending on which you press. Not every keyboard has a "Winkey" or only has just one. I prefer to use the F1 to F12 keys. Here is an example of some of my shortcuts:
+
+
+Show/Hide Sidepanel   F2
+Show/Hide Bookmarkbar F3
+Show/Hide Menubar     F4
+Refresh               F5
+Preferences           F7
+Focus Current Tab     F9
+Full Screen           F11
+Bookmarks             Ctrl+B
+Add Bookmarks         Ctrl+D
+Homepage              Ctrl+H
+Highlight URLbar      Ctrl+L
+Close Tab             Ctrl+W
+Next Tab              Ctrl+Page Down
+Previous Tab          Ctrl+Page Up
+ 
+
+Just wanted to add that if you want to "disable" a shortcut. Pressing Backspace in "New accelarator..." will disable it.
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/modem.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/modem.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,17 @@
+====== Hardware Guides: Modems ======
+
+[[cricket-a600|Cricket A600 Broadband Modem]]: - How to install a Cricket a600 Broadband Modem
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Low  |
+|Review| Major Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/netstart.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/netstart.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,57 @@
+====== Web start and possible immediate installation ======
+
+===== Special figure in Slitaz ! =====
+
+Slitaz is one of the extremely rare OS's available fully prepared for the web start in live mode using a very small starting program. The starting program can be saved on a old floppy disk or very little special ISO burned on a CD-ROM.
+
+But each starting ISO of Slitaz with the live version of "base", "justX" or "stable" or "cooking" contains also this start program being used through the commando line options at starting time of the ISO.
+
+The special advantage of this kind of start is to work with the most actual cooking version and not with the version of the CD.
+
+The same technical ability can of course be used within a closed community.
+
+==== Where can I find the starting image for a starting floppy disk? ====
+
+http://mirror.slitaz.org/boot/floppy-grub4dos
+
+Please read more here:
+
+http://boot.slitaz.org/
+
+==== Where can I find the small ISO for a small starting CD rom? ====
+
+You can use the little flavor version
+ 
+http://mirror.slitaz.org/iso/2.0/flavors/slitaz-2.0-base.iso
+
+for that.
+
+Only enter please "web" as commando line option!
+
+==== Starting from the net ====
+
+The start from net don't differ from usual start from the CD.
+
+Only enter "web" as commando line option. The starting program don't follow the CD any more but search the more actual file on the web.
+
+==== Install Slitaz on the hard disk after the net start ====
+
+Of course here is an important difference compared with the usual start:
+
+There is no CD in the drive where the installation program can find the row files.
+
+.... 
+
+==== Regular net start in my community net (school etc.) ====
+
+=== Install the adequate Slitaz version on the own server ===
+
+....
+
+=== Limit access if required ===
+
+....
+
+=== Prepare an adequate ISO for a own starting check card mini CD ===
+
+....
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/network-script.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/network-script.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,158 @@
+====== Secrets of /etc/init.d/network.sh ======
+
+===== Introduction =====
+
+SliTaz launches the /etc/init.d/network.sh at startup to initialize the network. It configures the hostname, loopback interface, and internet connection.
+
+It's also possible to call the script when SliTaz is started, and use it to open or close internet connections. For example netbox and any software linking get-wifi-firmware (get-ipw2100-firmware, get-b43-firmware...) use it.
+
+===== Usage =====
+
+By default, /etc/init.d/network.sh uses /etc/network.conf as the conf file. Parameters written in that file are made for the default network connection.
+
+To start the default connection, as when booting:
+
+
+# /etc/init.d/network.sh start
+
+
+The start arg should be used only at boot. To stop the connection:
+
+
+# /etc/init.d/network.sh stop
+
+
+To stop and restart:
+
+
+# /etc/init.d/network.sh restart
+
+
+But, most interestingly, is that ///etc/init.d/network.sh// may also use another config file. It's useful if you're using a laptop, as you can configure multiple connections for multiple access points.
+
+For example, we can create a directory /etc/network, containing some config files, named:
+
+    * Home, for home, using an ethernet connection and a static ip.
+    * Desktop, for the desktop, with a wep encryption, and a static ip.
+    * Univ, wifi without encryption, and with dhcp.
+
+Now to get connected at Home, later at a Desktop and finally at Univ, before stopping connection, we only have to:
+
+
+# /etc/init.d/network.sh restart /etc/network/Home
+# /etc/init.d/network.sh restart /etc/network/Desktop
+# /etc/init.d/network.sh restart /etc/network/Univ
+# /etc/init.d/network.sh stop
+
+
+===== Sudo =====
+
+Since /etc/init.d/network.sh/ can only be used by root, if you want a normal user to use it, you should install sudo:
+
+
+# tazpkg get-install sudo
+
+
+And then configure it:
+
+
+# visudo
+
+
+For user tux, which must use network.sh from every host; without a password you should add:
+
+
+tux  ALL=NOPASSWD: /etc/init.d/network.sh,
+
+
+For user tortux, which may only get connected from localhost, and which should use a password each time, you should add:
+
+
+tortux my_hostname=PASSWD: /etc/init.d/network.sh,
+
+
+If you forgot your hostname, just run:
+
+
+$ cat /etc/hostname
+
+
+Here is some help to use visudo:
+
+    * i insertion mode (to write).
+    * Escape exit insertion mode.
+    * :wq record and quit.
+    * :q! quit without recording.
+
+===== Openbox =====
+
+All this is not that really user friendly...
+
+That's why I'll give you a perfect treat: A way to integrate all this in an openbox menu! Create a script /usr/lib/openbox/network-menu.sh, and add this to it:
+
+
+#!/bin/sh
+#
+# openbox pipe menu to start network connections
+# (This script is only useful if sudo is installed, and correctly configured)
+
+echo ''
+
+# for default file:
+echo ''
+echo ''
+echo 'sudo /etc/init.d/network.sh restart'
+echo ''
+
+# for others files:
+for file in $(ls /etc/network/)
+	do
+	echo -e ""
+	echo ''
+	echo "sudo /etc/init.d/network.sh restart /etc/network/$file"
+	echo ''
+	done
+
+# To stop connections:
+echo ''
+echo ''
+echo 'sudo /etc/init.d/network.sh stop'
+echo ''
+
+echo ''
+
+
+Make it executable:
+
+
+# chmod +x /usr/lib/openbox/network-menu.sh
+
+
+And now you only have to add these lines in //~/.config/openbox/menu.xml//:
+
+
+ menu id="network-menu" label="Network" 
+	execute="/usr/lib/openbox/network-menu.sh" />
+
+
+Then reconfigure openbox:
+ 
+
+$ openbox --reconfigure
+
+
+Enjoy!
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: |  |
+
+\\
+----
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/nvidia.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/nvidia.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,111 @@
+====== Install the latest non-free Nvidia driver ======
+
+===== Required Reading =====
+
+    * Handbook - [[http://www.slitaz.org/en/doc/handbook/x-window.html#xorg|Xorg Installation]]
+    * Quickstart Guide - [[en:guides:kernel|Build your own custom Linux Kernel]]
+
+===== Prepare =====
+
+    * Download the installer from the Nvidia [[http://www.nvidia.com/object/unix.html|website]]. Latest version 190.53
+    * Install the Xorg server
+
+
+# tazpkg get-install xorg-server
+
+
+    * Install the linux-source package and development tools. See [[http://community.slitaz.org/wiki/quickstart/customkernel|here]]
+
+
+# tazpkg get-install linux-source
+
+
+
+===== Install the driver =====
+For this part you're going to need a pencil and paper as we now have to work in text mode without a X-server running
+
+When you're ready press alt-ctrl-del, you should now see a command line:-
+
+    * Configure the X-server and copy the (generated) xorg.conf
+
+
+# Xorg -configure
+# cp /root/xorg.conf.new /etc/X11/xorg.conf
+
+
+    * Prepare the Kernel
+
+# cd /usr/src/linux
+
+# make oldconfig && make prepare
+
+# make menuconfig (not required - but if you've come this far, you can take a peek)
+# make bzImage
+# make modules 
+# make modules_install
+
+
+    * Now make executable and install the Nvidia driver, change to directory you installed to
+
+ # chmod +x NVIDIA-Linux-x86-177.80.pkg1.run
+ # ./NVIDIA-Linux-x86-177.80.pkg1.run --kernel-source-path=/usr/src/linux
+
+
+    * Copy the Kernel Image to /boot
+
+
+# cd /usr/src/linux
+# cp arch/x86/boot/bzImage /boot
+
+
+
+===== Restart =====
+
+    * Reboot into text mode
+
+# reboot - Hard drive users
+# tazusb writefs gzip && reboot - USB users
+
+
+Don't forget to pass the screen=text option at startup, (it may well boot into text mode anyway, if not just press alt-ctrl-del again)
+
+    * Load the nvidia module
+
+
+# modprobe -v nvidia 
+
+
+    * Edit Slim configuration file to load Xorg server
+
+
+# vi /etc/slim.conf
+
+
+default_xserver     /usr/bin/Xorg
+#default_xserver     /usr/bin/Xvesa
+#xserver_arguments   -ac -shadow dpms +extension Composite -screen 1024x768x24
+
+
+    * Restart Slim
+
+
+# /etc/init.d/slim start
+
+
+Err… that's it
+
+(If you want the nvidia module to persist, just add it to the LOAD_MODULES variable in /etc/rcS.conf)
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Low  |
+|Review| DELETEME |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Nvidia pkgs are in repos, no need to compile anymore|
+|::: | Missing "tazhw setup nvidia --non-free" |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/playground.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/playground.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,4 @@
+===== Hardware Guide =====
+
+^  Laptop  ^  Harddisk  ^  Graphics  ^  Display  ^  Sound  ^  WiFi  ^  Wired  ^  Keyboard  ^
+|Lenovo T61  |160GB ATA  |Nvidia NVS 140M\\ Driver: nv (xorg)  |1400 x 900  |Intel Corporation 82801H\\ Driver: snd-hda-intel  |Intel Corporation PRO/Wireless 4965 AG\\ Driver: n/k  |Intel Corporation 82566MM\\ Driver: e1000  |standard  |
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/powermgmt.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/powermgmt.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,40 @@
+====== ACPI (Advanced Configuration and Power Interface) ======
+
+To install the acpi daemon and modules:
+
+# tazpkg get-install acpid
+# tazpkg get-install linux-acpi
+
+
+The acpi daemon needs to be started before dbus and hal,
+so edit your ///etc/rcS.conf// to look like this:
+
+RUN_DAEMONS="acpid, dbus, hald, etc..."
+
+
+Or, to start manually:
+
+# /etc/init.d/hald stop
+# /etc/init.d/dbus stop
+# /etc/init.d/acpid start
+# /etc/init.d/dbus start
+# /etc/init.d/hald start
+
+
+To check it's working, just:
+
+$ cat /proc/acpi/battery/{BAT0}/info
+
+
+You can find some example scripts in ///etc/acpi//.
+
+
+
+
+
+
+
+
+
+
+
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/printer.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/printer.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,392 @@
+====== Printing ======
+
+The CUPS (Common Unix Printing System) software manages printers connected to the local computer or over a network. The local printers are attached via a loop-back connection (IP 127.0.0.1), a network connection pointing to the same system.
+
+===== Installing a Network Printer =====
+
+Install CUPS and add the user(s) to the //lp// group to gain permissions to access the devices. This can be done as root in a terminal:
+
+
+# tazpkg get-install cups
+# addgroup tux lp
+
+
+Again as root, customise the default configuration in /etc/cupsd.conf:
+
+
+# Administrator user group...
+SystemGroup lp
+
+# Restrict access to the admin pages...
+
+  Order allow,deny
+  Allow 127.0.0.1
+
+
+# Restrict access to configuration files...
+
+  AuthType Default
+  Require user @SYSTEM
+  Order allow,deny
+  Deny From None
+  Allow From 127.0.0.1
+  
+
+Set the administrative password for CUPS and add an administrative user:
+
+
+# lppasswd -g lp -a tux
+
+
+You should now be able to have access to the CUPS administration through your browser by entering the address ''http://localhost:631/''
+
+Install the printer drivers with the following packages:
+
+    - hplip : for HP printers
+    - gutenprint : for Canon, Epson, Lexmark, Sony, Olympus
+    - foomatic-db, foomatic-db-engine, foomatic-db-nonfree and foomatic-filters : several free software printer drivers
+    - ufr2: for Canon printers (extra drivers)
+    - splix: for Samsung
+    - cups-pdf: for "printing" to PDF files
+
+For example, install the HP printer drivers with the following //root// command
+
+# tazpkg get-install hplip
+
+
+Now you add a new printer in the browser interface and choose:
+
+LPD/LPR Host or Printer (Unknown),
+and add the address socket//192.168.2.1:9100
+
+If you get the error, "//Returning IPP client-error-document-format-not-supported for Print-Job in /var/log/cups/error.log//" then add two files to the /etc/cups directory. The easiest method is to start a text editor such as Leafpad from a root terminal; start the Terminal and switch to the root user.
+
+  * ''mime.convs'' (/etc/cups/mime.convs):
+
+application/pdf		application/postscript	33	pdftops
+application/postscript	application/vnd.cups-postscript	66	pstops
+application/vnd.hp-HPGL	application/postscript	66	hpgltops
+application/x-cshell	application/postscript	33	texttops
+application/x-csource	application/postscript	33	texttops
+application/x-perl	application/postscript	33	texttops
+application/x-shell	application/postscript	33	texttops
+text/plain		application/postscript	33	texttops
+text/html		application/postscript	33	texttops
+image/gif		application/vnd.cups-postscript	66	imagetops
+image/png		application/vnd.cups-postscript	66	imagetops
+image/jpeg		application/vnd.cups-postscript	66	imagetops
+image/tiff		application/vnd.cups-postscript	66	imagetops
+image/x-bitmap		application/vnd.cups-postscript	66	imagetops
+image/x-photocd		application/vnd.cups-postscript	66	imagetops
+image/x-portable-anymap	application/vnd.cups-postscript	66	imagetops
+image/x-portable-bitmap	application/vnd.cups-postscript	66	imagetops
+image/x-portable-graymap application/vnd.cups-postscript	66	imagetops
+image/x-portable-pixmap	application/vnd.cups-postscript	66	imagetops
+image/x-sgi-rgb		application/vnd.cups-postscript	66	imagetops
+image/x-xbitmap		application/vnd.cups-postscript	66	imagetops
+image/x-xpixmap		application/vnd.cups-postscript	66	imagetops
+image/x-sun-raster	application/vnd.cups-postscript	66	imagetops
+
+
+image/gif		application/vnd.cups-raster	100	imagetoraster
+image/png		application/vnd.cups-raster	100	imagetoraster
+image/jpeg		application/vnd.cups-raster	100	imagetoraster
+image/tiff		application/vnd.cups-raster	100	imagetoraster
+image/x-bitmap		application/vnd.cups-raster	100	imagetoraster
+image/x-photocd		application/vnd.cups-raster	100	imagetoraster
+image/x-portable-anymap	application/vnd.cups-raster	100	imagetoraster
+image/x-portable-bitmap	application/vnd.cups-raster	100	imagetoraster
+image/x-portable-graymap application/vnd.cups-raster	100	imagetoraster
+image/x-portable-pixmap	application/vnd.cups-raster	100	imagetoraster
+image/x-sgi-rgb		application/vnd.cups-raster	100	imagetoraster
+image/x-xbitmap		application/vnd.cups-raster	100	imagetoraster
+image/x-xpixmap		application/vnd.cups-raster	100	imagetoraster
+image/x-sun-raster	application/vnd.cups-raster	100	imagetoraster
+
+application/vnd.cups-postscript	application/vnd.cups-raster	100	pstoraster
+
+
+  * ''mime.types'' (/etc/cups/mime.types):
+
+
+application/pdf			pdf string(0,%PDF)
+application/postscript		ai eps ps string(0,%!) string(0,<04>%!) \
+				contains(0,128,<1B>%-12345X) + \
+				(contains(0,4096,"LANGUAGE=POSTSCRIPT") \
+				 contains(0,4096,"LANGUAGE = Postscript") \
+				 contains(0,4096,"LANGUAGE = PostScript") \
+				 contains(0,4096,"LANGUAGE = POSTSCRIPT") \
+				 (contains(0,4096,<0a>%!) + \
+				  !contains(0,4096,"ENTER LANGUAGE")))
+application/vnd.hp-HPGL		hpgl \
+				string(0,<1B>E<1B>%0B) \
+				string(0,<1B>%-1B) string(0,<201B>)\
+				string(0,BP;) string(0,IN;) string(0,DF;) \
+				string(0,BPINPS;) \
+				(contains(0,128,<1B>%-12345X) + \
+				 (contains(0,4096,"LANGUAGE=HPGL") \
+				  contains(0,4096,"LANGUAGE = HPGL")))
+
+########################################################################
+#
+# Image files...
+#
+
+image/gif			gif string(0,GIF87a) string(0,GIF89a)
+image/png			png string(0,<89>PNG)
+image/jpeg			jpeg jpg jpe string(0,) &&\
+				(char(3,0xe0) char(3,0xe1) char(3,0xe2) char(3,0xe3)\
+				 char(3,0xe4) char(3,0xe5) char(3,0xe6) char(3,0xe7)\
+				 char(3,0xe8) char(3,0xe9) char(3,0xea) char(3,0xeb)\
+				 char(3,0xec) char(3,0xed) char(3,0xee) char(3,0xef))
+image/tiff			tiff tif string(0,MM<002A>) string(0,II<2A00>)
+image/x-photocd			pcd string(2048,PCD_IPI)
+image/x-portable-anymap		pnm
+image/x-portable-bitmap		pbm string(0,P1) string(0,P4)
+image/x-portable-graymap	pgm string(0,P2) string(0,P5)
+image/x-portable-pixmap		ppm string(0,P3) string(0,P6)
+image/x-sgi-rgb			rgb sgi bw icon short(0,474)
+image/x-xbitmap			xbm
+image/x-xpixmap			xpm ascii(0,1024) + string(3,"XPM")
+#image/x-xwindowdump		xwd string(4,<00000007>)
+image/x-sun-raster		ras string(0,<59a66a95>)
+
+#image/fpx			fpx
+image/x-alias			pix short(8,8) short(8,24)
+image/x-bitmap			bmp string(0,BM) && !printable(2,14)
+image/x-icon			ico
+
+########################################################################
+#
+# Text files...
+#
+
+application/x-cshell		csh printable(0,1024) + string(0,#!) +\
+				(contains(2,80,/csh) contains(2,80,/tcsh))
+application/x-perl		pl printable(0,1024) + string(0,#!) +\
+				contains(2,80,/perl)
+application/x-shell		sh printable(0,1024) + string(0,#!) +\
+				(contains(2,80,/bash) contains(2,80,/ksh)\
+				 contains(2,80,/sh) contains(2,80,/zsh))
+application/x-csource		c cxx cpp cc C h hpp \
+				printable(0,1024) + \
+				(string(0,/*) string(0,//)
+				 string(0,#include) contains(0,1024,<0a>#include) \
+				 string(0,#define) contains(0,1024,<0a>#define))
+text/html			html htm printable(0,1024) +\
+				(istring(0,"") istring(0,"))
+text/plain			txt printable(0,1024)
+text/css			css
+
+
+########################################################################
+#
+# RSS feed type...
+#
+
+application/rss+xml		rss
+
+
+########################################################################
+#
+# CUPS-specific types...
+#
+
+application/vnd.cups-command	string(0,'#CUPS-COMMAND')
+application/vnd.cups-form	string(0,"")
+application/vnd.cups-pdf
+application/vnd.cups-postscript
+application/vnd.cups-ppd	ppd string(0,"*PPD-Adobe:")
+application/vnd.cups-raster	string(0,"RaSt") string(0,"tSaR")
+application/vnd.cups-raw	(string(0,<1B>E) + !string(2,<1B>%0B)) \
+				string(0,<1B>@) \
+				(contains(0,128,<1B>%-12345X) + \
+				 (contains(0,4096,"LANGUAGE=PCL") \
+				  contains(0,4096,"LANGUAGE = PCL")))
+
+########################################################################
+#
+# Raw print file support...
+#
+# Comment the following type to prevent raw file printing.
+#
+
+application/octet-stream
+
+
+If at the end of the procedures the printer is not working, restarting the service or computer may help.
+
+===== Installing an USB Brother HL 2030 Printer =====
+
+To install cups, hal-cups-utils, usbutils. As root, type:
+
+
+root@slitaz:# tazpkg get-install cups
+root@slitaz:# tazpkg get-install hal-cups-utils
+root@slitaz:# tazpkg get-install usbutils
+
+
+Cups is used to manage the printer, hal-cups-utils allows cups to use HAL for printer connections and usbutils gives us the lsusb utility which lets us know how the printer is connected.
+
+Now we can add tux to the lp (printer) group. As root, we do:
+
+
+root@slitaz:# addgroup tux lp
+
+
+For the web interface of cups to be properly activated, we still need to change a few things in the ///etc/cupsd.conf// file:
+
+
+root@slitaz:# leafpad /etc/cups/cupsd.conf
+
+
+ 
+   # Administrator user group...
+   SystemGroup lp
+   
+   # Restrict access to the admin pages...
+   
+   Order allow,deny
+   Allow 127.0.0.1
+   
+   
+   # Restrict access to configuration files...
+   
+   AuthType Default
+   Require user @SYSTEM
+   Order allow,deny
+   Deny From None
+   Allow From 127.0.0.1
+ 
+
+To modify permissions on the printer you need to know the details of the bus and device. For this, we do as root:
+
+
+root@slitaz:# lsusb
+
+
+And get the following output:
+
+
+   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+   Bus 001 Device 002: ID 04f9:0027 Brother Industries, Ltd HL-2030 Laser Printer
+
+
+You can now change the permissions on the associated file:
+
+
+root@slitaz:# chmod 666 /dev/bus/usb/001/002
+
+
+And then start cups:
+
+
+root@slitaz:# /etc/init.d/cupsd start
+
+
+We can now configure the printer and fetch the openprinting ppd file for that printer 
+model: http://www.openprinting.org/printer/Brother/Brother-HL-2030 and also add the following 
+packages: foomatic-filters foomatic-db foomatic-db-engine:
+
+
+root@slitaz:# tazpkg get-install foomatic-filters
+root@slitaz:# tazpkg get-install foomatic-db
+root@slitaz:# tazpkg get-install foomatic-db-engine
+
+
+Now we can restart cups and point midori to http://localhost:631
+
+Cups then asks for:
+
+- The login "root" (default tux)
+
+- The corresponding password.
+
+Then navigate to > Printers > Add Printer > click on the printer name that you recognize and do not forget to indicate the path in the connection box: ///dev/bus/usb/001/002// (in my case).
+
+Then go to the web interface of cups ppd and install the new printer using the file Brother HL-2030-hl1250.ppd located in the user's account. Now you can automatically restart cupsd each time you start the system by using System Tools (in the menu) -> Control box -> Initialization and allow the cupsd daemon to run by adding it to the 'Run daemons' section: 
+
+
+dbus hald firewall slim cupsd
+ 
+
+===== Installing a HP Printer =====
+
+This is for a clean installation of SliTaz GNU/Linux cooking-20100314
+
+  - With the printer plugged in and powered on, run 
+# su root
+# tazpkg recharge
+# tazhw setup printer
+  - Install only hplip and hal-cups-utils
+  - The printer should show up in the list of printers displayed as part of this command. It will then attempt to open the CUPS admin pages in Midori (at http://localhost:631 )
+  - On my system, the printer does not show up in the browser under 'Find printers' and I get a 'Forbidden' error when trying to add a printer via the browser
+  - Instead, run # hp-setup and follow the instructions. The test page should print correctly. The printer should also show up in the list of printers in applications (like the text editor) and will also appear in the list of printers on the CUPS browser pages, although in my case it is still not possible to make any changes to it
+
+===== Installing a HP All-In-One Printer/Scanner =====
+
+
+=== Preparation & Packages ===
+
+Power on the scanner before installing the following packages:
+
+  * xsane
+  * sane-backends
+  * libusb
+  * libusb-compat
+  * usbtools
+  * usbutils
+
+You can automate the process with the following Bash command as //root// user:
+for PKG in xsane sane-backends-libusb libusb-compat usbtools usbutils; do 
+tazpkg get-install $PKG
+done
+
+
+=== Detection ===
+
+With those packages installed, use the Hardware Detection Tool (Menu > System Tools > Hardware Detection And Drivers) 
+Click on Scanner button
+
+If your scanner does not show up immediately, enter for none in my set-up; now the scanner device should be listed in purple text, e.g.:
+
+/dev/bus/usb/004/002
+
+=== Verify Permissions ===
+
+Your scanner must be in scanner group with 666 permissions
+
+$ crw-rw-rw-    1 root     scanner  189, 385 Jun 22 19:44 /dev/bus/usb/0 
+
+Reply y to start scanner
+Warning pops up about running scanner as root
+Click continue at your own risk button
+Agree to license
+
+Xsane should open and be working!
+
+The //tux// user is automatically added to scanner group, so tux may scan, but if you run under another user name that user can't scan until you add them to //scanner// group. Do this with the command (as //root//):
+
+# addgroup //username// scanner
+
+===== Links ====
+
+    * http://www.openprinting.org/printers
+
+===== TODO =====
+
+    * Parallel Printer
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Low  |
+|Review| Major Updates  FIXME |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/pxe.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/pxe.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,182 @@
+====== PXE =======
+
+The //Preboot eXecution Environment// (or //PXE//, pronounced 'pixie') is the process of booting a computer from a network connection. It is comparable to booting a LiveCD from a remote CD drive.
+
+This network boot method requires:
+
+    * a server to store files running DHCP and TFTP (each could be on a separate server);
+    * a client with a PXE boot-loader, stored in the BIOS firmware. It maybe disk-less.
+
+\\
+
+===== PXE Server Set-Up =====
+
+A PXE server comprises:
+
+  * a DHCP server to accept clients;
+  * a DHCP boot-file to configure them;
+  * a TFTP server to deliver an OS.
+
+The SliTaz LiveCD can be used as a PXE server. To begin the process, launch the Netbox application (from the System Tools menu).
+
+    * From the //Static IP// tab, click //Start//.
+      *  This box will be the DHCP server. It can't use DHCP to get IP configuration.
+
+Since SliTaz 3.0 the Netbox application is now split into Netbox and Serverbox. If you are running a recent SliTaz version, please read **Serverbox application** instead of **Server tab** below
+
+    * From the //Server// tab, select the  //INETD// sub-tab and ensure the //tftpd// line is **uncommented** in /etc/initd.conf. This is the default behaviour. Click //Start//.
+      *  This will launch the TFTP server, which will deliver the SliTaz LiveCD across the network.
+
+    * From the //Server// tab, select the //PXE// sub-tab.
+
+    * Edit the configuration to add your boot options.
+      *  This will update the DHCP server configuration automatically.
+
+    * From the //Server// tab, select the //DHCP// sub-tab. Check the configuration aligns with your network. The previous step has added the lines //boot_file// and //siaddr//. Click //Start//.
+      *  This will launch the the DHCP server. If clients to do not receive an IP address, check this configuration.
+
+    * Ensure the files //bzImage// and //rootfs.gz// are stored in the // /boot // directory of the LiveCD.
+
+\\ 
+
+===== PXE Client Set-Up =====
+
+Most recent machines with on-board Ethernet have a PXE-capable BIOS. Look for this feature in BIOS menus and BIOS boot menu and ensure it is activated. It may require you press a key, such as F12, during the boot process.
+
+If your computer does not support PXE booting, you can use SliTaz as a client instead. Create a bootable CD-ROM or floppy disk with the // Boot Floppy/CDROM // tool found in the //System Tools// menu.
+
+In PXE Network tab click Write floppy. Use this to boot the client computer.
+
+Is your Ethernet card not recognised? See [[http://rom-o-matic.net/|ROM-O-Matic]]
+
+\\
+
+===== Web Booting =====
+
+The SliTaz LiveCD has configuration settings to start your computer via the Internet. This is useful for using a newer version of SliTaz from older media.
+
+You can start the automatic process with the following command at the SliTaz LiveCD boot-splash:
+
+  web
+
+That's it!
+
+You can find more information on using an Internet connection to boot your computer at the [[http://boot.slitaz.org/|SliTaz Web Boot home-page]].
+
+You will need a DHCP server to get an IP address, netmask, gateway address, as per a normal network connection -- a standard home router should be sufficient for this.
+
+\\
+
+=== PXE boot without DHCP server: Web Boot & Command Line ===
+
+If you have no device that can function as a DHCP server, you need an IP address with a netmask, a gateway address and, optionally, a DNS address. 
+
+title Slitaz Web
+  kernel /boot/gpxe ip=192.168.0.12/24 gw=192.168.0.1 dns=192.168.0.1 url=http://mirror.slitaz.org/pxe/pxelinux.0
+
+
+You can modify the URL thus:
+
+title Slitaz Web
+  kernel /boot/gpxe ip=192.168.0.12/24 gw=192.168.0.1 dns=192.168.0.1 url=ip=192.168.0.12/24 gw=192.168.0.1
+  dns=192.168.0.1 url=http://mirror.slitaz.org/pxe/pxelinux.0
+
+
+Note that only the following keywords are recognised:
+
+  * ip=
+  * gw=
+  * dns=
+  * url=
+  * nodhcp (useful to avoid a DHCP timeout error)
+
+\\
+
+===== Advanced Web Booting Configuration =====
+
+The Web Booting process can be embedded into routers and other devices, as well as being customised.
+
+\\
+
+=== Embedded Web Boot, with PXE boot PROM (PXE forwarder) ===
+
+Configure a PXE server with http://download.tuxfamily.org/slitaz/boot/gpxe.pxe as the boot file, a 42Kb second stage loader. This was successfully tested with an [[http://openwrt.org/|OpenWRT]] router:
+
+    * install http://mirror.slitaz.org/boot/mips/tftpd (mips version) in /jffs/usr/sbin
+    * install gpxe.exe in /jffs/boot
+    * add dhcp bootfile option in dnsmasq config file
+
+  # echo "dhcp-boot=gpxe.pxe" >> /tmp/dnsmasq.conf
+
+launch the tftp server for your lan (say 192.168.0.1/24)
+
+  # /jffs/usr/sbin/tftpd 192.168.0.1 /jffs/boot
+
+\\
+
+=== Modifying the Default GPXE Web Boot URL ===
+
+The URL is stored at offset 519 in 255 bytes max.
+
+  * Show the current URL with:
+
+  $ dd bs=1 skip=519 count=255 if=gpxe 2> /dev/null | strings
+
+  * Change the URL with:
+
+  $ echo -n "http://myurl.org/myboot" | cat - /dev/zero | dd conv=notrunc bs=1 seek=519 count=255 of=gpxe
+
+  * Change the URL and IP configuration with:
+
+  $ echo -n "ip=192.168.0.10/24 gw=192.168.0.1 dns=192.168.0.1 url=http://myurl.org/myboot" | cat - /dev/zero | dd
+  conv=notrunc bs=1 seek=519 count=255 of=gpxe
+
+  * Remove URL to behave as a normal GPXE with:
+
+  $ dd if=/dev/zero conv=notrunc bs=1 seek=519 count=255 of=gpxe
+
+\\
+
+=== Hack the gpxe.pxe Default Web Boot URL ===
+
+The URL is stored at offset 5 in 255 bytes max.
+
+Show the current URL with:
+
+  $ dd bs=1 skip=5 count=255 if=gpxe.pxe 2> /dev/null | strings
+
+Change the URL with:
+
+  $ echo -n "http://myurl.org/myboot" | cat - /dev/zero | dd conv=notrunc bs=1 seek=5 count=255 of=gpxe.pxe
+
+Remove the URL and behave as a normal //gpxe.pxe// with:
+  $ dd if=/dev/zero conv=notrunc bs=1 seek=5 count=255 of=gpxe.pxe
+
+\\
+
+=== Using Redundancy with Web Boot Servers ===
+
+Comma separated URL lists are supported.
+
+The PXE client will try to load the first URL. If the load fails, it will try the next URL, and so on.
+
+Example with current Slitaz Web boot servers :
+
+  $ echo -n "http://mirror.slitaz.org/pxe/pxelinux.0,http://mirror.switch.ch/ftp/mirror/pxe/pxelinux.0,http:
+  download.tuxfamily.org/slitaz/pxe/pxelinux.0" | cat - /dev/zero | dd conv=notrunc bs=1 seek=519 count=255 of=gpxe
+
+ 
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Improve readability |
+|:::           | Section in to Client/Server, with Simple/Advanced in each |
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/qemu.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/qemu.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,64 @@
+====== QEMU ======
+
+===== Introduction =====
+
+QEMU provides a virtual machine that will run within XP. Refer to the QEMU documentation for a detailed description of the virtual hardware.
+
+It allows to test an operating system environment without actually installing it and without rebooting out of XP; e.g. you can test Slitaz this way, before deciding if you want to install it on your machine.
+
+Compared with Virtual Box (which I am also using regularly), QEMU is initially much faster and easier to set up. You will also have less problems if you are somewhat memory constrained (which you are, if you have less than 1.0 or 1.5 GB RAM). Performance wise, both virtualization platforms looked similar to me (although way slower than a native install). 
+
+If you just want to try Slitaz within your XP environment, prefer the QEMU solution described here (unless VirtualBox is already installed and set up on your machine).
+
+===== Getting started =====
+==== Requirements ====
+This works on XP with Slitaz 3.0 (should work with all versions of Slitaz). 
+
+==== Install QEMU ====
+Go to Pendrivelinux.com  and download the QEMU PC hardware emulator installer (QPU804.exe).
+This executable is actually a self-extracting archive. When you run it you just need to tell the installer where to unzip the contents (which may be on your hard disk or on a flash drive). The result will be a folder named QPU804.
+
+The QEMU setup can execute any ISO that you put in that folder.
+Copy the SliTaz ISO to that folder.
+You now have a virtualized SliTaz installation that can run alongside Windows.
+
+==== Start QEMU ====
+Execute QPU804.bat (double click on it from an explorer window) to start your virtual machine (it will advertise it is running Ubuntu, but really it will run the ISO you copied to that folder, Slitaz.iso in this case).
+
+You will see your virtual machine booting from the ISO file, as if it would be booting from a Slitaz LiveCD. Refer to other parts of the Slitaz documentation for a detailed presentation of what you can do from there.
+
+==== Getting in and out of the QEMU Window ====
+To move the mouse out of the QEMU screen window press ctrl, keep it pressed and press the alt key simultaneously. To go back, just left click in the window.
+
+==== Shared Folder ====
+Open a pcmanfm window: the Slitaz partition labeled "QEMU VVFAT" refers to the same physical (shared) location as the XP "QPU804\shared folder" folder. 
+
+==== Screen resolution ====
+My screen resolution was 800x600. You may want to read the QEMU documentation and play around with the available options from both QEMU and Slitaz to get a higher resolution.
+
+To get a full screen Slitaz, try adding the -full-screen option to the qemu command line of the QPU804.BAT file.
+
+===== I want to keep the changes I made in Slitaz =====
+
+==== Private data ====
+Copy any private data created in Slitaz to the shared directory: it will survive a virtual machine reboot.
+
+==== Keeping system changes ====
+Two ways to do this: 
+  * create a new iso with your changes, or 
+  * install Slitaz in a qemu virtual drive
+
+
+== Create an ISO file with your system changes ==
+In the Slitaz menu select //System Tools-> Create a LiveCD// (refer to the LiveCD section of the documentation).
+
+The writeISO panel will create a bootable image of Slitaz with any changes you made, and will store this image file as /home/slitaz/distro/slitaz.iso. 
+
+In the Slitaz environment, copy-paste that slitaz.iso file to the shared folder. Then from XP you will be able to copy the slitaz.iso file from the QPU804\shared folder to the QPU804 folder, replacing the existing ISO file (delete the old .iso file if it has a different name). Next time you start QEMU, it will boot from your new ISO which brings you back to the same environment.
+
+
+== Install Slitaz in a qemu virtual drive ==
+
+Alternatively, refer to the QEMU documentation to start QEMU with a "virtual disk" file, where you will be able to install Slitaz by using the menu item //System Tools -> Slitaz Installer//. 
+
+(Not tested with Slitaz but tested with other systems in the past)
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/remotedesktop.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/remotedesktop.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,110 @@
+===== Remote Desktop =====
+
+\\
+
+==== NoMachine (NX) ====
+
+This section is under construction and has not been verified by others. It has been created from one particular (working) configuration.
+
+[[http://www.nomachine.com|NoMachine]] (NX) is a propietary remote desktop system, supporting multiple hosts and keypair-based log-ins.
+
+This guide assumes you have a working SSH configuration for remote access. NoMachine/NX channels authentication and encrypted communications through SSH. This can be via password authentication or an RSA key pair; NoMachine/NX uses a DSA key pair to authenticate.
+
+My ([[http://forum.slitaz.org/index.php/profile/20/seawolf|seawolf]]) personal SSH configuration uses a non-standard port and key pair-based, password-less authentication. The differences in this guide to a standard, password-protected SSH configuration using port 22 are irrelevant as the default is given initially.
+
+There are three parts to a NX system:
+  - the **server** is the machine to which you connect;
+  - the **node** is one in a group of resources that hosts your session - this can be the server;
+  - the **client** that connects to a server (and in turn, the node).
+
+\\
+
+=== Download the Software ===
+
+There are three packages available to [[http://www.nomachine.com/download-package.php?Prod_Id=2071|download]] from NoMachine. All clients must have installed the client package, whereas all three packages must be installed on servers and nodes. This is because parts of the client package is used by the node, parts of which are used by the server.
+
+  * Decompress the three NX packages (client, node, server) on the server into ''/usr'' to create ''/usr/NX'' directory.
+  * Decompress the client package on the client(s).
+
+\\
+
+=== Server Configuration ===
+
+The automated commands are not compatible with BusyBox and the SliTaz configuration, so the installation commands need to be edited:
+  * Create the symlinks ''/etc/rc.d/rc#.d/'' all pointing to ''/etc/init.d/''. This can be easily achieved with the following command performed as the //root// user:
+  * ''for NUM in 0 1 2 3 4 5 6 ; do cp /etc/rc.d/init.d /etc/rc.d/rc$NUM.d; done''
+
+  * Modify ''/usr/NX/scripts/setup/nxserver'' by:
+      * fixing the user add/del commands in lines 924, 963, 984.
+      * comment out the command in line 956 by placing a hash immediately after the opening quotation mark (command not needed)
+  * Install the server: ''sudo /usr/NX/scripts/setup/nxserver --install fedora''
+      * the OS doesn't really matter but it's the closest match for the numerous /etc/init.d commands
+  * Change the server name & SSH port (if necessary) in ''/usr/NX/etc/server.cfg'' (line 31, 36 & 236)
+  * Allow administrative logins in line 87 of ''/usr/NX/etc/server.cfg''
+
+\\
+
+=== Node Configuration ===
+
+The automated commands are not compatible with BusyBox and the SliTaz configuration, so the installation commands need to be edited:
+  * Modify ''/usr/NX/scripts/setup/nxnode'' by:
+      * specify SSH port in line 43 (if necessary)
+      * change to ''local.sh'' on line 1305
+
+  * Install the node: ''sudo /usr/NX/scripts/setup/nxnode --install fedora''
+      * ignoring warning about CUPS detection if you don't have a printer
+  * Change server name & SSH port (if necessary) in'' /usr/NX/etc/node.cfg'' (line 32, 342)
+
+\\
+
+=== User Configuration ===
+
+  * Enable the nx user account by using: ''sudo passwd -u nx''
+  * Confirm this with: ''sudo /usr/NX/bin/nxserver --usercheck //username//''
+
+
+NX> 900 Verifying public key authentication for NX user: //username//.
+NX> 900 Adding public key for user: //username// to the authorized keys file.
+NX> 716 Public key added to: /home/ //username// /.ssh/authorized_keys2.
+NX> 900 Verifying public key authentication for NX user: //username//.
+NX> 900 Public key authentication succeeded.
+NX> 999 Bye.
+
+
+You should now be able to log-in to the server/node using a normal username and password.
+
+\\
+
+=== Recreating Keys ===
+
+When the default key pair authenticates correctly, they should be regenerated for security reasons. Issue the following command to create a new key pair:
+''sudo /usr/NX/bin/nxserver --keygen''
+
+New keys should be created. Distribute the secret key ''/usr/NX/share/keys/default.id_dsa.key'' to clients and import it in the client GUI (Configure > General > Server > Key... > Import).
+
+Restart the server (''sudo /usr/NX/bin/nxserver --restart'') to complete the changes.
+
+\\
+
+=== Tips ===
+
+  * If you want to use key pair and password-less authentication, ammend ///etc/ssh/sshd_config// with:
+PasswordAuthentication no
+AllowUsers nx //other usernames//
+
+  * Open ports 5000-5200 for an unencrypted connection. This is because after a successful authentication has taken place the client reconnects to a display in the range starting at 'DisplayBase' up to the value ('DisplayBase' + 'DisplayLimit'). These parameters default to the values "1,000" and "200" respectively and TCP port numbers are obtained by adding the value "4,000" to the display numbers, thus giving 5000 and 5200. If encrypted display is enabled, all traffic is piped through SSH.
+
+  * If the client fails to connect to the server with the following messages:
+ 
+
+NX> 203 NXSSH running with pid: //PID//
+NX> 285 Enabling check on switch command
+NX> 285 Enabling skip of SSH config files
+NX> 285 Setting the preferred NX options
+NX> 200 Connected to address: //IP address// on port: //SSH port//
+NX> 202 Authenticating user: nx
+NX> 208 Using auth method: publickey
+NX> 204 Authentication failed.
+
+
+then the ''/usr/nx/home/nx/.ssh/authorized_keys2'' file is likely at fault.
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/sdcard.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/sdcard.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,94 @@
+====== Installing SliTaz to a MMC/SD-card ======
+SliTaz can be installed to a MMC/SD flash-memory card (the kind used in digital cameras) in either of two ways: in a LiveUSB version as used on a "memory-stick" (also called "thumb-drive", "flash-drive", or a variety of other names), or as a regular install as used on a hard-drive. There are advantages and disadvantages to both methods.
+
+===== LiveUSB-type installation =====
+A memory-stick uses NAND flash memory which eventually wears out after about 100,000 read/write cycles. SliTaz tries to minimize this wear, and thus prolong the life of the memory-stick, by storing the entire main root-file-system ("rootfs") as a compressed image in one file (rootfs.gz), then uncompressing it into the machine's memory (RAM) when booting. Only the /home directory is normally written onto the memory-stick, unless the user issues this command:
+
+# tazusb writefs [compression]
+
+Where "[compression]" can be "lzma", "gzip", or "none". This command re-writes the rootfs.gz file onto the memory-stick, so that changes made to the system can be saved and used again at the next boot-up. The big advantage to using this method is obviously that it prolongs the life of the USB device. The big disadvantage is that booting takes a long time because of the use of compression, and the more packages you install to your rootfs system the longer it takes to boot. The rootfs can also be saved without compression (i.e., # tazusb writefs none), which will allow it to boot much faster. This was not such a good option when SliTaz 1.0 was released in 2008, because memory-sticks had much less storage space then, but with 4 GB memory-sticks common now, it's not as much of a problem. This same method can be used to install SliTaz to a MMC/SD card.
+
+===== Regular "hard-drive"-type installation =====
+The other option is to treat the MMC/SD card as if it were a real hard-drive, and simply use:
+
+# gparted
+
+to format the card and set up partitions like on a regular hard-drive, and
+
+# slitaz-installer
+
+to do the actual installation. Be sure to also allow the installer to install GRUB onto the card, so that you can boot from it the normal way, same as you would from a regular hard-drive.
+
+===== Example as used on my own Asus Eee-PC =====
+The SliTaz installation which I put onto a MMC/SD-card (16 GB) was for my Asus Eee-PC 701, leaving the Eee's original Xandrox Linux installation intact on its SSD (solid-state drive), and keeping the MMC/SD-card with SliTaz always in the card-reader slot. The Eee's BIOS needed to be changed to allow the SD-card to be the first boot device, so that the machine would boot into GRUB before anything else. The /boot/grub/menu.lst is setup to allow me to boot from either Xandros or SliTaz on the GRUB menu:
+
+# /boot/grub/menu.lst: GRUB boot loader configuration.
+#
+
+# By default, boot the first entry.
+default 0
+
+# Boot automatically after 8 secs.
+timeout 8
+
+# Change the colors.
+color yellow/brown light-green/black
+
+# To boot newest slitaz from : /dev/sdb5
+#
+title  SliTaz GNU/Linux (cooking - kernel 2.6.30.6)
+  root (hd0,4)
+#  kernel /boot/vmlinuz-2.6.30.6-slitaz rootdelay=10 root=/dev/sdb5
+# the kernel line used to be necessary
+# but apparently a later upgrade of SliTaz commented it out
+# GRUB boots into SliTaz with no problem using only the root (hd0,4) command
+
+# To boot Asus eee pc Xandros
+#
+title Xandros (kernel vmlinuz-2.6.21.4-eeepc)
+  root (hd1,0)
+  kernel /boot/vmlinuz-2.6.21.4-eeepc quiet rw vga=785 irqpoll i8042.noloop=1 root=/dev/sda1
+  initrd /boot/initramfs-eeepc.img
+
+
+The first 3 partitions on my MMC/SD-card were originally used as storage for various parts of the Eee's Xandros system, with the 4th partition formatted as an Extended Partition and further divided into two, with Partition 5 used for the SliTaz install and Partition 6 for Linux-Swap. But because this SliTaz installation has become my main one for the Eee, as I added more packages I finally decided to move parts of the SliTaz filesystem to other partitions and use this layout:
+
+$ df -h
+Filesystem                Size      Used Available Use% Mounted on
+rootfs                    1.4G    413.3M    913.1M  31% /
+/dev/root                 1.4G    413.3M    913.1M  31% /
+tmpfs                   500.7M         0    500.7M   0% /dev/shm
+/dev/sdb2                 3.0G      1.4G      1.6G  46% /usr
+/dev/sdb3                 2.5G      2.1G    323.0M  87% /home
+/dev/sdb1                 7.4G      5.2G      1.9G  73% /home/shared
+
+
+The /home/shared directory is one which has documents shared by the Xandros system.
+
+The Eee-PC was already set-up to recognize and read the MMC/SD-card. But one day I accidentally moved the whole contents of /boot to another directory and thus was unable to boot SliTaz. When I inserted the card into a Toshiba Satellite A215-S5850 laptop (my biggest, most modern, and main laptop), I was surprised to find that the machine did not see the MMC/SD-card. It was necessary to add a kernel package:
+
+# tazpkg get-install linux-mmc
+
+and then to load this module:
+
+# modprobe mmc_block
+
+After that, SliTaz was able to read the contents of the MMC/SD-card, and I was able to move the /boot files back to where they belonged and fix the system. If the output of
+
+# lsmod
+
+does not show mmc_block, then that module must be loaded manually. To have SliTaz always load it at boot-up, simply add it to the LOAD_MODULES line of /etc/rcS.conf.
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/sexydesktop.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/sexydesktop.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,74 @@
+====== Sexy desktop apps and config ======
+
+===== Introduction =====
+
+This page provides information about creating a beautiful desktop, available applications via the SliTaz package manager and configuration file examples or tweaks.
+Wbar and Tint2 desktop
+
+First install the used packages:
+
+    * wbar
+    * tint2
+    * nitrogen
+    * cairo-clock
+
+We have to create, modify or configure 3 files in your personal home directory (click on the link to download files or check the bottom of the page):
+
+    * //~/.wbar//
+    * //~/.config/tint2/tint2rc//
+    * //~/.config/openbox/autostart.sh//
+
+Wbar and Tint2 configuration files don't exist if you've never started the applications before, but Openbox autostart scripts should exist since it is the default Window Manager on SliTaz. Save the attached config files and put them in the correct directory.
+
+The cairo analog desktop clock needs the "Composite" extension enabled and a composite manager running (both activated by default on SliTaz). If you use Xorg you must adjust your xorg.conf file. The composite manager we use in Slitaz is called xcompmgr, it is light and has some command line options for shadows, etc.
+
+To automatically execute all applications when your X session starts you must edit the Openbox autostart script with your favorite editor or use the GUI //$(desktopbox autostart)// to add the following lines:
+
+
+# Start the Freedesktop standard menu panel.
+#lxpanel &
+
+# Tint2 - Simple and clean panel.
+tint2 &
+
+# Desktop Wallpaper with Nitrogen.
+nitrogen --restore &
+
+# Desktop effects composer (xcompmgr -c -r 10 &).
+xcompmgr &
+
+# Wbar icons panel.
+(sleep 4 && wbar -above-desk -bpress -pos top center -isize 24 -jumpf 0 -zoomf 2.0 -balfa 0) &
+
+# Nice clock for the desktop.
+(sleep 2 && cairo-clock) &
+
+
+Make sure to comment out lxpanel and modify PCmanfm preferences to let Nitrogen handle the desktop background. To choose your image:
+
+ $ nitrogen /usr/share/images 
+
+Now logout and login again into your customized desktop. Or kill the current process and then restart the applications:
+
+
+$ killall lxpanel
+$ tint2 &
+$ wbar -above-desk -bpress -pos top center -isize 24 -jumpf 0 -zoomf 2.0 -balfa 0 &
+
+{{ :en:guides:image:wbar-tint2-desktop.preview.png?100|Click to Preview}}
+[[http://savedonthe.net/download/185/dot.html|Link to download .wbar file]]
+[[http://savedonthe.net/download/186/tint2rc.html|Link to download tint2rc file]]
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/start.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/start.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,138 @@
+====== Guides ======
+
+The SliTaz GNU/Linux quick start and complete guides by the community. You will find here specific guides to software, hardware or system configurations written by SliTaz users and contributors. These guides aim to provide concise and correct instructions. They explain a precise example of a solution and don't expect to be a general how-to.
+
+
+===== General =====
+   * [[newbie | SliTaz Newbie Guide]] 
+   * [[read | README ]] - Before you post a question in the Community Forum
+   * [[contributor | Contribute to Slitaz]] - Guidelines to become a SliTaz Contributor
+   * [[bugs | Most Annoying Bugs ]]
+   * [[faq | FAQ]]
+   * [[testingapps | Testing Packages]] - Quality Management
+   * [[ http://scn.slitaz.org/image | Artwork]] - Showcase your screenshots, wallpaper, themes and other Artwork 
+
+===== Installation, flavors and virtualization =====
+  * [[pxe|PXE boot]] - Boot from the web
+  * [[lowramcd|Live CD for low RAM systems]]
+  * [[frugal|Frugal install to Windows partition ]]
+  * [[uncommoninst|Unusual install methods]]
+  * [[liveusb| LiveUSB]]- Installation to a USB flash drive 
+  * [[dvd|Offline DVD]] - All Slitaz resources on one DVD 
+  * [[sdcard|SD Card]] - How to install SliTaz to a MMC/SD flash memory card
+  * [[ http://pizza.slitaz.org/ | Online builder ]] - Create a flavor using Pizza
+  * [[manyinone | Create many-in-1 flavors]]
+  * [[internationalization | Internationalization ]] - Add language support and create your own language flavor
+  * [[qemu | Qemu ]] - SliTaz GNU/Linux with Qemu
+  * [[vmware| VMware]] - SliTaz GNU/Linux with VMware
+  * [[virtualbox | Virtualbox]]- SliTaz GNU/Linux with virtualbox
+  * [[netstart|Net start usage and immediate installation on hard disk]]
+  * [[http://blog.bodhizazen.net/linux/how-to-install-slitaz-with-ext4-and-grub2/|Grub2]] - Install SliTaz with grub2 (and ext4)
+
+
+===== Networking / LAN =====
+  * [[wifi-easy|Wifi easy]] - Easy way to configure wifi
+  * [[wifi-hard|Wifi hard]] - Hard way to configure wifi
+  * [[network-script|Network.sh script]] - The /etc/init.d/network.sh file
+  * [[vpn|VPN]] - Build your own Virtual Private Network
+  * [[dialup | 3G/Dialup]] - How to get your 3G modem working
+  * [[modem | Modem]] - Modem dialup with ppp or wvdial
+  * [[bluetooth|Bluetooth]] - Configure bluetooth
+  * [[samba | Window Networking with Samba]]
+  * [[remotedesktop | Remote Desktop ]] - NX software from NoMachine 
+
+===== SliTaz tinyutil Boxes =====
+  * [[tazpkgbox | Tazpkgbox]] - Package Manager GUI
+  * [[tazctrlbox | Tazctrlbox]] - SliTaz system administration GUI
+  * [[tazlitobox | Tazlitobox]] - GUI to generate LiveCD/flavors
+  * [[tazusbbox | Tazusbbox]] - GUI to generate LiveUSB
+  * [[tazhwbox | Tazhw box]] - Hardware detection and driver installation
+  * [[mountbox | Mountbox ]] - Graphically access and mount filesystems 
+  * [[burnbox | Burnbox]] - Burn CDs/VCDs/DVDs
+  * [[wifibox | Wifibox]] - Wireless Configuration
+  * [[netbox | Netbox]] - Ethernet/PPP/VPN/DHCP/Static IP configuration
+  * [[serverbox | Serverbox]] - Manage servers and/or firewall 
+  * [[scpbox | Scpbox]] - Copy securely using scp
+
+===== Software =====
+  * [[recommended | Recommended Software Packages]] - Applications to do almost anything on Slitaz
+  * [[flash|FlashInstall]] - How to install Adobe Flash Player 
+  * [[boottime|Super Fast Boot]] - Super fast boot time 
+  * [[burncd | Burn CD / DVD]] - Burn CD/DVD audio/video 
+  * [[backup| Backup ]] - How to make backups on CD / computer
+  * [[Midori|Midori]] - Midori Tips and Tweaks 
+  * [[panels | Panels and Launchers ]]
+  * [[arts | Themes, Wallpaper, Icon sets ]]
+  * [[fonts | Useful Fonts ]]
+  * [[sexydesktop| Sexy Desktop]] - Desktop apps and config
+  * [[conky | Conky ]] 
+  * [[audioplayers | Audio Players ]]
+  * [[videoplayers | Video Players ]]
+  * [[soundconvert | Sound and Video Conversion]] - Sound/Video conversion, Audio creation and synthesis
+  * [[importphotos | Import photos from digital camera]] - using gphoto2 
+  * [[dropbox | Dropbox ]]
+  * [[tor|Tor]] - The Tor Install Guide without blah-blah
+  * [[conspy|Conspy]] - Tiny session manager or shared console
+  * [[wicd | Wicd]] - Lightweight network manager
+  * [[grub | Grub and Grub2]]
+  * [[alsaequal | Alsaequal]] - Real-time adjustable equalizer plugin for ALSA
+ 
+
+===== Hardware =====
+  * [[xorg/xvesa | Xorg/Xvesa]] - What to do if X is will not start or has the wrong resolution
+  * [[nvidia|Nvidia]] - Install the latest non-free Nvidia driver
+  * [[ati | ATI]] - Install the latest non-free catalyst ATI driver
+  * [[webcam | Webcam]] - How to get webcam working
+  * [[printer | Printing]] - Howto print, CUPS install and configuration
+  * [[scanner | Scanning]]
+  * [[udev | UDEV and HAL]]
+  * [[troubleshoot | Troubleshoot]]
+  * [[powermgmt | Power Management ]] - ACPI (Advanced Configuration and Power Interface)
+  * [[CPU-frequency | CPU Frequency Scaling]] - CPU Frequency Scaling instructions
+
+===== Server setup and system Administration =====
+  * [[apache | Apache Webserver ]]
+  * [[lighttpd | Lighttpd Webserver]]
+  * [[ssh | Dropbear, Openssh ]]
+  * [[mailman | Mailserver and Mailman]]
+  * [[database|Database engine]] - SQLite, MySQL and other DB management systems
+  * [[redmine | Redmine Setup ]]
+  * [[mercurial | Mercurial Installation ]]
+  * [[en:handbook:server-apps#drupal|Drupal]] - Powerful CMS engine using PHP/MySQL
+  * [[streaming | Media Streaming Server ]]
+  * [[encryption | File, Drive Encryption ]]
+  * [[firewall | Firewall]]
+  * [[router | Router and Internet Gateway ]]
+
+
+===== Window Managers=====
+  * [[en:handbook:wm#dwm|DWM]] 
+  * [[en:handbook:wm#pekwm|Pekwm]]
+  * [[fluxbox | Fluxbox ]]
+  * [[en:handbook:wm#xfce | Xfce ]]
+ 
+ 
+
+===== Kernel and SliTaz Build system =====
+  * [[kernel|CustomKernel]] - Build your own custom Linux Kernel
+  * [[en:guides:linuxpkgs | linux-* packages]] - Explanation of various linux packages
+  * [[chroot|Chroot]] - How to setup a chroot to cook packages
+  * [[tazwoktips | Tips for compiling with Tazwok ]] - Build packages for SliTaz more effectively
+
+===== Playground =====
+  * [[playground|Playground]] - For testing purposes only
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Low  |
+|Review| Major Updates FIXME  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly, e.g.,|
+|::: | [[en:guides:start | Add link]]|
+|::: | Add new rows like this ;-)  |
+
+\\
+----
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/tazwoktips.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/tazwoktips.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,38 @@
+====== Tazwoktips ======
+
+You must read the [[http://doc.slitaz.org/en:cookbook:start|Cookbook]] first - it's a great collection of documents. This guide supplements the cookbook with some tips that you are most likely to face while compiling packages for SliTaz.
+
+===== Tips =====
+
+  - Add the "slitaz-dev-pkgs" package - it's a meta package that adds some of the useful *-dev packages
+  - Compilation Errors like 
+        * checking for $PKG... configure: error: Couldn't find $PKG >= 1.0.0,
+        * configure: error: Couldn't find $FILENAME
+        * use: "tazpkg search-pkgname $FILENAME" to find the package with the missing file; Add this package to the BUILD_DEPENDS in the receipt
+  - Read receipts of the other packages for standardization. The problems you face may already have a solution in one of these receipts. Some example receipts include: 
+       * xorg-libSM (or any xorg-*) : to use a $SOURCE variable
+       * cups : to strip files other than .so in usr/lib, and to compress some driver files
+       * ndiswrapper-driver or broadcom-wl : to cook linux modules
+       * mplayer-svn : to create packages from a svn/git repository
+       * 915resolution or busybox : to add patches
+       * nvidia : to create non-free packages that need the linux package for compiling modules
+       * get-* : to create non-free packages
+       * *-dev : to see how to create a dev receipt
+  - Create lighter packages. Always remember to disable gnome dependencies or any other dependencies that are not so useful. Always use "configure --help" to see the compile options. Many packages have auto-dependency tracking, i.e., if it finds a corresponding *-dev package installed on the system, it will auto-enable an option. So, if you don't disable an unwanted dependency, then when a package is cooked on the SliTaz tank server, it is likely that the package won't run properly because of the missing dependency. The missing dependency problems that are often reported on the forum are caused due to this problem. 
+  - Missing .pc files : Sometimes a dev package created upstream misses .pc files, so pkg-config cannot locate the corresponding dev files correctly. This can play havoc sometimes as you expect the upstream packages to be properly distributed. firefox-dev is one such example.
+  - gcc4.4 patches : The new stricter format of gcc4.4 breaks many packages. This is quite a common problem. You need to either create a simple patch or see if a new upgrade is available upstream. See mplayerplug-svn. 
+  - Use a chroot environment and keep it clean so that you can submit the receipt with the correct BUILD_DEPENDS. 
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/testingapps.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/testingapps.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,31 @@
+======= Testing Applications =======
+Not started yet - this is only a suggestion to discuss in the forum
+
+As a result of [[http://forum.slitaz.org/index.php/discussion/668/testing-packages/#Item_23|discussions in the forum]], this is the page for documentation - please take part and report any troubles with packages here.
+
+===== system-tools =====
+
+^  Package  ^  Maintainer  ^ Tester ^  Status  ^  Problems  ^  Link ^
+|Midnight Commander|~|kultex|tested|ok|~|
+|pcmanfm|~|~|not tested|~|~|
+
+===== x-window =====
+
+^  Package  ^  Maintainer ^ Tester ^  Status  ^  Problems  ^  Link  ^
+|xorg-xf86-video-intel|~|kultex|tested|should be updated to 2.7.1\\ update in progress|http://hg.slitaz.org/wok/rev/c86710039a5f|
+|xorg-xf86-video-nv|~|kultex|started|~|~|
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Poor FIXME |
+|Review| Major Updates or DELETEME |
+|Priority| Low |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly, e.g.,|
+|::: |  [[http://labs.slitaz.org/wiki/packages | New test guidilines are here]]|
+|::: | Add new rows like this ;-)  |
+
+\\
+----
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/tor.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/tor.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,42 @@
+====== The Tor Install Guide without blah-blah ======
+
+===== Installation =====
+
+# tazpkg get-install tor
+# tazpkg get-install privoxy
+# echo 'forward-socks4a /        127.0.0.1:9050   .' >> /etc/privoxy/config
+# sed -r '/RUN_DAEMONS/s/(" *)$/ privoxy\1/' -i /etc/rcS.conf 
+# echo 'tor > /dev/tty2 & ' >> /etc/init.d/local.sh
+
+
+Use Bridges to get tor working if the options above are not working.
+
+
+# echo '
+UseBridges 1
+UpdateBridgesFromAuthority 1
+bridge 66.160.141.98:6085 ' >> /etc/tor/torrc
+
+
+===== Reboot system and relogin. =====
+
+Login to tty2 (Ctrl+Alt+F2 gets you into tty2; Alt+F7 back to the Desktop) to check if it works or not.
+If it shows Success... then this means it works.
+
+Then install the "tor button" plugin for Firefox.
+
+Over the Wall, you can touch everywhere in the world.
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Medium  |
+|Review| Minor Updates  |
+|Priority| Low |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Introduction is missing|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/uncommoninst.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/uncommoninst.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,288 @@
+====== Unusual install methods ======
+
+The //slitaz-installer// installs SliTaz in a partition or a hard drive as most Linux distributions do. However, there are many other ways to install SliTaz...
+
+===== Frugal install =====
+
+You don't need a special partition, the system runs in RAM like a Live CD...
+
+See [[http://doc.slitaz.org/en:guides:frugal#traditional-frugal-install|frugal install]] and [[http://doc.slitaz.org/en:guides:frugal#iso-image-install|ISO image install]]
+
+...it can be tuned to your needs a little bit.
+
+See [[http://doc.slitaz.org/en:guides:frugal#tuning-the-boot-process|tune boot]]
+
+You can also use a LORAM flavor created with //tazlitobox// and //The filesystem is always in RAM//...
+
+...or //The filesystem may be on a small CDROM//. Install the CD-ROM files // /boot/bzImage // and // /boot/rootfs.gz // and copy the // /rootfs.gz //. Say into // /this/directory //. Now get the label of the partition. Say mypartition:
+  # blkid
+And append the param //loram=// to the cmdline:
+
+kernel (hd1)/boot/bzImage rw root=/dev/null vga=normal loram=LABEL=mypartition,this/directory
+
+
+You can also use a device name (loram=/dev/hda2,this/directory). The device name may vary with the kernel version (hda or sda) and USB keys.
+
+===== USB key install =====
+
+==== Tazusb ====
+
+This is a mix between a frugal and traditional install. The system runs fully in RAM but the // home // directory is always on the key. You can modify the system (configure, install packages) and then save the new system on the key 8-).
+See [[http://hg.slitaz.org/tazusb/raw-file/tip/doc/tazusb.en.html|tazusb manual]]
+
+==== Hybrid ISO ====
+
+This install method will **erase all of your key** and install a **unmodifiable** :-/ SliTaz. You can create a custom system with //tazlito// or //tazlitobox//. Each Slitaz ISO image is [[http://doc.slitaz.org/en:guides:dvd#hybrid-iso|hybrid]].
+
+===== Loop install =====
+
+If you want to install SliTaz on a disk (not a frugal install), and you don't want to create a partition for SliTaz, but you have enough room in a feature-poor filesystem (FAT32 or NTFS)...
+
+... create a loop file and install SliTaz into it!
+
+The problem is: what size? 200MB should be the minimum. Imagine, you could like it and install many more packages!
+
+==== Loopfile creation ====
+
+You can create the loop file with **mountbox** (click loop, enter the file name, then click create, enter the size, the units, click create) or with the command line:
+  # dd if=/dev/zero bs=1M count=200 of=slitaz.fs
+
+You now need to create a filesystem in this loopfile:
+  # yes | mke2fs -j slitaz.fs
+
+Later, if the loopfile is too small you can extend it (assuming you don't boot from the loopfile, but a Slitaz Live CD for example):
+  # dd if=/dev/zero bs=1M count=100 >> slitaz.fs
+  # resize2fs slitaz.fs
+
+==== Root filesystem files installation ====
+
+Copy files from the rootfs.gz archive of a cdrom into the loopfile:
+  # mount /dev/cdrom /media/cdrom
+  # mount -o loop,ro slitaz.fs /media
+  # unlzma -c /media/cdrom/boot/rootfs.gz | ( cd /mnt; cpio -idmu )
+  # umount -d /mnt
+  # umount /media/cdrom
+
+==== Boot setup ====
+
+Get a **preinit** iso file with same version (the kernel version must match the modules version in the root filesystem).
+The partition storing the loopfile (say /dev/hda1) and its path into the partition (say /data/slitaz.fs) is defined by the **mount** and **loopfs** arguments:
+
+title SliTaz cooking
+  map (hd0,0)/boot/slitaz-preinit.iso (hd1)
+  map --hook
+  kernel (hd1)/boot/bzImage mount=/dev/hda1 loopfs=data/slitaz.fs
+  initrd (hd1)/boot/rootfs.gz
+
+The loop install does not use exotic packages from preinit. You can use any SliTaz flavor (except lorams).
+
+You can built an up-to-date **preinit** iso anytime with# tazlito get-flavor preinit
+# tazlito gen-distro
+
+title SliTaz cooking in loop file
+  map (hd0,0)/boot/slitaz-cooking.iso (hd1)
+  map --hook
+  kernel (hd1)/boot/bzImage mount=/dev/hda1 loopfs=data/slitaz.fs
+  initrd (hd1)/boot/rootfs.gz
+  
+title SliTaz cooking in RAM (like the Live CD)
+  map (hd0,0)/boot/slitaz-cooking.iso (hd1)
+  map --hook
+  kernel (hd1)/boot/bzImage rw root=/dev/null autologin
+  initrd (hd1)/boot/rootfs.gz
+
+Or, you can replace the device name of the mount variable by the UUID or LABEL returned by blkid:
+
+title SliTaz cooking
+  map (hd0,0)/boot/slitaz-preinit.iso (hd1)
+  map --hook
+  kernel (hd1)/boot/bzImage mount=a4b346ee-4c7b-46aa-9fd4-6bc39ab4fa96 loopfs=data/slitaz.fs
+  initrd (hd1)/boot/rootfs.gz
+
+You can extract the bzImage and rootfs.gz from the iso image to avoid map commands and defragmentation.
+
+===== Subdirectory install =====
+
+If you want install SliTaz on a disk (not a frugal install), and you don't want to create a partition for SliTaz, but you have room in a filesystem for another Unix and you don't know how much space to reserve for SliTaz...
+
+... create a subdirectory and install SliTaz into it!
+
+This install method can waste some MB of RAM: it loads a ramdisk from the preinit flavor and doesn't disallocate RAM fully from the ramdisk.
+
+
+==== Root filesystem files installation ====
+
+Simply install SliTaz file in a subdirectory (say /var/slitaz) of another linux partition:
+  # mkdir /mnt/var/slitaz
+  # unlzma -c /media/cdrom/boot/rootfs.gz | ( cd /mnt/var/slitaz ; cpio -idmu )
+
+==== Boot setup ====
+
+Like a loop install, you need a preinit iso file with a matching version.
+The partition (say /dev/hda1) and the path into the partition are defined by the mount and subroot arguments: 
+
+title SliTaz cooking
+  map (hd0,0)/boot/slitaz-preinit.iso (hd1)
+  map --hook
+  kernel (hd1)/boot/bzImage mount=/dev/hda1 subroot=var/slitaz
+  initrd (hd1)/boot/rootfs.gz
+
+
+Both notes in 'Loop install' section about bzImage extraction and UUID/LABEL also apply here.
+The subdirectory install does not use exotic packages from preinit. You can use any SliTaz flavor (except lorams). However this is not recommended because the RAM filesystem is not fully disallocated
+
+===== LVM install =====
+
+The Logical Volume Manager can manage (add disks, replace disks ...) and logically freeze any disks for backup (snapshots) without disrupting service. 
+See [[wp>Logical_Volume_Manager_(Linux)]]
+
+==== LVM partition setup ====
+
+A small amount of storage (depending on the disk activity, likely between 1% and 15%) is used by snapshots to hold frozen data during a backup.
+Assuming we use the sda1 partition with 5% reserved for snapshots:
+  # tazpkg get-install lvm2
+  # modprobe dm-mod
+  # pvcreate /dev/sda1
+  # vgcreate slitaz /dev/sda1
+  # lvcreate -l 95%VG slitaz -n root 
+  # mke2fs -j /dev/mapper/slitaz-root        
+  # tune2fs -c 0 -i 0 /dev/mapper/slitaz-root
+  # mount /dev/mapper/slitaz-root /mnt
+
+==== Root filesystem files installation ====
+
+Similar to a loop install:
+  # unlzma -c /media/cdrom/boot/rootfs.gz | ( cd /mnt ; cpio -idmu )
+
+==== Boot setup ====
+
+Like a loop install, you need a **preinit** iso file with a matching version. The argument **lvmroot** holds the volume name:
+
+title SliTaz cooking
+  map (hd0,0)/boot/slitaz-preinit.iso (hd1)
+  map --hook
+  kernel (hd1)/boot/bzImage lvmroot=slitaz-root
+  initrd (hd1)/boot/rootfs.gz
+
+
+===== RAID install =====
+
+==== Hardware RAID ====
+
+Full hardware [[wp>RAID]] is transparent for SliTaz. The disk array is seen as a single disk and nothing special has to be done to install SliTaz.
+
+==== Semi hardware RAID ====
+
+=== Creation & installation ===
+
+The [[wp>RAID]] array is built with the BIOS menus. SliTaz needs the driver **dmraid** to see the array and not only each hard disk:
+  # tazpkg get-install lvm2
+  # tazpkg get-install dmraid
+  # dmraid -s            <== shows raid infomation
+  # modprobe raid1       <== could be raid0, raid456 or raid10
+  # dmraid -ay           <== activates the array in /dev/mapper
+  # mount /etc/mapper/myraid /media
+  # unlzma -c /media/cdrom/boot/rootfs.gz | ( cd /mnt ; cpio -idmu )
+
+=== Boot setup ===
+
+Like a loop install, you need a **preinit** iso file with a matching version. The argument **dmraid** holds the volume name:
+
+title SliTaz cooking
+  map (hd0,0)/boot/slitaz-preinit.iso (hd1)
+  map --hook
+  kernel (hd1)/boot/bzImage dmraid=myraid
+  initrd (hd1)/boot/rootfs.gz
+
+
+
+
+==== Software RAID ====
+
+The array does not need the BIOS and can be fully administered remotely!
+
+You should tune the **preinit** flavor to your needs. Enable the dropbear startup in /etc/rcS.conf and maybe install a VPN. If the software RAID does not start on startup, you will be able to fix it remotely...
+
+
+=== Creation & installation ===
+
+Example for mirroring (raid1) devices /dev/sda3 and /dev/sdb3:
+  # tazpkg get-install lvm2
+  # tazpkg get-install mdadm
+  # echo y | mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sda3 /dev/sdb3 --bitmap=internal --assume-clean
+  # modprobe raid1
+  # mdadm --assemble --scan
+  # mount /dev/md0 /media
+  # unlzma -c /media/cdrom/boot/rootfs.gz | ( cd /mnt ; cpio -idmu )
+
+=== Boot setup ===
+
+Like a loop install, you need a preinit iso file with a matching version. The argument **softraid** holds the device name:
+
+title SliTaz cooking
+  map (hd0,0)/boot/slitaz-preinit.iso (hd1)
+  map --hook
+  kernel (hd1)/boot/bzImage softraid=/dev/md0
+  initrd (hd1)/boot/rootfs.gz
+
+
+===== Crypto install =====
+
+
+Encrypts the whole [[wp>Disk_encryption|root filesystem]], not just the /home partition. Important, because the files in /tmp, /var/tmp may betray your work. The swap does too unless you use a file instead of a partition (like /tmp/swapfile; this will be encrypted too because this file is in the root filesystem)
+
+
+==== LUKS ====
+
+[[wp>LUKS]] replaces the [[wp>Cryptoloop]] and Loop-AES formats now.
+
+=== Creation & installation ===
+
+Create the encrypted device with **mountbox** (crypto button). You may have to accept the missing packages installation. Select the device (say /dev/sda3) and click the **create** button. Now you can start to format it:
+  # mke2fs -j /dev/mapper/crypto-sda3
+  # tune2fs -c 0 -i 0 /dev/mapper/crypto-sda3
+  # mount /dev/mapper/crypto-sda3 /media
+  # unlzma -c /media/cdrom/boot/rootfs.gz | ( cd /mnt ; cpio -idmu )
+
+=== Boot setup ===
+
+Like a loop install, you need a preinit iso file with a matching version. The argument cryptoroot holds the volume name:
+
+title SliTaz cooking
+  map (hd0,0)/boot/slitaz-preinit.iso (hd1)
+  map --hook
+  kernel (hd1)/boot/bzImage cryptoroot=sda3
+  initrd (hd1)/boot/rootfs.gz
+
+
+====== TODO ======
+
+==== Loop-AES compatibility ====
+
+This deprecated format needs the same __boot setup__ as LUKS.
+
+====== TODO ======
+
+===== Mixed install =====
+
+You can mix several above methods using one device access and/or one filesystem access.
+
+^Device access^Filesystem access^
+|mount=|subroot=|
+|*raid=|loopfs=|
+|lvmroot=|cryptoroot=|
+|*raid= + lvmroot=|loopfs= + cryptoroot=|
+
+==== Example 1 : RAID + LVM ====
+
+==== Example 2 : Loop + crypto ====
+
+==== Possible improvements? ====
+
+Add network support: nbd/iscsi + RAID 1 net&local + crypto 
+
+====== TODO ======
+
+===== PXE: No install ! =====
+
+You can [[http://doc.slitaz.org/en:guides:pxe#pxe-server-set-up|setup a PXE server]] (well... you need to configure your server) or a [[http://doc.slitaz.org/en:guides:pxe#advanced-web-booting-configuration|PXE forwarder]], see the //Embedded Web Boot with PXE boot PROM// (the SliTaz team has [[http://boot.slitaz.org|configured the server for you]] 8-))
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/virtualbox.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/virtualbox.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,63 @@
+====== Virtualbox ======
+
+===== SliTaz GNU/Linux with VirtualBox =====
+
+You can now play with SliTaz GNU/Linux on Windows with VirtualBox.
+Required:
+
+    * [[http://virtualbox.wordpress.com/2008/06/27/slitaz-gnulinux-is-here/|SliTaz GNU/Linux Image]], the virtual machine.
+    * [[http://www.virtualbox.org/wiki/Downloads|Oracle VirtualBox]] software, binaries for Windows.
+    * [[http://www.7-zip.org/fr/download.html|7-Zip]], needed to decompress the file.
+
+===== Step 1 - Downloads and installation. =====
+
+    * Download and install 7-Zip - necessary to decompress the files.
+    * Download and install the Oracle VitualBox software.
+    * Download and decompress the virtual machine somewhere on your local hard drive.
+
+===== Step 2 - Play the virtual machine. =====
+
+Before running SliTaz GNU/Linux virtual machine you need to configure a new virtual machine in the VirtualBox software.
+
+  -     Run virtualbox [//Start/Programms/Oracle xVM VirtualBox/VirtualBox//].
+  -     Add a new Machine: Click on [//New//] toolbar button.
+  -     Click [//Next//] in the “ Create New Virtual Machine ” dialog box.
+  -     Give a name to your new virtual machine ( i.e: SliTaz GNU/Linux ), and select Linux 2.6 in OS Type list and click [//Next//] .
+  -     Select the amount of memory for the virtual machine. 256MB default should be sufficient.
+  -     In the “ //Virtual Hard Disk// ” dialog box click on the [//Existing//] button to use your SliTaz virtual disk.
+  -     The Virtual Disk Manager start. Click the [//Add//] toolbar button, locate and select the VDI file (i.e: slitaz-1.9-x86.vdi ).
+  -     Click on [//Next//] and [//Finish//].
+
+You can now play with your new SliTaz GNU/Linux virtual machine.
+
+
+VirtualBox can use VMware virtual disks as well.
+
+
+===== Virtualbox-OSE =====
+
+You can install the open source edition of virtualbox (free software) in SliTaz with the package virtualbox-ose:
+
+# tazpkg get-install virtualbox-ose
+ 
+This is a restricted version without USB support.
+
+===== Slitaz get-virtualbox =====
+
+You can install virtualbox (full, but non-free version) in Slitaz with the get-virtualbox package:
+# tazpkg get-install get-virtualbox ; get-virtualbox
+
+Other virtualization (free software) is also available such as lguest or qemu.
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Low |
+|Review| Major Updates FIXME |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| We have get-virtualbox pkg now? Can we remove linux-source dependency from get-virtualbox like nvidia?|
+|:::|  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/vmware.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/vmware.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,32 @@
+====== VMWare ======
+
+===== Test SliTaz GNU/Linux with VMware =====
+
+What you will need:
+
+    * [[http://dl.free.fr/getfile.pl?file=/Dz6bYtdE/slitaz.7z|SliTaz GNU/Linux Virtual Appliance]] The Virtual appliance file.
+    * [[http://www.7-zip.org/fr/download.html|7-Zip]] Needed to decompress the file.
+    * [[http://www.vmware.com/products/player/overview.html|VMware Player]] Run the virtual machine on your Windows system.
+
+   -  Download and install 7-Zip.
+   -  Download and install the VMware Player.
+   -  Download the SliTaz GNU/Linux file and decompress it with 7-zip.
+   -  Now you can run the SliTaz virtual machine ( slitaz.vmx ) with VMware Player.
+
+
+When starting the virtual machine for the first time, VMware Player detects that files have been moved from another location. Keep the default option in the dialog box and click on the [Ok] button.
+
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Low  |
+|Review| Major Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve|Are instructions still valid? Some link don't work |
+|::: | How about creating get-VMWare pkg?? |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/vpn.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/vpn.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,73 @@
+====== Virtual Private Network =======
+
+A VPN binds isolated networks with tunnels over the Internet network. A tunnel encrypts and encapsulates network frames.
+
+    * frames are hidden (data and header, including routing info)
+    * encapsulation sets tunnel ends as source and destination
+    * only traffic volume is visible. But you can send dummy frames
+
+===== Tunnel using SSH and PPP =====
+
+Slitaz can build such tunnels out of the box (without additional packages) with menu system / netbox.
+You need on remote server:
+
+    * a user account
+    * a ssh access
+    * pppd launch rights (group rights or setuid bit)
+    * remote stations know how to route frames to the tunnel (peer is the default router or is running routing protcols such as rip, ospf, …)
+
+===== Tunnel setup =====
+
+    * launch system / netbox
+    * select VPN tab
+    * fill Peer and update Route(s) fields. Routes are the local area networks on peer side you want to reach. You only need to update Local IP and Remote IP when you create multiple tunnels. They are tunnel end IP points
+    * click Send Key and enter password
+    * click Connect
+
+===== Limitations =====
+
+    * This tunnel should not be used for real time traffic like VoIP. Based on TCP, the tunnel tries to avoid data loss instead of respecting timing. VoIP should use UDP based tunnels
+    * Only the Slitaz box can see the remote network. Other stations on the lan can't, until you add your lan routes to peer (assuming Slitaz is the default router or is running routing protcols)
+
+===== OpenSSH =====
+
+The openssh package is available on the mirror and provides TCP based tunnels:
+
+ # yes y | tazpkg get-install openssh 
+
+See http://www.openbsd.org/cgi-bin/man.cgi?query=ssh&sektion=1#SSH-BASED+VIR...
+
+===== OpenVPN =====
+
+The //openvpn// package is available on the mirror:
+
+ # yes y | tazpkg get-install openvpn 
+
+See documentation at http://openvpn.net/
+
+===== Cisco EasyVPN =====
+
+The //vpnc// package is available on the mirror:
+
+ # yes y | tazpkg get-install vpnc 
+
+See documentation at http://www.unix-ag.uni-kl.de/~massar/vpnc/
+
+===== Others VPN =====
+
+SliTaz packages search tool shows every VPN supported by SliTaz:
+http://pkgs.slitaz.org/search.cgi?tags=vpn
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Any new changes in the process? |
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/wicd.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/wicd.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,23 @@
+====== WICD ======
+
+[[http://doc.slitaz.org/en:guides:network-script|Pankso's openbox treat]] is very close to WICD, but if you want to set up SliTaz for not very experienced users it's recommended that you use WICD for Wireless Internet Control.
+
+Do as root:
+
+# tazpkg get-install wicd
+# leafpad /etc/rcS.conf
+
+In ///etc/rcS.conf// remove from the section RUN_SCRIPTS: **network.sh**
+and add to the section RUN_DAEMONS: **wicd**
+
+Then as user:
+
+$ leafpad .config/openbox/autostart.sh
+And add to the end:
+
+# wicd Network Configuration
+wicd-client &
+
+Then remove the network-plugin from the LX-Panel by right clicking on the network-plugin. 
+
+Reboot - don't test before rebooting, because network.sh is interfering with WICD (even if you stop it by typing /etc/int.d/network.sh stop).
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/wifi-easy.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/wifi-easy.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,271 @@
+====== Wifi configuration, easy method ======
+
+===== Introduction =====
+
+To install wifi under Linux, two methods are possible:
+
+    * Use the kernel module specific to your wifi card
+    * Use the Ndiswrapper module to install a Windows driver
+
+
+Here, we will discuss the usage of a kernel module specific to your card (Ndiswrapper will one day have another page on the wiki).
+
+To use a specific kernel module, you'll need to:
+
+    - Know your wifi hardware
+    - Know which module your card needs
+    - Install this module, and possibly firmware too
+    - Configure your connection to the access point
+    - Get connected and surf
+
+Netbox is a tool which can do that just by clicking a few buttons. 
+But it's also possible to configure your wifi from the command line.
+
+===== Wifibox/Netbox Graphical Utility =====
+
+With //netbox// or //wifibox// you can configure your wifi with only a few mouse clicks. As you already know which module you need, it's easy to use //wifibox//:
+
+$ subox wifibox
+
+//Wifibox// will install all the software needed and then launch the wifi. You won't have to manually install your wifi.
+
+Here are the necessary steps for //Wifibox//:
+
+    * First, go to the Drivers tab, and install the module you need. SliTaz will load the firmware (if needed), the kernel module, configure your wifi, and connect to the access point.
+    * Then, go to "//Configuration//", and start to configure. If you don't know what to add, have a look at the sample /etc/network.conf - wifibox uses the same parameters. Click on "//Start//"
+    * If all goes well, you may start surfing!
+
+===== Manually Configure your Wifi =====
+
+If you want to understand how wifi works in SliTaz, then you can try configuring your wifi manually. 
+
+But if you want to know how wifi generally works under linux, or if your kernel module is not on this list, you should look at the step by step wifi.
+
+Here is a quick summary of the steps needed:
+
+    * Know your wifi card
+    * Check and install if your wifi card needs any firmware, e.g., b43
+    * Load the kernel module specific to your wifi card       
+    * Check that your wifi card is detected and your module is loaded
+    * Configure /etc/network.conf
+    * Load up your WIFI interface
+    * Start /etc/init.d/network.sh
+
+The following commands do all of the above steps. This is also the easiest way: 
+
+
+# tazhw detect-pci --get-firmware
+# /etc/init.d/network.sh restart
+
+
+Now for more detailed instructions: 
+
+===== Detailed Instructions =====
+=== Identifying your hardware (Which wifi card do I have?) ===
+
+You can list your hardware using the terminal. It's useful to know which wifi card you have.
+
+If you have an integrated wifi card:
+
+$ lspci | grep -i network
+
+
+If your card is an usb one, you'll need //lsusb// which is available in the package //usbutils//:
+
+# tazpkg get-install usbutils
+$ lsusb
+
+
+In either case, you'll see something like this:
+
+02:02.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)
+
+
+This tells us the following:
+
+    * //Intel Corporation// made the card
+    * The card is a //Pro/Wireless Lan 2100 3B//
+    * The chipset is a //IPW 2100 (Intel Pro Wireless 2100)//
+    * The interface is a //Mini PCI//
+
+=== Which module do I need, and do I need firmware? ===
+
+The SliTaz linux kernel is made to be light. Some software modules; especially those needed by wifi cards are not installed by default, but have to be loaded by the user.
+
+Many wifi cards will work if you load the correct module. The easiest way is to let SliTaz auto-detect your hardware. 
+
+For integrated wifi cards:
+
+# tazhw detect-pci
+
+
+For usb cards:
+
+# tazhw detect-usb
+
+
+Sometimes, however, the module alone is not enough. Some types of card (Intel for example) also need firmware. Such firmware is not free software, so we can't distribute it as part of SliTaz. You may need to obtain the firmware from the website of your card manufacturer and download it to ///lib/firmware//. But you'll see that SliTaz can sometimes do this for you! 
+
+=== For b43, b43legacy, ipw2100 or ipw2200 kernel modules ===
+
+
+If the kernel module you need is either b43, b43legacy, ipw2100 or ipw2200, you also need to install the package: get-wifi-firmware. You can install it like this:
+
+# tazpkg get-install get-wifi-firmware
+
+
+=== Launch wifi ===
+
+get-wifi-firmware will install some commands named get-"//a module//"-firmware. To see the list: 
+
+# ls /usr/bin/get-*-firmware
+
+Launch the software that corresponds to your module (ipw2100 in the earlier example):
+
+# get-my_module-firmware
+
+
+For example, say your module is ipw2200, you can type:
+
+
+# get-ipw2200-firmware
+
+
+This command will:
+
+    - Get the needed firmware for "//my_module//", make the package //my_module-firmware//, and install it.
+    - Get useful software for wifi support (iwconfig, wpa_supplicant if needed...)
+    - Load the module "//my_module//" into the linux kernel.
+    - Launch ///etc/init.d/network.sh restart//, which starts wifi.
+  
+If ///etc/network.conf// is correctly configured, you can surf!
+
+The easiest way is to do this is to download the firmware graphically using Wifibox (Slitaz Wireless Manager). Yes, Slitaz graphical wireless manager (wifibox) can do these steps on the Driver tab (after selecting the correct module, say ipw2200 and pressing install). 
+
+
+
+===== Troubleshoot your wifi =====
+
+Here is a quick summary of the steps needed (Repeated again for understanding):
+
+    * Know your wifi card
+    * Check and install if your wifi card needs any firmware, e.g., b43
+    * Load the kernel module specific to your wifi card       
+    * Check that your wifi card is detected and your module is loaded
+    * Configure /etc/network.conf
+    * Load up your WIFI interface
+    * Start /etc/init.d/network.sh
+
+The following commands do all of the above steps. This is also the best way to troubleshoot. To get maximum help on the forums; please post the output of each of these commands. 
+
+ 
+lspci | grep -i network
+modprobe your_module
+dmesg | tail 
+lsmod 
+nano /etc/network.conf
+ifconfig eth1 up 
+ifconfig -a 
+iwconfig 
+/etc/init.d/network.sh restart 
+ifconfig -a 
+
+
+===== Configure /etc/network.conf =====
+
+Slitaz launches wifi using the script ///etc/init.d/network.sh//. This script uses the config file: ///etc/network.conf//. You should first edit your config file using the instructions in the sample /etc/network.conf.
+You'll find more information about /etc/init.d/network.sh [[en:guides:network-script|here]]
+
+Now your module must be loaded at each boot. To automate, add "//my_module//" to the line //LOAD_MODULES// in ///etc/rcS.conf//:
+
+# geany /etc/rcS.conf
+
+
+LOAD_MODULES="nls_utf8 my_module"
+
+===== Sample /etc/network.conf file with comments =====
+
+
+# start wifi on boot "yes" or "no"
+WIFI="yes"
+ 
+# wifi interface,  (usually "wlan0" or "eth0")
+WIFI_INTERFACE="wlan0"
+
+ 
+# ESSID of access point: "my_essid" or "any"
+# if any is chosen, slitaz will try to connect to the first access point
+# Be careful:
+# In some states (in France for example), you are not allowed to connect
+# to a private access point if it is not secured.
+# WIFI_ESSID="any" 
+
+ 
+# type of connection:
+# you can chose between:
+# ad-hoc : Connect to one cell without access point.
+# managed : One or more cell, with access point.
+# master : Your card is a master card
+# repeater : Your card acts as a repeater.
+#          Useful for long distances.
+# secondary : Your card is a backup for master or repeater
+# monitor : Your card only receives messages.
+# For most of the time, you'll use managed.
+# (Home, cyber-coffe, work, university...)
+WIFI_MODE="managed"
+
+
+# Key
+WIFI_KEY="ma8clef8de8chiffrement8difficilement8déchiffrable"
+
+ 
+# Key type wep or wpa or any or none
+# If you're using WPA-EAP (at work for example),
+# try any.
+WIFI_KEY_TYPE="wpa"
+
+ 
+# driver needed by wpa_supplicant.
+# It depends on your kernel module.
+# The possible drivers are:
+#  wext = Linux wireless extensions (in most cases, use this one.)
+#  hostap = Host AP driver (Intersil Prism2/2.5/3)
+#  atmel = ATMEL AT76C5XXx (USB, PCMCIA)
+#  wired = wpa_supplicant wired Ethernet driver
+WPA_DRIVER="wext"
+
+ 
+# Wifi channel. Leave it blank, if you don't know what it is.
+WIFI_CHANNEL=""
+
+ 
+# More args to pass to iwconfig.
+# Look at iwconfig man page for more information.
+WIFI_IWCONFIG_ARGS=""
+
+
+
+===== Extra Information =====
+Now for more detailed instructions: 
+First do "lspci" to know which card you have. Once we know which card you have, we can surf the internet to find which module you require, and if we need any special firmware. To help you, here are some useful links:
+
+    * [[http://linux-wless.passys.nl/|Linux wireless LAN support]] (The column on the right, tells you where to get the firmware, if applicable)
+    * [[http://help.ubuntu.com/|Ubuntu documentation]] (Good Ubuntu website, wifi page)
+    * [[http://www.google.com/|Google]] with "//the name of your wifi card//" + "//modprobe//" or "//linux//"
+If these links are not useful, you can ask at the [[http://forum.slitaz.org/|forum]]
+
+So we learn that the //Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter// works with the //IPW2100// module and the firmware is available at http://ipw2100.sourceforge.net/.
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/wifi-hard.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/wifi-hard.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,169 @@
+====== Wifi, step by step =======
+
+===== Introduction =====
+
+If you want to use your wifi right away, this page is not for you. You should look at the easy wifi tutorial which explains how to use the tools given by SliTaz.
+But if you want to know how to use wifi (under linux), this page will explain how, and help you to configure it //from scratch//.
+Before continuing:
+
+    * You should know the kernel module needed by your wifi card.
+    * If you need any firmware; you should know where to download it.
+
+We are going to:
+
+    -Install any useful software and firmware.
+    -Load the kernel module.
+    -Configure the wifi connection.
+    -Configure wpa.
+    -Get connected and surf.
+    -Shutdown wifi.
+
+//PS:// On SliTaz, the script /usr/bin/get-wifi-firmware takes care of steps 1 and 2, and the script /etc/init.d/network.sh; steps 3 to 6.
+
+===== Install needed software =====
+
+You'll need the wifi kernel modules and some software to manage wifi. If you are using a wpa key, you'll also need wpa_supplicant:
+
+
+# tazpkg get-install linux-wireless
+# tazpkg get-install wireless_tools
+# tazpkg get-install wpa_supplicant
+
+
+If you need firmware:
+
+# cd /lib/firmware
+# wget http://www.address/of/my/firmware
+
+
+Untar to install:
+
+# tar -xvf my_firmware.tar*
+# rm my_firmware.tar*
+
+
+===== Load the kernel module =====
+
+
+# modprobe -v my_module
+
+If you've got errors, verify that your firmware is where it should be and look at dmesg:
+
+$ ls -l /lib/firmware
+$ dmesg
+
+If you don't have any errors, you can continue.
+
+===== Configure wifi interface =====
+
+Before configuring a new interface, you should de-configure the old one. If your ethernet interface is configured, you should:
+
+# ifconfig eth0 down
+
+
+iwconfig allows you to configure your wifi card, so that it can connect to your access point. You need to know the name of your wifi interface (usually //wlan0// or //eth1//). If you don't know its name, just run iwconfig:
+
+# iwconfig
+
+
+Now we can configure your wifi interface and start it:
+
+# ifconfig WIFI_INTERFACE up
+# iwconfig WIFI_INTERFACE txpower on
+
+
+Let's test that the card works:
+
+# iwlist scan
+
+If you've got a list of access points you can now tell your wifi interface which ESSID to connect to:
+
+# iwconfig WIFI_INTERFACE essid MY_ESSID 
+
+Iwconfig can also accept others args, look at its man page to know more.
+
+===== Configure a wep or wpa key =====
+
+You can easily configure a wep key with iwconfig:
+
+# iwconfig WIFI_INTERFACE key my_wep_key
+
+
+But you should //always// use a wpa key, because wep keys can be easily cracked with aircrack, as noted [[http://www.tuto-fr.com/tutoriaux/tutorial-crack-wep-aircrack.php|here]],
+wpa_supplicant allows you to use a wpa key (some cards may use wpa without wpa_supplicant). It needs a config file. Usually, ///etc/wpa_supplicant.conf//. If you are using wpa_psk (normally, you are), add this to the file:
+
+ap_scan=1
+network={
+	ssid="my_essid"
+	scan_ssid=1
+	proto=WPA
+	key_mgmt=WPA-PSK
+	psk="my_clear_key"
+	priority=5
+}
+
+Or try:
+
+ap_scan=1
+network={
+	ssid="my_essid"
+	scan_ssid=1
+	key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE
+	group=CCMP TKIP WEP104 WEP40
+	pairwise=CCMP TKIP
+	psk="my_clear_key"
+	priority=5
+}
+
+It's now possible to launch wpa_supplicant:
+
+ # wpa_supplicant -B -w -c/etc/wpa_supplicant.conf -DWPA_DRIVER -iWIFI_INTERFACE
+
+WPA_DRIVER is the name of the driver used by wpa_supplicant.
+Usually, it's //wext//, but sometimes, another is needed. Here is a list of possible drivers:
+
+    * //wext// = Linux wireless extensions (generic, should work in most cases)
+    * //hostap// = Host AP driver (Intersil Prism2/2.5/3)
+    * //atmel// = ATMEL AT76C5XXx (USB, PCMCIA)
+    * //wired// = wpa_supplicant wired Ethernet driver
+
+The option //-B// launches wpa_supplicant as a daemon. If you want to kill it:
+
+
+# killall wpa_supplicant
+
+
+===== Get connected =====
+
+If you want to connect in dhcp, just run:
+
+# /sbin/udhcpc -b -i WIFI_INTERFACE -p /var/run/udhcpc.WIFI_INTERFACE.pid
+
+Normally, you should be surfing!
+
+===== Turn off wifi =====
+
+To stop wifi, you should shutdown your wifi card, and stop the wpa_supplicant and udhcpc daemons:
+
+# iwconfig WIFI_INTERFACE txpower off
+# kill `cat /var/run/udhcpc.WIFI_INTERFACE.pid`
+# killall wpa_supplicant
+
+You can also unload the kernel module:
+
+# rmmod my_module
+
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/guides/xorg-xvesa.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/guides/xorg-xvesa.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,307 @@
+====== Xorg & XVesa ======
+
+By default, SliTaz v3 uses Xorg 7.4 with the //xorg-xf86-video-vesa// v2.0.0 driver. This basic driver can cause problems with certain hardware combinations and can sometimes result in a very low resolution. Occasionally, X does not start at all and instead falls back to the log-in screen or to a text-based prompt. There are some simple solutions that can yield major improvements:
+
+  * check that you have enough RAM to run the default ISO. If not, use the [[http://mirror.slitaz.org/iso/3.0/flavors/|Low RAM ISO]] instead.
+  * try the [[http://mirror.slitaz.org/iso/3.0/flavors/slitaz-3.0-xvesa.iso|XVesa ISO]] (a.k.a. TinyX)
+  * install a more specific driver for your graphics card
+  * customise your Xorg configuration file (//xorg.conf//)
+
+Good introductions to Xorg Configuration can be found at [[http://www.freebsd.org/doc/en/books/handbook/x-config.html|The FreeBSD Handbook]] and [[https://wiki.ubuntu.com/X/Config|X Configuration from Ubuntu]].
+
+ Up to v7.3, the Ctrl+Alt+Backspace key combination could be used to quit the X server. To enable it in version 7.4 and later, type the following command from any X terminal emulator:
+
+setxkbmap -option terminate:ctrl_alt_bksp
+
+
+
+
+Throughout this page, commands preceeded with a hash sign (#) should be executed as the **root** user. This is best under a terminal window. Otherwise, the dollar symbol ($) denotes a regular (tux) user.
+
+
+
+===== Using Xorg & Vendor-Specific Drivers =====
+
+When you are using SliTaz as your main system, it's recommended to use Xorg over XVesa. You will get a much better display and performance than when using Xvesa tinyX.
+
+
+=== AGP Cards ===
+
+All AGP video cards need extra kernel modules to function under Xorg. Check if you have an AGP video card with //lspci//; if so, install the necessary modules in the //linux-agp// package before using Xorg:
+
+
+# tazpkg get-install linux-agp
+
+
+Load the modules using the SliTaz hardware detection tool:
+
+# tazhw detect-pci 
+
+You can now use the SliTaz X configuration tool to detect your settings:
+
+# tazx
+
+Select the appropriate driver for your video card from the list.
+
+
+=== DRI / DRM Problem ===
+
+Sometimes, the auto-detection is not enough. Cards that require [[http://www.bitwiz.org.uk/s/how-dri-and-drm-work.html|DRI / DRM]] are supported under SliTaz, but v3 has a couple of bugs! The file ///dev/dri// should be a directory and not a file and, to get DRI working correctly, we have to add tux to the group video or modify permissions in the Xorg configuration file:
+
+
+# tazpkg get-install linux-drm
+# tazpkg get-install mesa-demos (for glxinfo and glxgears)
+# rm /dev/dri
+# mkdir /dev/dri/
+# addgroup tux video
+
+
+The //drm// module is not loaded by //tazhw// so you have to do it manually:
+# modprobe drm
+
+All modules, which are loaded by tazhw and yourself to make your changes permanent, have to be added to the SliTaz Control Box under Initialization in "Load Modules". 
+
+
+=== Intel cards ===
+
+The xorg-xf86-video-vesa 2.0.0 driver has a lot of trouble with Intel chips. For example, on a 82945GM chipset it does not display 1280x1024 and 1024x768, but 1600x1200 is not a problem.
+
+Use "tazx" to select the intel driver, then "tazhw detect-pci", solve the dri problem and load drm and restart X - normally that's it (perhaps you must change your xorg.conf too).
+
+Some users may need to add the "intel_agp" module to the xorg.conf file:
+
+
+Section "Module"
+        ...
+	Load  "intel_agp"
+	...
+EndSection
+
+
+for the driver to work.
+
+Depending on the hardware, the //mode-setting// feature must be turned on or off. To turn it off append one of the following to the //kernel// line in the GRUB boot-loader configuration:
+
+  *  //nomodeset//
+  *  //i810.modeset=0//
+  *  //i915.modeset=0//
+
+If mode-setting is off by default and should instead be turned on, append one of the following:
+
+  *  //modeset//
+  *  //i810.modeset=1//
+  *  //i915.modeset=1//
+
+=== Trident cards ===
+
+Use "tazx" to select the trident driver, install mesa-dri-trident
+# tazpkg get-install mesa-dri-tridentand restart X
+
+
+=== nVidia cards ===
+
+SliTaz provides automatic configuration for nVidia cards. There are two drivers available, the Xorg-provided //[[#free-driver-nv|nv]]// and the nVidia-provided, non-free //[[#non-free-driver-nvidia|nvidia]]//. The //nv// driver should be tried first as this has been compiled for SliTaz, whereas the nVidia-supplied driver is a //binary blob// that tries to fit each and every Linux distribution.
+\\
+
+== Free Driver (nv) ==
+
+To set-up the free nVidia drivers, use the SliTaz Hardware Configuration tool:
+# tazhw setup nvidia 
+
+Alternatively, you can do this process manually:
+  * Download the following packages:
+    *  mesa, mesa-demos, linux-agp, xorg-xf86-video-nv
+# tazpkg get-install xorg-xf86-video-nv
+# tazpkg get-install mesa
+# tazpkg get-install mesa-demos
+# tazpkg get-install linux-agp
+
+  * Load the kernel modules 
+# tazhw detect-pci
+
+  * Replace the standard //vesa// driver with //nv//
+# sed -i 's/vesa/nv/' /etc/X11/xorg.conf
+
+
+== Non-Free Driver (nvidia) ==
+
+To set-up the non-free nVidia drivers, use the SliTaz Hardware Configuration tool with the //--non-free// switch:
+# tazhw setup nvidia --non-free 
+
+Alternatively, you can do this process manually:
+  * Download the following packages:
+    *  mesa mesa-demos linux-agp nvidia
+# tazpkg get-install nvidia
+# tazpkg get-install mesa
+# tazpkg get-install mesa-demos
+# tazpkg get-install linux-agp
+
+  * Load the kernel modules 
+# tazhw detect-pci
+
+  * Attempt to configure the card with nVidia's tool:
+# nvidia-xconfig
+  * To test if rendering is working, 
+# glxinfo | grep render
+  * To change nVidia's settings, use nVidia's Settings tool:
+# nvidia-settings
+
+== Hiding the Logo ==
+To hide the nVidia logo when the system boots, add the following to ///etc/X11/xorg.conf// at the end of the //Device// section:
+Option "NoLogo" "True"
+
+
+=== ATI cards ===
+
+SliTaz provides automatic configuration for ATI cards. There are two drivers available, the Xorg-provided //[[#free-driver-radeon|radeon]]// and the ATI-provided, non-free //[[#non-free-driver-catalyst|catalyst]]//. The //ati// driver should be tried first as this has been compiled for SliTaz, whereas the ATI-supplied driver is a //binary blob// that tries to fit each and every Linux distribution.
+\\
+
+== Free Driver (radeon) ==
+
+To set-up the free ATI drivers, install the AGP & DRM modules, then use the SliTaz Hardware Configuration tool:
+
+# tazpkg get-install linux-agp
+# tazpkg get-install linux-drm
+# tazhw setup ati
+
+- but perhaps this is not enough - check /var/log/Xorg.0.log to see if other modules must be loaded: See [[#dri-drm-problem | DRI / DRM Problem ]]
+
+Alternatively, you can do this process manually:
+  * Download the following packages:
+    *  xorg-xf86-video-ati mesa-dri-ati mesa-demos linux-agp
+# tazpkg get-install xorg-xf86-video-ati
+# tazpkg get-install mesa-dri-ati
+# tazpkg get-install mesa-demos
+# tazpkg get-install linux-agp
+# tazpkg get-install linux-drm
+
+  * Load the kernel modules 
+# tazhw detect-pci
+
+  * To install the free ATI driver radeon, replace //vesa// with //radeon// in the ///etc/X11/xorg.conf// file:
+# sed -i 's/vesa/radeon/' /etc/X11/xorg.conf
+
+
+== Non-Free Driver (catalyst) ==
+
+To set-up the non-free ATI drivers, use the SliTaz Hardware Configuration tool with the //--non-free// switch:
+# tazhw setup ati --non-free 
+
+
+=== Modifying the Xorg Configuration ===
+
+Normally Xorg will start successfully, but perhaps not with the correct resolution. See the [[#adding-resolutions|tips]] at the end of this page or sometimes search the Internet for the xorg.conf for your card and your monitor - or use another LiveCD and copy the working configuration file to SliTaz.
+
+
+===== Configuring X =====
+
+While X will do it's bets to auto-configure itself for your graphics card set-up, sometimes it needs a tweak. Its configuration file, ///etc/X11/xorg.conf//, is the place to customise the configuration. The best example of this is switching drivers or adding resolutions it doesn't detect.
+
+
+=== Adding Resolutions ===
+1. Include //HorizSync// and //VertRefresh// (refresh timings) in the //Monitor// section:
+
+
+Section "Monitor"
+	Identifier   "Monitor0"
+	VendorName   "Monitor Vendor"
+	ModelName	 "Monitor Model"
+	HorizSync	 28-64
+	VertRefresh  60
+EndSection
+
+
+2. Include a //DefaultDepth// in the //Screen// section:
+ 
+
+Section "Screen"
+	Identifier "Screen0"
+	Device     "Card0"
+	Monitor    "Monitor0"
+**	DefaultDepth 24 **
+
+
+3. Add an extra //Mode// to the line in the //Display// sub-section:
+
+
+   SubSection "Display"
+		Viewport   0 0
+		Depth     24
+		Modes 	  "1024x768" "800x600"
+	EndSubSection
+
+
+4. Also, add the default Font paths in the //Files// section:
+
+
+Section "Files"
+	ModulePath   "/usr/lib/X11/modules"
+	FontPath     "/usr/share/fonts/X11/misc/"
+	FontPath     "/usr/share/fonts/X11/TTF/"
+	FontPath     "/usr/share/fonts/X11/OTF"
+	FontPath     "/usr/share/fonts/X11/Type1/"
+	FontPath     "/usr/share/fonts/X11/100dpi/"
+	FontPath     "/usr/share/fonts/X11/75dpi/"
+	FontPath     "/usr/share/fonts/truetype/ttf-dejavu"
+EndSection
+
+
+  *  If you have DRI/DRM enabled, it may be easier to change its permission so all users can use it, rather than adding each to the //video// group. Append the following section:
+
+
+Section "DRI"
+        Mode 0666
+EndSection
+
+
+
+You can use xrandr to identify your monitor(s). This utility is in the //xorg-xrandr// package:
+
+# tazpkg get-install xorg-xrandr
+
+See the [[http://wiki.debian.org/XStrikeForce/HowToRandR12|Debian RandR 1.2 Wiki]] for more information.
+
+
+
+=== Restarting Xorg ===
+
+For changes to take effect, you need to restart Xorg. This can be done by logging out of your session and back in again. Choose //Logout// from the Menu and select the //Logout X session// button. If you see the Slim log-in manager, Xorg has restarted successfully!
+
+
+===== Using XVesa and Generic Drivers (TinyX) =====
+
+The [[http://mirror.slitaz.org/iso/3.0/flavors/slitaz-3.0-xvesa.iso|SliTaz-3.0-xvesa.iso]] uses the XVesa system instead of Xorg, which offers a more generic driver at the cost of performance. It boots on nearly all computers and laptops, but can only display a 4:3 resolution.
+
+To find out which resolutions are possible with your card, type:
+
+# Xvesa -listmodes 
+
+Here's a selection of resolutions for an example Intel Atom Board:
+
+VBE version 3.0 (Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS)
+DAC is switchable, controller is VGA compatible, RAMDAC causes snow
+Total memory: 7872 kilobytes
+0x015A: 1600x1200x24 TrueColor [8:8:8:8]
+0x011B: 1280x1024x24 TrueColor [8:8:8:8]
+0x0118: 1024x768x24 TrueColor [8:8:8:8]
+0x0112: 640x480x24 TrueColor [8:8:8:8]
+0x0115: 800x600x24 TrueColor [8:8:8:8]
+
+This output shows widescreen resolutions cannot be displayed with XVesa.
+
+If X does not start with the default SliTaz ISO, you could use the XVesa ISO to install your default Xorg driver. When you are asked for your resolution at boot-time, scroll down the window and find the option to install your Xorg driver //before// XVesa is started. However, don't use "tazx" and "tazhw setup ati or nv" on the XVesa ISO to install your Xorg driver because you will end up with a blank and confused screen!
+
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Extra config. for other cards? |
+|::: | More details on or references to xorg.conf  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/accessibility.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/accessibility.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,92 @@
+====== Accessibility ======
+
+===== About =====
+
+SliTaz aims to provide some Assistive Technology (AT) tools.
+
+===== Screen magnifier =====
+
+SliTaz supplies a screen magnifier whose edges can be resized and that can magnify up to 16x. 
+It also provides graphical tools that enable a crosshair, pixel positions and RGB values. It
+can be found in the Menu -> Utilities:
+
+ # tazpkg get-install magnifier
+
+
+===== Espeak - Text to speech (TTS) =====
+
+The espeak speech synthesizer run from the command line can speak text from an input file or 
+from stdin and supports many languages. Espeak can adjust the amplitude, pitch, word gap, 
+speed, etc. It can also write its output to a wave file rather than speaking it directly.
+Type ''%%espeak --help%%'' for a full list of available options:
+
+ # tazpkg get-install espeak
+
+
+Example of use:
+
+ $ espeak -f example.txt
+
+
+===== On-screen keyboard =====
+
+Virtual keyboard (xvkbd) can be used to enter characters into the software of your choice.
+The menu can be used to change the keyboard layout, function keys, etc. It supports word
+completion, the removal of unwanted keys and can connect to a remote display. The 
+configuration can be found in the ~/.Xdefaults file:
+
+ # tazpkg get-install xvkbd
+
+
+===== Yasr - Screen Reader =====
+
+Yasr is a console (text-based) screen reader that operates through the speech-dispatcher
+interface and espeak:
+
+ # tazpkg get-install yasr
+
+
+To configure speech-dispatcher:
+
+ # spd-conf 
+
+
+Speech-dispatcher can be started/stopped like a daemon:
+
+ # speech-dispatcher
+ # killall speech-dispatcher
+
+
+=== Usage ===
+
+ $ yasr
+ $ exit
+
+
+The configuration files can be found in the /etc/speech-dispatcher or ~/.speech-dispatcher directories
+and the yasr configuration file is located in /usr/share/yasr.
+
+
+===== Sticky/Slow/Mouse Keys in X =====
+
+To enable the accessibility keys just edit your ///etc/slim.conf// file and logout of your X session:
+
+
+default_xserver     /usr/bin/Xorg 
+xserver_arguments   +accessx 
+
+
+After you login again, to enable/disable:
+    * **Sticky keys**: Press the shift key 5 times
+    * **Slow keys**: Hold down the shift key for 8 seconds
+    * **Mouse keys**: Hold down the left shift, left Alt and Num Lock keys
+
+There is also a package in the Cooking repos that can do all this in gui or command line mode: **accessx**. To install and run:
+
+ # tazpkg get-install accessx
+ $ ax help
+ $ accessx
+
+
+
+       
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/chroot.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/chroot.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,100 @@
+====== 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
+ #
+
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/commands.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/commands.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,214 @@
+====== Command Line Reference ======
+
+===== 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 
+
+===== Move (rename) files or directories =====
+
+The mv command takes the contents of a file and copies it to a new file, then deletes the original file:
+ 
+ $ mv file1 file2 
+
+It can also rename directories (provided the new directory doesn't exist): 
+
+ $ mv ~/Documents ~/Docs 
+
+Move files (and directories) to a new directory:
+
+ $ mv file1 file2 dir1 dir2 ~/Documents 
+
+===== Create a new file =====
+
+The touch command can create a new empty file: 
+
+ $ touch newfile 
+
+===== 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 ( 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 :
+
+
+ $ 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  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
+ 
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/desktop.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/desktop.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,70 @@
+====== 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 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 //// 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 [[http://icculus.org/openbox/index.php/Openbox:Themes|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:
+
+
+
+  pcmanfm
+
+
+
+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"// : 
+
+{{ :en:handbook:image:desktopbox-autostart.png }}
+
+===== 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"// :
+
+{{ :en:handbook:image:desktopbox-icons.png }} 
+
+===== 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// or //~/.local/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 4 tabs:-
+
+    * Geometry handles the position, icons, and size - either dynamic or fixed of the panel.
+    * Appearance adjusts the background and fonts.
+    * 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 [[http://lxde.org/|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"//. 
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/development.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/development.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,139 @@
+====== Development ======
+
+===== 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: http://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 either 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 dependencies:
+
+ # 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 tac:
+
+ $ tazpkg search ncurses 
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/genlivecd.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/genlivecd.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,213 @@
+====== Generating a Customised LiveCD ======
+
+//Tazlito// can create your own, personalised SliTaz LiveCD in very little time. You can choose precisely the software packages that you want and 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.
+
+\\
+
+=== Overview ===
+
+Tazlito automates the process of building a LiveCD, although the method is quite straight-forward:
+
+  - download a template (flavor) to work on
+  - customise its packages
+    *  //optional: include additional files, added after the packages//
+  - compress the generated pseudo-file-system
+  - create an ISO image
+
+\\
+
+=== Notes ===
+
+  *  Creating a LiveCD requires a minimum of 256MB of RAM.
+  *  Compressing the file-system with LZMA may take some time. GZip can also be used, though its compression ratio is not as effective.
+  *  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 an 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. It is installed by default on SliTaz, but you can generate from another LiveCD distribution if they have the necessary packages (they can be downloaded if not). See the [[#installing-tazlito-on-another-distribution|instructions]] at the bottom of the page for more details.
+
+\\
+
+===== A LiveCD in Two Commands =====
+
+A good way of becoming familiar with Tazlito is to re-build the LiveCD. To do this, download the default //core// flavor (a //.flavor// file that contains all the necessary information to create a LiveCD) and build it with the default options. This takes only two commands and will demonstrate the process:
+\\
+
+    * Get the default (//core//) flavor:
+
+  # tazlito get-flavor core
+
+    * //Optional: Amend the list of packages or add additional files.//
+
+    * Create the LiveCD:
+
+  # tazlito gen-distro
+
+\\
+
+That's it! You will find the LiveCD ISO image in ///home/slitaz/distro//.
+
+\\
+
+===== Part I: Downloading a Flavor =====
+
+Flavors can be used to build various styles of LiveCDs by containing the list of packages (//distro-packages.list//) and sometimes additional files. This saves you the effort of saving the configuration files and provides a quick way of switching between them. of  A list of flavors available on the SliTaz servers can be downloaded and updated with Tazlito:
+
+  # tazlito list-flavors
+Or :
+  # tazlito list-flavors --recharge
+
+\\
+
+The list of flavors will be automatically displayed, showing the size of the LiveCD and a brief description. To use a flavor, use the get-flavor command to 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:
+
+   # tazlito get-flavor name
+
+\\
+
+The description of the flavor can be displayed with the //show-flavor// command. Once your chosen flavor is downloaded, you can start to customise your distribution!
+
+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
+
+
+
+\\
+
+===== Part II: Generating the Distribution =====
+
+When generating a distro, there are some essential //base-system// packages that must be included. The dependency information in each package will take effect so these will be automatically included, even if they are not specified in the package list.
+
+For your first ISO, we advise you re-build the default LiveCD without modifying the list. When you are comfortable with the process, you can start to delete or add packages as required. The gen-distro command generates an ISO image with all the packages on the list. All dependencies will be fulfilled automatically, just as with normal package installation. It must be run as root and be in the same directory as the list and the configuration file.
+
+Tazlito uses the //distro-packages.list// file to download each package and 'install' it into a pseudo-file-system. This is the distro tree and contains the whole of the LiveCD's operating system. This is not unlike //chroot//-ing in to another system from a LiveCD. It is then compressed and added to a CD ISO image with booting information.
+
+To generate a LiveCD:
+
+   # tazlito gen-distro
+
+Voilà! Your first LiveCD ISO image is generated in ///home/slitaz/distro//!
+
+\\
+
+=== Cleaning & Re-Generating ===
+
+As you have generated a LiveCD, you need to clean-up so another can be generated. Removing the resulting ISO image, cleaning the generated distro tree (but not your additional files!) can be done through the //clean-distro// option:
+
+   # tazlito clean-distro
+
+\\
+
+You can now customise your LiveCD further. To start, add one or two packages to the list. When you are ready, re-generate a new ISO image with the //gen-distro// command:
+
+   # tazlito gen-distro
+
+\\
+
+All the customisations applied so far should be effective on your new LiveCD ISO image.
+
+ Tazlito also offers several possibilities such as burning the ISO, copying additional files into the system or directly on to the CD-ROM. See the Tazlito [[http://hg.slitaz.org/tazlito/raw-file/tip/doc/tazlito.en.html|Manual]] for more information.
+
+\\
+
+=== The 'Hacker' User ===
+
+If you want to have a hacker user account, we must decompress the root file-system, add the account, then re-compress the root file-system. The first two stages can be executed as one command, the last stage another:
+
+   # tazlito addhacker
+   # tazlito gen-initiso
+
+This adds the account only to the LiveCD; your running system will not be affected.
+
+\\
+
+===== Including Additional Files =====
+
+The files containing flavors usually have additional files copied directly into the file-system or the root of the CD-ROM. The path to the files used is specified in the configuration file //tazlito.conf// - by default, these 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 file-system (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. You can easily create your own packages with Tazpkg, or recreate packages from a SliTaz system in operation with Tazlito. By default, SliTaz packages are located in the ///home/slitaz/packages// directory but you can change this in the Tazlito configuration file (see [[#configuration-file|the bottom of this page]] for more information).
+
+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//. The direct URL to package versions is: ''ftp://download.tuxfamily.org/slitaz/packages/''
+
+You can also use your own packages by putting them in the packages directory. For more information on creating your own SliTaz packages, see the [[en:cookbook:start|Cookbook]].
+
+\\
+
+===== Configuration File =====
+
+Tazlito uses the //tazlito.conf// located in the current directory, if it exists, or defaults to the system configuration file ///etc/tazlito/tazlito.conf//. This means that you can use the default file or a configuration file specific to the distro you want to create.
+
+This file specifies a number of properties:
+
+  * the name of the ISO image (//ISO_IMAGE//)
+  * the label used when mounted (//VOLUME_NAME//)
+  * the name of the maintainer (//PREPARED//)
+
+  * the paths to the working directories:
+    *  where the distro tree is located (//DISTRO//)
+      * default: ///home/slitaz/distro//
+    *  any packages that may be installed (//PACKAGES_REPOSITORY//)
+      * default: ///home/slitaz/packages//
+    *  the files that should be added to the built LiveCD (//ADDFILES//)
+      * default: //$DISTRO/addfiles//
+
+  * options for running Tazlito inside QEMU (//QEMU_OPTS//)
+
+  * the compression algorithm used on the root file-system (//COMPRESSION//):
+    * lzma //(default)//
+    * gzip
+    * bzip2
+
+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 working from it, use the command:
+
+   $ tazlito configure
+
+Once you've answered the questions, you can either create the ISO image, rebuild the root file-system and ISO, or generate a new distro with the list of packages.
+
+ If you generate many LiveCDs, including the //date// command in the ISO name may be beneficial. To do this, use a line such as:
+ISO_NAME="MyLiveCD-`date +%Y%m%d-%H%M`" 
+
+\\
+
+===== Advanced: Creating a Flavor =====
+
+Tazlito allows you to easily create your own flavor from the results of generating the distribution (//gen-distro//). The flavor will contain all the additional files, a description and a list of packages (which can be reused and updated later, according to their versions). 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 to make it available to everyone! It will then be listed via //list-flavor// and usable via //get-flavor//. You can send a flavor by several ways: 
+
+  * announce through a post on the [[http://www.slitaz.org/en/mailing-list.html|Mailing List]];
+  * save the file on-line and report on the [[http://forum.slitaz.org/|Forum]];
+  * send an e-mail to a SliTaz contributor.
+
+A contributor with sufficient privileges will then publish your flavor on the SliTaz servers.
+
+\\
+
+===== Installing 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 [[http://download.tuxfamily.org/slitaz/sources/tazlito/|sources of Tazlito]].
+
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates FIXME  |
+|Priority| High |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly, e.g.,|
+|::: | add more information to the Hacker user section |
+|::: | Add new rows like this ;-)  |
+
+\\
+----
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/graphics.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/graphics.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,37 @@
+====== Graphics ======
+
+===== 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 
+
+===== Viewnoir - Elegant image viewer =====
+
+Viewnoir is fast and simple image viewer with a minimalistic interface. It can rotate, flip, crop, save, delete images and supports fullscreen, slideshow, etc. To start from the menu //Graphics -> Viewnoir//.
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/hacklivecd.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/hacklivecd.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,212 @@
+====== 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 accommodate 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. Example configuration:
+
+
+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 &
+
+
+Adding the following lines:
+
+
+label memtest
+      kernel /boot/memtest
+
+
+Official website of [[http://www.memtest86.com/|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
+
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/installation.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/installation.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,149 @@
+====== Hard Disk 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 3.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 CD-ROM device and search for the compressed file-system (//rootfs.gz//). If no file-system is found, then the installation will abort.
+
+If you get into trouble because the compressed file-system 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 installer expects to find it:
+
+ # mount -o loop slitaz-3.0.iso /media/cdrom 
+
+=== Target Partition ===
+
+The second step is the partition configuration. You will need to have a partition ready; the installer does not set-up your disk for you. If you already have a free partition you can use it; if not you will have to create one graphically using GParted, or from the command line using fdisk.
+
+For example, if you want to install SliTaz on the second partition of the first disk recognized as hda:
+
+ /dev/hda2 
+
+=== Formatting ===
+
+ Formatting a partition **permanently** removes all data from it. Be sure you choose your intended partition carefully as //this action is irreversible//.
+
+The next step lets you format the target partition into ext3. Ext3 is a robust, stable and journalled file-system. If the partition is already formatted you can skip this step, if not just accept.
+
+=== Hostname ===
+
+Hostname configuration lets you set the machine name. The hostname is used internally and to identify the computer on a network. This can be changed after the system is installed. It cannot be longer than 64 characters and can only contain letters, numbers, and dashes.
+
+=== Boot-Loader (GRUB) ===
+
+When the installation process is finished you have the option to install the GRUB boot-loader. GRUB is capable of booting almost any kind of operating system and can be configured through a human-readable text file; changes to this file are instant and do not require an additional commands to take effect.
+
+If you want to use an existing GRUB installation, skip this step and add the correct lines to your GRUB configuration file (menu.lst); [[installation#grub-boot-loader | see below]] for more information. 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//).
+
+=== Finishing the 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//.
+
+===== Manual ('By Hand') Installation =====
+
+SliTaz can also be installed 'by hand' from the command line. You can use a CD-ROM or an ISO image. The following commands can be copied/pasted from your web browser to the Terminal.
+
+Firstly, prepare a target partition and mount it. For example, to use the second partition on the first disk drive (///dev/hda2//), one would type:
+
+
+ # mkdir /mnt/target
+ # mount /dev/hda2 /mnt/target
+
+
+=== Mount CD-ROM or ISO image ===
+
+Mount the CD-ROM...
+
+ # mount /dev/cdrom /media/cdrom 
+
+...or if you are using an ISO image:
+
+ # mount -o loop slitaz-3.0.iso /media/cdrom 
+
+=== Install and Extract ===
+
+With a target partition prepared and the installation media made accessible, we need to copy the files from the media into the target partition and then extract the compressed file-system (rootfs.gz).
+
+    *  Create a boot directory and install the Linux Kernel file:
+
+
+ # mkdir /mnt/target/boot
+ # cp -a /media/cdrom/boot/vmlinuz-* /mnt/target/boot
+
+
+    *  Copy the root file-system:
+
+ # cp /media/cdrom/boot/rootfs.gz /mnt/target 
+
+Now the necessary files are present, change (//cd//) to the target directory and decompress the file-system. This is done with the //lzma// and //cpio// utilities:
+
+
+ # cd /mnt/target
+ # lzma d rootfs.gz -so | cpio -id 
+ # rm rootfs.gz init
+
+
+That's it; SliTaz is installed! Before rebooting to start your new SliTaz GNU/Linux installation, please check that you have a boot-loader (GRUB or Lilo) installed and add the necessary lines (see below) to boot SliTaz.
+
+===== GRUB Boot-Loader =====
+
+GRUB is an universal boot-loader capable of booting almost any operating system , including Linux, *BSD and Windows. GRUB uses a single configuration file named //menu.lst//.
+
+If you used the SliTaz Installer and installed GRUB, you don't need to manually install GRUB -- just reboot.
+
+Otherwise, to install GRUB onto the MBR (Master Boot Record) using a root directory of ///mnt/target// (the target mounted partition) and the disk named hda, use the following command and note the lack of a partition number:
+
+ # grub-install --root-directory=/mnt/target /dev/hda 
+
+You can now create a GRUB configuration file and add the lines which will boot SliTaz. The //menu.lst// file can be edited with your favourite text editor such as Nano or Leafpad:
+
+ # leafpad /mnt/target/boot/grub/menu.lst 
+
+=== Example /boot/grub/menu.lst ===
+
+
+title  SliTaz GNU/Linux 3.0 (Kernel 2.6.34-slitaz)
+       root(hd0,0)
+       kernel /boot/vmlinuz-2.6.34-slitaz root=/dev/hda1 vga=normal
+
+
+Verify again that everything is in place before rebooting with the //reboot// command:
+
+
+ # reboot
+
+
+You should see GRUB with a SliTaz item in its menu.
+
+===== Dual-Booting with Windows =====
+
+A common query asked on the [[http://forum.slitaz.org/|Community Forum]] is how to dual-boot SliTaz and Windows. This is a straight-forward task that just needs the following lines appended to the ///boot/grub/menu.lst// file:
+
+
+title   Microsoft Windows
+        rootnoverify (hd0,0)
+        chainloader +1
+
+
+In this example, the Windows installation resides on the first hard disk (hd0) and the first partition (the second 0) within it. This may need modification to reflect individual cases. If it were the other way around and SliTaz proceeded Windows for instance, the line would read:
+
+rootnoverify (hd0,1)
+
+Most operating systems will either contain a boot-loader of their own (in the case of Windows and *BSD) or can be booted directly with GRUB.
+
+===== Installing SliTaz on an USB Device =====
+
+If you want to install SliTaz on an USB device, you must give a little "rootdelay" to allow time for the Linux kernel to detect it.
+
+To include this option, edit your menu.lst to include the argument
+:
+
+title  SliTaz GNU/Linux 3.0 (Kernel 2.6.34-slitaz)
+       root(hd0,0)
+       kernel /boot/vmlinuz-2.6.34-slitaz root=/dev/sda1 vga=normal rootdelay=10
+
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/internet.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/internet.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,77 @@
+====== Internet ======
+
+===== 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.
+
+===== 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 install:
+
+ # tazpkg get-install firefox 
+
+The web browser configuration files are stored in the hidden (dot) directory ~/.mozilla/firefox.
+
+When you combine the LiveCD with USB media, you can keep your bookmarks and plugins wherever you go.
+
+===== Retawq - Text mode web browser =====
+
+Retawq is an interactive web brower that can be run from the console or a graphical terminal. To install:
+
+ # tazpkg get-install retawq 
+
+To start retawq, just type (with or without the url): 
+
+ $ retawq http://www.slitaz.org/en 
+
+The configuration files are found in //~/.retawq//, you can edit them with a text editor. Pressing  will display the bookmarks (bookmarks.html) and the  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. To install gitmail:
+
+ # tazpkg get-install gitmail 
+
+===== 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. To install gFTP:
+
+ # tazpkg get-install 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 
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/livecd.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/livecd.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,126 @@
+====== Using the LiveCD ======
+
+SliTaz can be used straight from a CD-ROM or USB memory stick, without being installed to a hard drive. There are a number of ways to use the Live media, with options to customise how it starts.
+
+SliTaz runs entirely in memory (RAM), independently of the installed host system. It will not damage your other operating system(s) in any way, so you are perfectly safe to try out SliTaz.
+
+===== Quick Start =====
+
+To start using SliTaz from a CD-ROM, just burn the ISO image onto a blank disc and reboot your computer, leaving the disc in your CD-ROM drive. SliTaz will load automatically, detecting your hardware configuration to start.
+
+== If SliTaz LiveCD Does Not Start ==
+
+In most cases, your computer is already configured to boot from the CD-ROM. If the SliTaz splash screen does not appear, you can change the boot order via the BIOS set-up interface. This is different with each computer but can often be done by pressing a key such as the F11, F12, Esc button directly after turning on, before your operating system starts. You can then change the boot sequence and settings so that the CD-ROM comes first. Finally, save your changes before leaving the BIOS configuration interface.
+
+When the SliTaz Live media starts, the splash image will be presented. This is the //isolinux// boot-loader, which affects options to start SliTaz. You can just press ENTER to use the default settings, or enter options.
+
+Pressing F1 through F4 at the boot-splash will display help and information.
+
+When the loading process has finished, you can log-in to the desktop as the //tux// user, without any password. To use the administrator account, or **root**, you can start a Terminal and type the command //su//. The default password is **root**.
+
+===== Boot Options =====
+
+The SliTaz LiveCD accepts various boot options at the prompt. There are two types of options: options handled by SliTaz software and those generally handled by the Linux kernel.
+
+The options for SliTaz are used by various start-up scripts; the parameters such as the VGA mode are managed directly by the Kernel (kernel boot parameters). To pass options at start-up, just precede your commands with //slitaz// when the splash screen and **boot:** prompt is displayed. For example,
+ slitaz vga=791 no387
+
+The Linux kernel keeps options that were passed. These can be seen in the text file ///proc/cmdline//. 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 during the build. The SliTaz-built kernel has few core modules, compensated by loading others on-demand. This means few modifiable parameters are available at start-up. However, you can disable the emulation of a math coprocessor via 
+
+  * **no387**
+    *  Disables the emulation of a math co-processor.
+
+  * **irqpoll**
+    *  Turn on in case of problems with interrupts, shown by problems with the CD-ROM.
+
+  * **vga=**//XXX//
+    *  Specifies the kernel graphics mode. The SliTaz kernel displays the Tux penguin logo and manages the display of the Linux terminal by providing a basic video output mode, called the VGA/VESA frame-buffer. The following table lists the codes used; select a resolution and colour combination:
+
+^ ⇩ //Colours// ^ //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    |
+
+Once the system has started you have access to six pseudo-terminals via the key combinations Ctrl+Alt+F1 through Ctrl+Alt+F6. The key combination Ctrl+Alt+F7 and upwards are reserved for graphical output.
+
+=== Slitaz Parameters ===
+  * **home=usb**
+    * Specifies a /home directory to use within the Live environment. This will include your bookmarks, downloads and desktop customisations. To store your data permanently, you need USB media with a partition formatted in ext3; see the [[en:handbook:liveusb|Live USB]] page for more information. In most cases **home=usb** can be used for //sdb1//, or **home=**//devname// where the equivilent /dev node can be specified. Note that you can also specify the device using the partition UUID or label by using ** home=* **. Example:
+slitaz home=sdb1 
+
+    * **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
+
+
+
+  * **lang=**//XX//
+  * **kmap=**//XX//
+    * Sets the system language & keyboard mapping. Each are codes such as //en//, //de// or //fr_CH//. Alternatively, set your country code and press ENTER to sets the locale and refreshes the boot-loader; other options can then be entered as normal. To skip the language and keyboard configuration you can simply type options on the command line, for English/UK:
+ slitaz lang=en kmap=en 
+
+  * **config=**////**,**////
+    * Executes a script at SliTaz boot time. The script can be located on external media or a HD partition, specified with the //device// & //path// variables. 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 
+
+  * **screen=**////**x**////**x**////
+    *   Specifies the desktop screen resolution. These follow the standard pattern, e.g. //1024x768x24//
+ slitaz screen=1024x768x24 
+
+The **screen=text** option disables the graphical desktop & Slim login manager. 
+
+  * **sound=no**
+    *  Disables sound completely. This loads no sound-related kernel modules.
+ slitaz sound=no 
+
+  * **sound=noconf**
+    *  Skips automatic configuration of your sound card; you must configure it manually later.
+
+  * **modprobe=**//modules//
+    *  Loads specific kernel modules. Many can be loaded by separating with commas.
+ slitaz modprobe=module1,module2 
+
+  * **laptop**
+    * Loads ac and battery Kernel modules - useful for laptop computers.
+
+  * **previous**
+    *  Used by the TazUSB utility to roll-back to a previous filesystem.
+ slitaz previous
+
+===== The Desktop =====
+
+When the system has finished its initialization, the screen is cleared and the login prompt (Slim) is displayed. You can choose here to login as the regular //tux// account (without a password) or as the admisitrative //root// account (with the **root** password).
+
+The desktop is powered by //Openbox//. You can start applications from the menu at the lower-left of the screen. 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). 
+
+===== Text Mode =====
+
+If you are new to SliTaz or Linux in general, a graphical desktop is highly recommended.
+
+The above information applies also to the text-mode log-in prompt. Once logged in, you can use the many text-mode applications available in SliTaz, such as the basic BusyBox operation, the GNU text editor //Nano//, or the //Clex// file manager. Just type the name of the application you wish to start. There is a [[en:handbook:commands|Command Line Reference]] page to get you started.
+
+To launch a graphical desktop session from the text-mode prompt (if you have passed the screen=text option, or if Slim is not configured to run at startup, for example) just type **startx**.
+
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]] 
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| ? |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/liveusb.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/liveusb.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,36 @@
+====== 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 [[http://hg.slitaz.org/tazusb/raw-file/tip/doc/tazusb.en.html|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/sdb1 
+
+Then format and label your device (Warning: this will erase all data, make sure you specify the right device):
+
+ # tazusb format /dev/sdb1  
+
+And finally generate your LiveUSB media device:
+
+ # tazusb gen-liveusb /dev/sdb1 
+
+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 one the following commands:
+
+    * fast compression, average filesize:  # tazusb writefs gzip 
+    * slow compression, smaller filesize:  # tazusb writefs lzma 
+    * no compression, larger filesize:  # tazusb writefs none 
+
+Each of these writes everything to a '//rootfs.gz//' archive 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 using //tazusb clean//.
+
+=== Tazusb Manual ===
+
+The official Tazusb manual can be found in the SliTaz [[http://hg.slitaz.org/tazusb/raw-file/tip/doc/tazusb.en.html|Web site documentation]]; this contains a lot more useful information. The manual is also available through the documentation menu on the LiveCD.
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/multimedia.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/multimedia.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,102 @@
+====== Multimedia ======
+
+===== 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.
+
+===== mhWaveEdit - Audio editor and recorder =====
+
+mhWaveEdit is a graphical application for playing, recording and editing sound files. Supported formats: wav (default), and a few others. A variety of other formats can also be imported through Mplayer. To start from
+the menu, select //Multimedia -> mhWaveEdit//.
+
+===== 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 and run:
+
+ # tazpkg get-install mpc
+ $ 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 install:
+
+# tazpkg get-install mpg123
+
+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. To install mplayer:
+
+# tazpkg get-install mplayer-svn
+
+===== 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 dependencies:
+
+ # tazpkg get-install xine-ui 
+
+Official Xine [[http://xinehq.de/index.php/home|website]] 
+
+===== VLC =====
+
+VLC media player is a highly portable multimedia player and multimedia framework  capable of reading most audio and video formats (MPEG-2, MPEG-4, H.264, DivX, MPEG-1, mp3, ogg, aac ...) as well as DVDs, Audio CDs VCDs, and various streaming protocols. To install vlc:
+
+ # tazpkg get-install vlc 
+
+Official VLC [[http://www.videolan.org/vlc/|website]] 
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/netstart.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/netstart.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,57 @@
+====== Web start and possible immediate installation ======
+
+===== Special figure in Slitaz ! =====
+
+Slitaz is one of the extremely rare OS's available fully prepared for the web start in live mode using a very small starting program. The starting program can be saved on a old floppy disk or very little special ISO burned on a CD-ROM.
+
+But each starting ISO of Slitaz with the live version of "base", "justX" or "stable" or "cooking" contains also this start program being used through the commando line options at starting time of the ISO.
+
+The special advantage of this kind of start is to work with the most actual cooking version and not with the version of the CD.
+
+The same technical ability can of course be used within a closed community.
+
+==== Where can I find the starting image for a starting floppy disk? ====
+
+http://mirror.slitaz.org/boot/floppy-grub4dos
+
+Please read more here:
+
+http://boot.slitaz.org/
+
+==== Where can I find the small ISO for a small starting CD rom? ====
+
+You can use the little flavor version
+ 
+http://mirror.slitaz.org/iso/2.0/flavors/slitaz-2.0-base.iso
+
+for that.
+
+Only enter please "web" as commando line option!
+
+==== Starting from the net ====
+
+The start from net don't differ from usual start from the CD.
+
+Only enter "web" as commando line option. The starting program don't follow the CD any more but search the more actual file on the web.
+
+==== Install Slitaz on the hard disk after the net start ====
+
+Of course here is an important difference compared with the usual start:
+
+There is no CD in the drive where the installation program can find the row files.
+
+.... 
+
+==== Regular net start in my community net (school etc.) ====
+
+=== Install the adequate Slitaz version on the own server ===
+
+....
+
+=== Limit access if required ===
+
+....
+
+=== Prepare an adequate ISO for a own starting check card mini CD ===
+
+....
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/networkconf.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/networkconf.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,243 @@
+====== Network Configuration ======
+
+===== 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. 
+
+{{:en:handbook:image:netbox.png}}
+
+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. 
+
+{{:en:handbook:image:wifibox.png}}
+
+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 
+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: http://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
+
+}
+
+
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/office.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/office.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,49 @@
+====== Office ======
+
+===== 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: [[http://homebank.free.fr/|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//. 
+
+===== Wikipedia - Online Encyclopedia =====
+
+Wikipedia is a free online encyclopedia where you can find information on various subjects. To open the wikipedia, choose //Office -> Wikipedia Encyclopedia//. Main website: http://wikipedia.org
+
+===== Zoho Viewer - Online document viewer =====
+
+If you need to quickly edit a document and the right spreadsheet or word processor is not at hand, you can use the document viewer to quickly upload your file (up to 10 MB). And within a couple of seconds it will be available for reading and editing. To open Zoho on the menu, select //Office -> Zoho Document Viewer//.
+
+It currently supports most popular formats:
+
+    * Microsoft Word (doc, docx), Excel (xls, xslx), PowerPoint (ppt, pptx)
+    * OpenOffice.org Writer (odt, sxw), Spreadsheet (ods sxc), Presentation (opd, sxi)
+    * Also pdf (experimental stage), rtf, html, txt, and others
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/packages.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/packages.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,76 @@
+====== Packages ====== 
+
+===== 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. 
+
+=== 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 specify cat or category. Examples:
+
+
+ $ tazpkg list cat
+ $ tazpkg list base-system
+
+
+Tazpkg can also generate a 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
+
+
+== The 'get' Packages ==
+
+There are a few packages that are prefixed with //get-//. These are not packages per-sé but contain only a script. This script provides binary software by:
+
+  * downloading the program
+  * creating a Tazpkg from it
+  * installing the generated Tazpkg
+
+This means that the actual program is not contained within the //get// package, but that generated by it.
+
+To manage this style of software:
+   * install the latest version using the //get// script in the //get// package;
+   * remove it by using tazpkg on the **generated** package.
+ 
+Please note that after downloading the //get-package//, you need to run the script that has the same name:
+ # tazpkg get-install get-OpenOffice3
+ # get-OpenOffice3
+
+
+=== 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 [[http://hg.slitaz.org/tazpkg/raw-file/tip/doc/tazpkg.en.html|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 then test the application or library. 
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/security.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/security.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,60 @@
+====== SliTaz and System Security ======
+
+===== 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 
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/server-apps.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/server-apps.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,65 @@
+====== Server applications ======
+
+===== Dokuwiki =====
+
+Dokuwiki (http://www.dokuwiki.org/) is a light and powerful Wiki engine using PHP and flat files as a backend; so no database server is needed. To use Dokuwiki you just need to install a web server (lighttpd or apache) and PHP.
+
+===== Drupal =====
+
+Drupal is a powerful CMS (Content Management System) using PHP server side language and a MySQL database. To install Drupal and have it running in a few minutes you must first install the web server (lighttpd), PHP and MySQL:
+
+
+# tazpkg get-install lighttpd
+# tazpkg get-install php
+# tazpkg get-install mysql
+
+
+Download the latest version from http://drupal.org/ and create a virtual host or go into your public directory and untar the Drupal sources:
+
+
+$ mkdir ~/Public && cd Public
+$ tar xzf drupal-*
+
+
+Now we have to modify some file permissions so that Drupal can write to the filesystem during the installation process and when running:
+
+
+$ cd drupal-*/sites
+$ chmod 777 default
+$ cp default/default.settings.php default/settings.php
+$ chmod 666 default/settings.php
+
+
+Create a MySQL database and then use your favorite web browser to install Drupal through the web interface. When the installation process has ended you must modify file permissions and can start to customize the application. Change permissions for production and clean-up:
+
+
+$ cd ..
+$ chmod 755 sites/default
+$ chmod 644 sites/default/settings.php
+
+
+To ensure easy upgrades of your Drupal core installation you should put all additional modules and themes into the directory: site/all/. So to prepare the addition of any future modules and themes:
+
+
+$ mkdir sites/all/modules
+$ mkdir sites/all/themes
+
+
+==== Online ====
+
+    * Drupal Modules: http://drupal.org/project/modules
+    * Drupal Themes: http://drupal.org/project/themes
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Good  |
+|Review| Minor Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Suggest briefly|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/ssh.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/ssh.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,45 @@
+====== Secure SHell (SSH) ======
+
+===== 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: http://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//. 
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/start.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/start.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,64 @@
+====== Handbook ======
+
+Note: The current Handbook is still on the main web site and will be migrated after 3.0 is released. Here we have a copy of the livecd page (to help translators) and some new pages to improve and complete the current Handbook: http://www.slitaz.org/en/doc/handbook/
+
+===== General =====
+
+  * [[livecd|LiveCD usage]] - How to boot and set options at the command prompt.
+  * [[desktop|Desktop]] - Configure the Desktop and Window Managers.
+  * [[commands|Commands]] - List of useful commands.
+  * [[installation|Installation]] - HD install instructions.
+  * [[accessibility|Accessibility]] - Assistive technologies.
+
+
+===== Desktop Applications =====
+
+    * [[utilities|Utilities]] - Calculator, Text editor, Create CD/DVDs and ISOs.
+    * [[office|Office]] - Word processor, Personal organizer and PDF reader.
+    * [[internet|Internet]] - Web browsers, IRC chat client, mail client, BitTorrent and FTP.
+    * [[graphics|Graphics]] - Computer graphics and Image management.
+    * [[development|Development]] - SHell scripts, Perl, Python and Toolchain.
+    * [[multimedia|Multimedia]] - Sound, music and video.
+    * [[systemtools | System Tools]] - File & Disk managers and other tools.
+    * [[wm|Window Managers]] - Openbox, Pekwm, JWM, Enlightenment, dwm and others.
+
+
+
+===== System Administration =====
+
+     * [[packages|Packages]] - Install more software, keep system up-to-date.
+    * [[networkconf|Network configuration]] - Ethernet, DHCP, static IP or PPP dialup connection, Firewall.
+    * [[systemutils|System administration]] - Mount devices, manage users and groups, adjust system time.   
+    * [[xwindow|X Window System]] - Xvesa & Xorg servers, Slim Login and Window managers.   
+    * [[security|Security]] - SliTaz and system security.
+
+===== Flavor ======
+    * [[genlivecd|Generate a LiveCD flavor]] - Generate your own LiveCD flavor using Tazlito.
+    * [[liveusb|LiveUSB media]] - Create bootable USB media using TazUSB.
+    * [[hacklivecd|Hacking LiveCD]] - Manipulate and play with the ISO image of LiveCD.    
+    * [[chroot|Chroot Environment]] - Build a chroot to protect the host system.
+
+===== Server Applications =====
+  * [[server-apps|Server applications]] - Install and config of CMS, Wiki, etc.
+  * [[webserver|Web server]] - Configure and use the LightTPD web server.
+  * [[ssh|Secure SHell (SSH)]] - Secure login using Dropbear SSH client/server.
+
+
+
+===== About this Handbook =====
+
+This is the SliTaz GNU/Linux English Handbook, a collection of instructions and manuals about the distribution. 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. 
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Medium  |
+|Review| Major Updates FIXME |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Make all pages current as of 3.0|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/systemtools.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/systemtools.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,35 @@
+====== System Tools ======
+
+===== Clex - Command line File Manager =====
+
+To navigate through your folders and directories you can use cd on the command line or install the Clex File Manager:
+
+ # tazpkg get-install clex 
+
+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 dependencies.
+
+=== 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//. 
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/systemutils.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/systemutils.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,157 @@
+====== 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 ( to save & exit):
+
+ # nano /var/spool/cron/crontabs/root 
+
+Add the line:
+
+ * * * * * 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 
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/utilities.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/utilities.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,79 @@
+====== Utilities ======
+
+===== Galculator =====
+Galculator is a simple GTK 2 based calculator that features basic, paper (cmdline) and scientific modes. You can easily switch number bases between decimal, hexadecimal, binary, etc and it supports ordinary notation/reverse polish notation. To locate from the menu, select //Utilities -> Scientific Calculator//.
+
+===== 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 PCManFM2. 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  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 ( 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.
+
+Website : 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). To install Xpad:
+
+ # tazpkg get-install xpad
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/webserver.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/webserver.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,117 @@
+====== LightTPD Web Server ======
+
+===== 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 tux (//user=tux//):
+
+
+# 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=tux"
+)
+)
+
+
+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 tux:root to the password file ///etc/lighttpd/plain.passwd//:
+
+
+ # echo "tux: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 
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/wm.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/wm.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,119 @@
+====== Window Managers ======
+
+===== Openbox =====
+
+More details in [[en:handbook:desktop|Desktop]]
+
+===== 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 (([[http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html|Recognized desktop entry keys]])) 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: http://exchange.enlightenment.org/
+
+===== 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:   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 other 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 ===
+
+    * http://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.
+
+===== Pekwm =====
+[[http://www.pekwm.org/files/pekwm/doc/0.1.10/html/index.html|Documentation]]
+
+===== DWM =====
+[[http://dwm.suckless.org/tutorial|Documentation]]
+
+===== Xfce =====
+
+[[http://www.xfce.org/|Xfce]] is a lightweight desktop environment. It replaces the default OpenBox and PCManFM, and is also based on GTK+.
+
+To install Xfce, select the 'xfce4' meta-package from the Package Manager. This will install all the related packages.
+
+To use Xfce, ensure you have the correct command for Xfce in the Slim (log-in manager) configuration. Do this by appending **xfce4** to the //sessions// line of the ///etc/slim.conf// file - note that you will need root permissions to modify the file:
+sessions            openbox,e17,jwm,xfce4, 
+
+You can then select Xfce by pressing F1 at the log-in screen, as you enter your user-name and password.
+
+Extras are available at [[http://goodies.xfce.org/|Xfce Goodies]], including plug-ins, artwork and bindings.
+
+To remove Xfce, use the following command as //root// user:
+
+for PKG in xfce4 xfce4-session xfce4-panel xfwm4 libxfcegui4 xfce-utils libxfce4util thunar thunar-volman xfconf ; \ 
+do yes y | tazpkg remove $PKG ; done
+
+
+
+---- 
+\\
+^  Page Review Section  ^^ 
+|Quality| Medium  |
+|Review| Minor/Major Updates  |
+|Priority| Medium |
+|Problems| add a [[http://forum.slitaz.org|forum post link]]|
+|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
+|How to Improve| Add Pekwm/dwm/fluxbox sections|
+|::: |  |
+
+\\
+----
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/handbook/xwindow.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/handbook/xwindow.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,130 @@
+====== X Window System ======
+
+===== X11 - X Window System =====
+
+The X Window System or X11 provides a window manager running on top of a X server.
+
+SliTaz 2.0 by default uses the lightweight X server called Xvesa from the Xorg project (www.x.org).
+
+Slitaz 3.0 by default uses the Xorg server, there is however a Xvesa flavor.
+
+The X server 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 either '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 dependencies 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 for 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 
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/newsletter/oldissues.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/newsletter/oldissues.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,18 @@
+====== Monthly Newsletter - Old Issues ======
+
+[[en:newsletter:oldissues:14|Issue 14]]
+
+[[en:newsletter:oldissues:15|Issue 15]]
+
+[[en:newsletter:oldissues:16|Issue 16]]
+
+[[en:newsletter:oldissues:17|Issue 17]]
+
+[[en:newsletter:oldissues:18|Issue 18]]
+
+[[en:newsletter:oldissues:19|Issue 19]]
+
+[[en:newsletter:oldissues:20|Issue 20]]
+
+[[en:newsletter:oldissues:21|Issue 21]]
+
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/newsletter/oldissues/14.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/newsletter/oldissues/14.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,143 @@
+====== Monthly Newsletter - Issue 14 ======
+
+	* Written on 16th January 2010
+
+===== Latest News =====
+
+        * SliTaz featured in Distrowatch [[http://distrowatch.com/weekly.php?issue=20100111#feature|review]]
+        * SliTaz [[http://mirror.slitaz.org/iso/cooking-snow/README.html|snow]] isos released
+        * We will have a stand at the forthcoming http://www.solutionslinux.fr/
+        * Newsletter is back again!
+
+===== New Packages =====
+
+	* calcurse
+	* tty-clock
+	* nethogs
+	* icmptx
+	* plotdrop
+	* xournal
+	* apr-dpd-*
+	* openvas-*
+	* snort
+	* lives
+	* gkll
+	* gutenpy
+	* python-pyprotocols
+	* aspell-{hu,cs,id,it,ru,sl}
+	* evince
+	* libmagic
+	* libical
+	* libmpdclient
+	* libunique
+	* libplayer
+	* libvalhalla
+	* elementary
+	* enna
+	* libffd
+
+===== Updated  Packages =====
+
+	* mpg123 => 1.10.0
+	* openbox => 3.4.9
+	* cairo => 1.8.8
+	* firefox => 3.5.7
+	* web-applications => 1.2
+	* postgresql => 8.3.9
+	* apr => 1.3.9
+	* apache => 2.2.14
+	* sarg => 2.2.6
+	* squid => 3.0STABLE21
+	* putty => 0.60-2009-09-08
+	* sudo => 1.7.2p2
+	* mc => 4.7.01
+	* perl-pango => 1.221
+	* python-pygments => 1.1.1
+	* python-bpython => 0.9.5.2
+	* python-mysql => 1.2.3.c1
+	* python-django => 1.1.1
+	* python-sqlalchemy => 0.5.6
+	* python-formalchemy => 1.3.1
+	* python-jinja2 => 2.2.1
+	* tuxtype => 1.8.0
+	* intltool => 0.40.6
+	* babl=> 0.1.0
+	* gegl => 0.1.0
+	* gimp => 2.6.8
+	* couchdb => 0.10.1
+	* python-couchdbkit => 0.3.1
+	* libsmpeg => 389
+	* stoq => 0.9.11
+	* stoqdrivers => 0.9.8.2
+	* fpm2 => 0.76.1
+	* awstats => 6.95
+	* pure-ftpd => 1.0.27
+	* strace => 4.5.19
+	* pygtk => 2.16.0
+	* pycairo => 1.8.2
+	* pygobject => 2.20.0
+	* gdb => 7.0.1
+	* reiserfprogs => 3.6.21
+	* gajim => 0.13.1
+	* midori => 0.2.2
+	* ntfs-3g => 2009.11.14
+	* libboost => 1.41.0
+	* wormux => 0.8.5
+	* vte => 0.23.1
+	* sakura => 2.3.6
+	* jfsutils => 1.1.14
+	* emelfm2 => 0.7.1
+	* leafpad => 0.8.17
+	* popt => 1.15
+	* libmodplug => 0.8.7
+	* espeak => 1.42.04
+	* libffi => 3.0.9
+	* udev => 150
+	* cyrus-sasl => 2.1.23
+	* rsync => 3.0.7
+	* mpd => 0.15.7
+	* mpc => 0.19
+	* ario => 1.4.2
+	* slitaz-bootscripts => 3.2
+	* eet => 1.2.3
+	* e17 => 2009.12.02
+	* enlightenment => 2009.12.02
+	* pidgin => 2.6.5
+	* dnsmasq => 2.51
+	* get-virtualbox => 1.01
+	* bind => 9.6.1-P2
+
+===== Improvements =====
+
+  * slitaz-tools (3.4) - Lots of fixes and improvements
+  * tazpkg (3.2) - Box is much faster and deps auto-installed
+  * slitaz-boot-scripts (3.2) - WPA connections are much faster, boot time is logged and Xorg is autoconfigured at boot for any Live systems using it
+  * Package database for the Cooking version: 2226 (+ 835 from 2.0)
+
+===== Bugs =====
+
+
+^   Activity   ^    Open   ^    Closed  ^
+|    Bugs      |     58    |      50    |
+|    Features  |     37    |      21    |  
+|    Tasks     |     9     |      38    |
+
+
+	* Based on current figures
+
+===== Cartoon =====
+
+{{http://people.slitaz.org/~paul/cartoons/cartoon%236.png}}
+
+
+===== Tips and Tricks =====
+
+	* The Many Uses of Screen: http://www.serverwatch.com/tutorials/article.php/3838961/The-Many-Uses-of-Screen.htm	
+
+===== Online =====
+
+	* Slitaz Linux - Zero to Distro in 30MB!: http://linuxologist.com/reviews/slitaz-linux-zero-to-distro-in-30-mb/		
+
+===== Old Issues =====
+
+       * Click [[en:newsletter:oldissues|here]]
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/newsletter/oldissues/15.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/newsletter/oldissues/15.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,112 @@
+====== Monthly Newsletter - Issue 15 ======
+Lang:[[cn:handbook:newsletter|cn]] [[en:newsletter:start|en]]
+
+    * Written on 27th February 2010
+
+===== Latest News =====
+
+    * SliTaz Cooking 20100221 released
+    * Newsletter translated into Chinese (thanks draplater)
+
+===== New Packages =====
+
+    * vim-tiny
+    * smbfs
+    * libsasl
+    * libsasl-modules
+    * libcomerr3
+    * libkrb5support
+    * cgdb
+    * ccache
+    * distcc
+    * xorg-xf86-input-evtouch
+    * xorg-xf86-input-microtouch
+    * xorg-xf86-input-mutouch
+    * open-iscsi
+    * liblzma
+    * pidgin-libnotify
+    * xfce4-taskmanager
+    * xfce4-ristretto
+    * parole
+    * xfmpc
+    * xorg-xf86-input-void
+    * hal-scripts
+    * xorg-xf86-input-plpevtouch
+    * xfmedia
+    * dotconf
+    * speech-dispatcher
+    * yasr
+    * ncdu
+    * gfortran
+    * libgfortran
+    * octave
+    * fusecloop
+    * zsync
+    * tinc
+    * cloudvpn
+    * antiword
+    * l2tpd
+    * rp-lstp
+    * sctp-tools
+    * libsctp
+    * nat-tester
+    * evilvte
+    * lrzip
+    * wipe
+    * fsarchiver
+    * perl-gd
+
+===== Updated  Packages =====
+
+    * seamonkey => 2.0.2
+    * ncmpcpp => 0.5
+    * claws-mail-*
+    * gtkhtkl-viewer => 0.26
+    * rssyl => 0.26
+    * vala => 0.7.9
+    * mpd => 0.15.8
+    * libxml2 => 2.7.6
+    * mp => 5.1.3
+    * scite => 2.01
+    * beaver => 0.4.0rc1
+    * xvkbd => 3.1
+    * zim => 0.29
+    * mplayer-svn => 30605
+    * ntfs-3g => 2010.1.16
+    * xterm => 255
+    * lxpanel => 0.5.5
+
+===== Improvements =====
+
+    * tazlito (3.0) - Easier to customize LiveCD, GUI refactored, fixes and misc improvements
+    * slitaz-base-files (3.1) - 2 new scripts (man,ldd), OOO looks better and UTF-8
+    * slitaz-tools (3.5) - Better wifibox scan, UTF-8 locale with tazlocale, installer improved
+    * slitaz-doc (3.1) - Now provides a getting started guide
+
+===== Bugs =====
+
+
+^   Activity   ^    Open   ^    Closed  ^
+|    Bugs      |     68    |      57    |
+|    Features  |     36    |      24    |  
+|    Tasks     |      8    |      39    |
+
+
+    * Based on current figures
+
+===== Cartoon =====
+
+{{http://people.slitaz.org/~paul/cartoons/cartoon%237.png}}
+
+
+===== Tips and Tricks =====
+
+    * How do I run a remote Linux desktop in Windows 7: http://blogs.techrepublic.com.com/window-on-windows/?p=2138	
+
+===== Online =====
+
+    * SliTaz Guide for survival (Live Linux) CD USB flash - http://www.fixya.com/support/r3885135-slitaz_guide_survival_live_linux_cd_usb			
+
+===== Old Issues =====
+
+    * Click [[en:newsletter:oldissues|here]]
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/newsletter/oldissues/16.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/newsletter/oldissues/16.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,89 @@
+====== Monthly Newsletter - Issue 16 ======
+Lang:[[cn:handbook:newsletter|cn]] [[en:newsletter:start|en]]
+
+	* Written on 5th April 2010
+
+===== Latest News =====
+
+	* SliTaz version 3.0 released
+
+===== New Packages =====
+
+	* busybox-static
+	* httpfs-fuse-static
+	* ctags
+	* nss
+	* yad
+	* xorg-xf86-video-openchrome
+	* samba-common
+	* vym
+	* perl-net-xwhois
+	* rgzip
+	* sslh
+
+===== Updated  Packages =====
+
+	* ntfs-3g => 2010.1.16
+	* tor => 2.1.23
+	* lxpanel => 0.5.5
+	* task => 1.9.0
+	* libgphoto2 => 2.4.8
+	* libsoup => 2.29.91
+	* mplayer-svn => 30817
+	* libdevmapper => 1.02.44
+	* cryptsetup => 1.1.0
+	* bluez => 4.62
+	* midori => 0.2.4
+	* wvdial => 1.61
+	* ppp-* => 2.4.5
+	* squid => STABLE25
+	* xorg-xf86-video-intel => 2.7.1
+	* privoxy => 3.0.16-stable
+	* sudo => 1.7.2p5
+	* lighttpd => 1.4.26
+	* openssh => 5.4p1
+	* sftp-server => 5.4p1
+	* xterm => 256
+	* nano => 2.2.3
+	* isomaster => 1.3.7
+	* mhwaveedit => 1.4.18
+	* gtk-gnutella => 0.96.8
+
+===== Improvements =====
+
+	* tazlito (3.2) - box can now generate loram and loram/web
+	* slitaz-base-files (3.2) - release notes added
+	* slitaz-tools (3.8) - many improvements, po edits and fixes
+	* slitaz-doc (3.2) - release notes updated
+	* slitaz-boot-scripts (3.2) - updated
+	* slitaz-configs - small improvements
+	* slitaz-dev-tools - updated
+	* tazusb - ext2 and fat32 formatting added
+	* tazpkg - gui improvements and bug fixes
+
+===== Bugs =====
+
+
+^   Activity   ^    Open   ^    Closed  ^
+|    Bugs      |     85    |      73    |
+|    Features  |     35    |      29    |  
+|    Tasks     |     26    |      43    |
+
+
+	* Based on current figures
+
+===== Cartoon =====
+
+{{http://people.slitaz.org/~paul/cartoons/cartoon%238.png}}
+
+===== Tips and Tricks =====
+
+	* A System Monitoring Tool Primer: http://certcities.com/editorial/columns/story.asp?EditorialsID=413	
+
+===== Online =====
+
+	* Greetings from SliTaz 3.0 - http://kmandla.wordpress.com/2010/03/29/greetings-from-slitaz-3-0/			
+
+===== Old Issues =====
+
+    * Click [[en:newsletter:oldissues|here]]
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/newsletter/oldissues/17.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/newsletter/oldissues/17.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,203 @@
+====== Monthly Newsletter - Issue 17 ======
+Lang:[[cn:newsletter:start|cn]] [[en:newsletter:start|en]] [[fr:newsletter:start|fr]]
+
+	* Written on 9th May 2010
+
+===== Latest News =====
+
+        * SliTaz 'Summer of Documentation' 
+
+===== New Packages =====
+
+	* aria2
+	* exo
+	* gtkperf
+	* liblinebreak
+	* fbreader
+	* enigma
+	* xfce4-notification
+	* mountlo
+	* speedometer
+	* python-urwid
+	* geequie
+	* mpc-library
+	* cmatrix
+	* ffmpeg-svn
+	* get-prince
+	* get-msttcorefonts
+	* gen-init-cpio
+	* wikiss
+	* groff
+	* linmodem-hsfmodem
+
+===== Updated  Packages =====
+
+	* evilvte => 0.4.6
+	* yad => 0.2.0
+	* freetype => 2.3.12
+	* lrzip => 0.45
+	* mpfr => 2.4.2
+	* gmp => 4.3.2
+	* binutils => 2.20.1
+	* linux => 2.6.33.2
+	* libbfd => 2.20.1
+	* gcc => 4.5.0
+	* glibc => 2.11.1
+	* broadcom-wl => 5.60.48.36
+	* pixman => 0.16.0
+	* vala => 0.7.10
+	* libgmp = 4.5.0
+	* autoconf => 2.65
+	* coreutils => 8.4
+	* dillo => 2.2
+	* lxtask => 0.1.3
+	* bison => 2.4.2
+	* cmake => 2.6.4
+	* cpio => 2.11
+	* libxml2 => 2.7.7
+	* abiword => 2.8.4
+	* libart-lgpl =>2.3.21
+	* mpd => 0.15.9
+	* ncmpcpp => 0.5.3
+	* dstat = 0.7.1
+	* openssl => 1.0.0
+	* openssh => 5.5p1
+	* libssl => 1.0.0
+	* xorg-*proto => 1.2.0
+	* libcrypto => 1.0.0
+	* libdrm => 2.4.20
+	* xorg-lib* => various
+	* mesa => 7.8.1
+	* xorg-server => 1.8.0
+	* sftp-server => 5.5p1
+	* ndiswrapper => 1.56
+	* xorg-* => various
+	* xorg-xf86-video-* => various
+	* zile => 2.3.15
+	* kismet => 2010-01-R1
+	* emacs-pkg-lua-mode => 20100404
+	* hal-info => 20091130
+	* libedit => 3.0
+	* pm-utils => 1.2.6.1
+	* boxbackup-* => 0.11rc8
+	* curl => 7.20.1
+	* wine => 1.1.43
+	* sylpheed => 3.0.2
+	* cairo => 1.8.10
+	* nvidia => 195.36
+	* linmodem => 2.1.80~20091225
+	* fuse => 2.8.4
+	* git => 1.7.1
+	* vlc => 1.0.6
+	* ffmpeg => 0.5.1
+	* mercurial => 1.5.2
+	* subversion => 1.6.11
+	* zlib => 1.2.5
+	* sqlite => 3.6.23.1
+	* tcl => 8.5.8
+	* conky => 1.8.0
+	* audacity => 1.3.12
+	* asunder => 1.9.3
+	* grsync => 1.1.0
+	* audiofile => 0.2.7
+	* lguest => 2.6.33.2
+	* libwebkit => 1.2.0
+	* webkit-web-inspector => 1.2.0
+	* parted => 2.2
+	* gparted => 0.5.2
+	* grub2 => 1.98
+	* cmake => 2.8.1
+	* glib => 2.25.2
+	* libgio => 2.25.2
+	* pango => 1.28.0
+	* bazaar => 2.1.0
+	* avidemux => 2.5.2
+	* cdrkit => 1.1.10
+	* readom -> 1.1.10
+	* atk => 1.30.0
+	* aircrack-ng => 1.1
+	* gtk+ => 2.20.1
+	* firefox => 3.6.3
+	* irssi => 0.8.15
+	* bluefish => 2.0.0
+	* btrfs-progs => 0.19
+	* libtool => 2.2.6b
+	* e2fsprogs => 1.41.11
+	* menu-cache => 0.3.2
+	* openbox => 3.4.11.1
+	* mtpaint => 3.31
+	* clamav => 0.96
+	* tor => 0.2.1.26
+	* openal => 1.2.854
+	* bzip2 => 1.0.5
+	* bzlib => 1.0.5
+	* gaijim => 0.13.4
+	* gtkpod => 0.9.16
+	* neon => 0.29.3
+	* bind => 9.7.0-P1
+	* goffice => 0.8.2
+	* libgsf => 1.14.16
+	* transmission-* => 1.93
+	* glibmm => 2.24.2
+	* libgiomm => 2.24.2
+	* cariomm => 1.8.4
+	* pangomm => 2.26.2
+	* gtkmm => 2.20.3
+	* pkg-config => 0.23
+	* pmount => 0.9.20
+	* gnutls => 2.8.6
+	* perl-net-ssleay => 1.36
+	* dahdi-* => 2.3.0
+	* x11vnc-* => 0.9.10
+	* asterisk => 1.6.2.7
+	* diffutils => 3.0
+	* cups-pam => 1.4.2
+	* davfs2 => 1.4.6
+	* ruby => 1.9.1
+	* ptlib => 2.6.5
+	* opal => 3.6.6
+	* ekiga => 3.2.6
+	* seamonkey => 2.0.4
+	* linmodem-slmodem => 2.9.11-20100303
+	* depmod => 3.11.1
+	* module-init-tools =>3.11.1
+	* patch => 2.6.1
+	* wireshark => 1.2.8
+	* testdisk => 6.11.3
+	* file => 5.04
+	* libmagic => 5.04
+	* pidgin => 2.6.6
+	* claws-mail-* => various
+	* gtkhtml2-viewer => 2.27
+	* rssl => 0.27
+
+===== Improvements =====
+
+	* New toolchain 
+	* tazwok updated (3.2)
+
+===== Bugs =====
+
+^   Activity   ^    Open   ^    Closed  ^
+|    Bugs      |     94    |      73    |
+|    Features  |     37    |      29    |  
+|    Tasks     |      27   |      43    |
+
+
+	* Based on current figures 
+
+===== Cartoon =====
+
+{{http://people.slitaz.org/~paul/cartoons/cartoon%239.png}}
+
+===== Tips and Tricks =====
+
+	*  How-To: Grep Tricks for Linux Users: http://www.itworld.com/it-managementstrategy/106032/how-to-grep-tricks-linux-users		
+
+===== Online =====
+
+	* SliTaz Linux 3.0 lends credence to the phrase “Small but Powerful” - http://www.linuxcritic.com/slitaz-linux-30-lends-credence-phrase-small-powerful/				
+
+===== Old Issues =====
+
+	* Click [[en:newsletter:oldissues|here]]
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/newsletter/oldissues/18.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/newsletter/oldissues/18.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,163 @@
+====== Monthly Newsletter - Issue 18 ======
+Lang:[[cn:newsletter:start|cn]] [[en:newsletter:start|en]] [[fr:newsletter:start|fr]]
+
+	* Written on 11th July 2010
+
+===== Latest News =====
+
+        * SliTaz moves to new FSF server
+
+===== New Packages =====
+
+	* qt4-phonon
+	* php-curl
+	* libegl-mesa
+	* emacs po-mode
+	* gimp-dev
+	* libburn
+	* libisofs
+	* xfburn
+	* liferea
+	* arora
+	* libcanberra
+	* xvidcore
+	* barcode
+	* echinus
+	* gtk-theme-switch
+	* gtk-engines-rezlooks
+	* deadbeef
+	* linux-logfs
+	* linux-configfs
+	* linux-toshiba
+	* linux-dlm
+	* qiv
+	* normalize
+	* python-pybluez
+	* attica
+	* wxpython
+	* strigi
+	* gammu
+	* ypserv
+	* yp-tools
+	* ypbind-mt
+	* nis
+	* git-gui
+	* cpufrequtils
+	* python-mygpoclient
+	* gpodder
+	* turnserver
+	* osip
+	* exosip
+	* linphone
+	* bygfoot
+
+===== Updated  Packages =====
+
+	* claws-mail-extras => 3.7.6
+	* boxbackup => 0.11rc8
+	* yad => 0.2.1
+	* zile => 2.3.1.6
+	* lives => 1.3.3
+	* wine => 1.1.44
+	* aria2 => 1.9.3
+	* slang => 2.2.2
+	* libpng => 1.2.43
+	* tint2 => 0.9
+	* emelfm2 => 0.7.2
+	* pngcrush => 1.7.10
+	* optipng => 0.6.4
+	* yasm => 1.0.0
+	* nasm => 2.08.01
+	* gfortran => 4.5.0
+	* libarchive => 2.8.3
+	* pidgin => 2.7.1
+	* gettext => 0.18
+	* linux => 2.6.34
+	* lguest => 2.6.34
+	* iptables => 1.4.7
+	* emacs => 23.2
+	* mplayer-svn => 31179
+	* goffice => 0.8.3
+	* xvkbd => 3.2
+	* libxcb => 1.6
+	* xcb-proto => 1.6
+	* xorg-xf86-video-{openchrome, nv, s3, neomagic, mga}
+	* catalyst => 10.4
+	* midori => 0.2.6
+	* libwebkit => 1.2.1
+	* elinks => 0.11.7
+	* webkit-web-inspector => 1.2.1
+	* avidemux => 2.5.3
+	* yasm => 1.0.1
+	* awesome => 3.4.5
+	* pekwm => 0.1.12
+	* bastet => 0.43
+	* glibc => 2.11.2
+	* sudoku-savant => 1.3
+	* e2fsprogs => 1.41.12
+	* minicom => 2.4
+	* udev => 156
+	* nscd => 2.10.2
+	* task => 1.9.1
+	* clamav => 0.96.1
+	* vorbis-tools => 1.4.0
+	* libogg => 1.2.0
+	* libvorbis => 1.3.1
+	* libtheora => 1.1.1
+	* parted => 2.3
+	* alsa-lib => 1.0.23
+	* scribus => 1.3.7
+	* busybox => 1.17.0
+	* xfce4-taskmanager => 1.0.0
+	* geany => 0.19
+	* p7zip => 9.13
+	* ario => 1.4.4
+	* sudo => 1.7.2p7
+	* fetchmail => 6.3.17
+	* usbutils => 0.86
+	* libusb => 1.0.8
+	* libusb-compact => 0.1.3
+	* amsn => 0.98.3
+	* amule => 2.2.6
+	* libxml2-tools => 2.7.7
+	* osmo => 0.2.10
+	* dmsetup => 1.02.44
+	* bluez-dev =>4.62
+	* nscd => 2.11.2
+	* vte => 0.25.1
+	* krb5 => 1.8.2
+	* strace => 4.5.20
+	* pyqt-x11-gpl => 4.7.3
+	* speex => 1.2rc1
+
+===== Improvements =====
+
+	* tazwok updated (3.2.1)
+	* slitaz-tools updated (3.8.1)
+	* slitaz-boot-scripts updated (3.4.1)
+
+===== Bugs =====
+
+^   Activity   ^    Open   ^    Closed  ^
+|    Bugs      |     101    |      75    |
+|    Features  |     37    |      29    |  
+|    Tasks     |      28   |      43    |
+
+
+	* Based on current figures 
+
+===== Cartoon =====
+
+{{http://people.slitaz.org/~paul/cartoons/cartoon%2310.png}}
+
+===== Tips and Tricks =====
+
+	*  Roundup - Text Based Text Editors: http://fosswire.com/post/2010/07/text-based-text-editors/		
+
+===== Online =====
+
+	* Slitaz Tutorials (youtube)  - http://www.youtube.com/watch%3Fv%3D6YQrBgNGQrw			
+
+===== Old Issues =====
+
+	* Click [[en:newsletter:oldissues|here]]
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/newsletter/oldissues/19.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/newsletter/oldissues/19.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,154 @@
+====== Monthly Newsletter - Issue 19 ======
+Lang:[[cn:newsletter:start|cn]] [[en:newsletter:start|en]] [[fr:newsletter:start|fr]] [[ru:newsletter:start|ru]]
+
+    * Written on 29th August 2010
+
+===== Latest News =====
+
+    * Handbook translated and updated into Russian (thanks Lexeii, Onion, Cyril)
+
+===== New Packages =====
+
+    * hostapd
+    * xfce4-dev-tools
+    * tmux
+    * tazwikiss
+    * exiftool
+    * libgtkimageview 
+    * ufraw
+    * macchanger
+    * libcss
+    * libwapcaplet
+    * elfutils
+    * lxrandr
+    * lxterminal
+    * masqmail
+    * wbarconf
+    * unrar
+    * perl-rfc-rfc822-address
+    * perl-parse-recdescent
+    * perl-text-iconv
+    * silc-server
+    * nut
+    * uclibc-cross-compiler
+    * openttd
+    * opengfx
+    * sysstat
+    * icecast
+    * uget
+    * glew
+    * get-google-talkplugin
+    * qemu-{arm,mips,ppc,x86}
+    * puzzles
+    * ruby-gtk2
+    * thunderbird
+    * thunderbird-langpack-*
+
+===== Updated  Packages =====
+
+    * sip => 4.10.2
+    * busybox => 1.17.1
+    * pidgen => 2.7.1
+    * john => 1.7.6
+    * isof => 4.83
+    * chkrootkit => 0.49
+    * libiec61883 => 1.2.0
+    * logrotate => 3.7.9
+    * calcurse => 2.8
+    * nss-ldap => 265
+    * pam-ldap => 185
+    * c-client => 2007e
+    * exo => 0.3.107
+    * goffice => 0.8.6
+    * gnumeric => 1.10.7
+    * xfce4* => 4.6.2
+    * thunar => 1.0.2
+    * libxfcegui4 => 4.6.4
+    * libraw1394 => 2.0.5
+    * task => 1.9.2
+    * fotoxx => 10.8
+    * printoxx => 2.7
+    * zim => 0.48
+    * xorg-xf86-input-synaptics  => 1.2.99.1
+    * keepass => 0.4.3
+    * tmux => 1.3
+    * py3k => 3.1.2
+    * xchat => 3.8.8
+    * xorg-xf86-input-elographics  => 1.2.4
+    * xorg-xf86-input-plpevtch  => 0.5.0
+    * beaver => 0.4.0
+    * libmng => 1.0.10
+    * netsurf => 2.5
+    * memtest => 4.10
+    * wine => 1.2
+    * wesnoth => 1.8.3
+    * gcc => 4.5.1
+    * catalyst => 10.7
+    * cpufrequtils => 008
+    * exiftool => 8.27
+    * dbus => 1.2.24
+    * apache-ant => 1.8.1
+    * krb5 => 1.8.3
+    * libpng => 1.4.3
+    * jpeg => 8b
+    * lirc => 0.8.6
+    * ecj => 3.6
+    * dbus-glib => 0.86
+    * dbus-python => 0.83.1
+    * eggdbus => 0.6
+    * Policykit => 0.97
+    * GConf => 2.31.7
+    * bazaar => 2.2.0
+    * glib => 2.25.13
+    * libftdi => 0.18
+    * scite => 2.10
+    * srcpd => 2.1.1
+    * libgdiplus => 0.18
+    * mono => 2.6.7
+    * pixman => 0.18.0
+    * icedtea6 => 1.8.1
+    * pango => 1.28.1
+    * freetype => 2.4.2
+    * zile => 2.3.19
+    * yad => 0.3.1
+    * evince => 2.30.3
+    * libproxy => 0.4.2
+    * firefox => 3.6.8
+    * qemu => 0.12.5
+    * putty  =>0.60-2010-08-29
+    * kismet  => 2010-07-R1
+    * libedit => 20100424-3.0
+    * pm-utils => 1.4.1
+    * powertop => 1.13
+    * xorg-xf86-video-neomagic => 1.2.5
+
+===== Improvements =====
+
+    * tazbb - add stable support for log.php
+    * mirror-tools - add mirror-info web page
+
+===== Bugs =====
+
+^   Activity   ^    Open   ^    Closed  ^
+|    Bugs      |     97    |     86     |
+|    Features  |     39    |     31     |  
+|    Tasks     |     26    |     33     |
+
+
+* Based on current figures 
+
+===== Cartoon =====
+
+{{http://people.slitaz.org/~paul/cartoons/cartoon%2311.png}}
+
+===== Tips and Tricks =====
+
+    * Text editing with Nano made easy: http://tuxradar.com/content/text-editing-nano-made-easy	
+
+===== Online =====
+
+    * One floppy, dozens of tools  - http://kmandla.wordpress.com/2010/07/23/one-floppy-dozens-of-tools/		
+
+===== Old Issues =====
+
+    * Click [[en:newsletter:oldissues|here]]
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/newsletter/oldissues/20.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/newsletter/oldissues/20.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,219 @@
+====== Monthly Newsletter - Issue 20 ======
+Lang:[[cn:newsletter:start|cn]] [[en:newsletter:start|en]] [[fr:newsletter:start|fr]] [[ru:newsletter:start|ru]]
+
+	* Written on 16th October 2010
+
+===== Latest News =====
+
+        * Scratchbook translated into Russian (thanks Lexeii, Onion, Cyril)
+        * Over 400 packages updated
+
+
+===== New Packages =====
+
+	* clucene
+	* fbxkb
+	* droid-font
+	* uclibc
+	* recorder
+	* rt-source
+	* fbida
+	* cd-discid
+	* rubyripper
+	* grub4dos-linux
+	* libtirpc
+	* nfs-utils
+	* rpcbind
+	* surf
+	* libplist
+	* adeskbar
+	* polipo
+	* vidalia
+	* aspell-da
+	* zsnes
+	* slsnif
+	* scummvm
+	* frogatto
+	* xbill
+	* devede
+	* gen-gs
+	* rawstudio
+	* rsnapshot
+	* stellarium
+	* accessx
+	* iron-linux
+	* warzone2100
+	* pwgen
+	* ftgl
+	* ilmbase
+	* openexr
+	* cinepaint
+	* lincity-ng
+	* chrpath
+	* ldapvi
+	* assaultcube
+	* libdnet
+	* xcircuit
+	* gdk-pixbuf
+	* winetricks
+	* linux-api-headers
+	* btanks
+
+===== Updated  Packages (abridged) =====
+
+	* rddtool => 1.4.4
+	* transmission => 2.10
+	* libwebkit => 1.24
+	* vlc => 1.1.4
+	* midori => 0.2.8
+	* git => 1.7.3.1
+	* mercurial => 1.6.4
+	* abiword => 2.8.6
+	* apache => 2.2.16
+	* lighttpd => 1.4.28
+	* clamav = 0.96.3
+	* audacious => 2.4.0
+	* asunder => 2.0
+	* sudo => 1.7.4p4
+	* goffice => 0.8.10
+	* bluefish => 2.0.1
+	* aria2 => 1.10.3
+	* thunderbird => 3.1.3
+	* firefox => 3.6.10
+	* pkg-config => 0.25
+	* automake => 1.11.1
+	* tar => 1.23
+	* bluez => 4.75
+	* geany => 0.19.1
+	* ntfs-3g => 2010.8.8
+	* gimp => 2.6.11
+	* babl => 0.1.2
+	* gparted => 0.6.4
+	* gegl => 0.1.2
+	* gnumeric => 1.10.11
+	* cups => 1.4.4
+	* openssh => 5.6p1
+	* openssl => 1.0.0a
+	* buildbot => 0.8.1
+	* cabextract => 1.3
+	* pidgin => 2.7.3
+	* seamonkey => 2.0.8
+	* gphoto => 2.4.9
+	* gtksourceview => 2.10.4
+	* cdrdao => 1.2.3
+	* chmlib => 0.40
+	* chocolate-doom => 1.4.0
+	* aaphoto => 0.38
+	* dosbox => 0.74
+	* hardinfo => 0.5.1
+	* sqlite => 3.7.2
+	* lcms => 0.19
+	* lame => 3.98.4
+	* centerim => 4.22.9
+	* curl => 7.21.1
+	* gnomeplayer => 0.9.9.2
+	* mplayer => 1.0rc3
+	* smplayer => 0.6.9
+	* taglib => 1.6.3
+	* easytag => 2.1.6
+	* ddrescue => 1.13
+	* cryptsetup => 1.1.3
+	* poppler => 0.14.3
+	* nano => 2.2.5
+	* filezilla => 3.3.4.1
+	* zsh => 4.3.10
+	* xterm => 262
+	* pixman => 0.18.4
+	* wormux => 0.9.2.1
+	* wpa_supplicant => 0.7.3
+	* lxterminal => 0.1.9
+	* lxappearance => 0.4.0
+	* xine-lib => 1.1.19
+	* grsync => 1.1.1
+	* gpodder => 2.8
+	* beaver => 0.4.1
+	* fluxbox => 1.1.1
+	* bluefish => 2.0.2
+	* gtkspell => 2.0.16
+	* bison => 2.4.3
+	* m4 => 1.4.15
+	* gawk => 3.1.8
+	* ghostscript => 9.00
+	* epeak => 1.44.05
+	* jack-audio-connection-kit => 0.118.0
+	* iptables => 1.4.9.1
+	* gxine => 0.5.905
+	* imagemagick => 6.6.4-10
+	* dosfstools => 3.0.10
+	* dialog => 1.1-20100428
+	* cmake => 2.8.2
+	* gettext => 0.18.1.1
+	* gdb => 7.2
+	* nitrogen => 1.5.1
+	* readline => 6.1
+	* gstreamer => 0.10.30
+	* recordmydesktop => 0.3.8.1
+	* samba => 3.5.6
+	* wireshark => 1.4.1
+	* wicd => 1.7.0
+	* sylpheed => 3.0.3
+	* bzip2 => 1.0.6
+	* nmap => 5.21
+	* pcre => 8.10
+	* tiff => 3.9.4
+	* git-gui => 0.13.0
+	* homebank => 4.3
+	* lxpanel => 0.5.6
+	* tcl, tk => 8.5.9
+	* mutt => 1.5.21
+	* ruby => 1.9.2-p0
+	* mirage => 0.9.5.1
+	* mpg123 => 1.12.4
+	* gnuplot => 4.4.0
+	* feh => 1.9
+	* parcelite => 0.9.2
+	* awesome => 3.4.8
+	* subversion => 1.6.13
+	* make => 3.82
+	* conky => 1.8.1
+	* php => 5.2.14
+	* postgresql => 9.0.1
+	* atk => 1.32.0
+	* cairo => 1.10.0
+	* pango => 1.28.3
+	* gtk+ => 2.22.0
+	* wine =>1.2.1
+	* hplip => 3.10.9
+	* busybox => 1.17.3
+	* curl => 7.21.2
+	* xorg-server => 1.8.2
+
+===== Improvements =====
+
+	* Website updated (mailing list, artwork, sitemap)
+
+===== Bugs =====
+
+^   Activity   ^    Open   ^    Closed  ^
+|    Bugs        |     102    |     86     |
+|    Features  |     39      |     31     |  
+|    Tasks       |     24      |     48     |
+
+
+	* Based on current figures 
+
+===== Cartoon =====
+
+{{http://people.slitaz.org/~paul/cartoons/cartoon%231.png}}
+
+===== Tips and Tricks =====
+
+        * How To Use Bash Parameter Substitution Like A Pro: http://www.cyberciti.biz/tips/bash-shell-parameter-substitution-2.html
+
+===== Online =====
+
+        * Spotlight on Linux: SliTaz GNU/Linux 3.0  - http://www.linuxjournal.com/content/spotlight-linux-slitaz-gnulinux-30		
+
+===== Old Issues =====
+
+    * Click [[en:newsletter:oldissues|here]]
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/newsletter/oldissues/21.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/newsletter/oldissues/21.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,282 @@
+====== Monthly Newsletter - Issue 21 ======
+Lang:[[cn:newsletter:start|cn]] [[en:newsletter:start|en]] [[es:newsletter:start|es]] [[fr:newsletter:start|fr]] [[ru:newsletter:start|ru]]
+
+	* Written on 5th December 2010
+
+===== Latest News =====
+
+        * Guides translated into Russian (thanks Lexeii, Onion, Cyril)
+        * Over 400 packages updated
+
+===== New Packages =====
+
+        * libbonobo
+        * rarian
+        * libasyncns
+        * bin86
+        * hd2u
+        * mupen64plus
+        * pcsxr-svn
+        * ladspa
+        * raptor
+        * liblrdf
+        * libtar
+        * hydrogen
+        * bmpanel2
+        * aubio
+        * fftw
+        * frei0r-plugins
+        * liblo
+        * mlt
+        * fluidsynth
+        * ardour
+        * openshot
+        * libquicktime
+        * x264
+        * mupdf
+        * python-chardet
+        * jbig2dep
+        * openjpeg
+        * gavl
+        * swig
+        * vde2
+        * watchdog
+        * goocanvas
+        * portmidi
+        * mixxx
+        * singularity
+        * lmms
+        * deluge
+        * tinyproxy
+        * docbook-xml-{5,4.*}
+        * docbook-xsl-{ns}
+        * iasl
+        * ndisc6
+        * fop
+        * flam3
+        * electricsheep
+        * nanochess
+        * p4wn
+        * checkers
+        * othello
+        * hatenarunner
+        * chess3d
+        * sudoku
+        * jstetris
+        * virtualbox-ose
+        * qtconfig
+        * atkmm
+        * perl-file-tail
+        * txt2tags
+        * udhcpc6-fake
+        * lorcon
+        * libnet
+        * airpwn
+        * icewm
+        * cssc
+        * aspell-pl
+        * xorg-xf86-video-r128 6.8.1
+        * libfm
+        * pcmanfm2
+        * atftp
+        * aspell-nl
+        * cherokee
+        * linux-firmware
+        * stella
+        * sleuthkit
+        * linux-nfsd 
+        * linux-autofs
+        * autofs
+        * aufs
+        * geoip
+        * wavpack
+        * libass
+        * xorg-xf86-video-vmware
+        * which
+        * fcitx
+        * python-notify
+        * decibel
+        * stardict
+        * firefox-langpack-zh_CN
+        * wordpress
+        * drupal
+        * perl-locale-gettext
+        * perl-yaml
+        * libsdl-perl
+        * libsdl-pango
+        * frozen-bubble
+        * vnc2flv
+        * linux-iscsi
+        * aescrypt
+        * whois
+        * zvbi
+        * meld
+        * libglademm
+        * visualboyadvance
+        * aiksaurus
+        * lyx
+
+===== Updated  Packages (abridged) =====
+
+        * xorg => 1.9.2 
+        * libsndfile => 1.0.23
+        * wireshark => 1.4.2
+        * curl => 7.21.2
+        * libdrm => 2.4.22
+        * mesa => 7.8.2
+        * mpd => 1.15.15
+        * ncmpcpp => 5.5
+        * transmission => 2.12
+        * mtools => 4.0.14
+        * pyopenssl => 0.10
+        * pycairo => 1.8.10
+        * pygobject => 2.26.0
+        * pygtk => 2.22.0
+        * cdrkit => 1.1.11
+        * openldap => 2.4.23
+        * viewnoir => 1.0
+        * apr-util => 1.3.10
+        * apache => 2.2.17
+        * libsamplerate => 0.1.7
+        * dbus => 1.4.0
+        * udev => 163
+        * hal => 0.5.14
+        * freeimage => 3141
+        * vte => 0.27.2
+        * coreutils => 8.6
+        * mgetty => 1.1.37
+        * firefox => 3.6.12
+        * thunderbird => 3.0.15
+        * icedtea6-{jdk,jre} => 1.9.1
+        * libfirefox => 3.6.12
+        * aria2 => 1.10.5
+        * arora => 0.11.0
+        * gnutls => 2.10.2
+        * pidgin => 2.7.7
+        * ffmpeg => 0.6.1
+        * qemu => 0.13.0
+        * ffplay => 0.6.1
+        * nss => 3.12.8
+        * vlc => 1.1.15
+        * adeskbar => 0.4.2
+        * python-pygame => 1.9.1release
+        * libcap => 2.19
+        * pam => 1.1.2
+        * squirrelmail => 1.4.21
+        * valgrind => 3.6.0
+        * vala => 0.10.0
+        * syslinux => 4.03
+        * mono => 2.8.1
+        * clamav => 0.96.5
+        * scite => 2.22
+        * seamonkey => 2.0.10
+        * tar => 1.25
+        * iptables => 1.4.10
+        * poedit => 1.4.6.1
+        * fotoxx => 10.12
+        * dstat => 0.7.2
+        * remind => 03.01.10
+        * midori => 0.2.9
+        * libvorbis => 1.3.2
+        * mysql => 5.1.53
+        * aria2 => 1.10.6
+        * libpcap => 1.1.1
+        * snort => 2.9.0.2
+        * mtr => 0.80
+        * ncdu => 1.7
+        * inkscape => 0.48.0
+        * mercurial => 1.7.2
+        * dhcp => 4.2.0-P1
+        * cmake => 2.8.3
+        * linux 2.6.36
+        * gnome-mplayer => 1.0.0
+        * gecko-mediaplayer => 1.0.0
+        * zim => 0.49
+        * amule => r10365
+        * squid => 3.1.9
+        * alsaplayer => 0.99.81
+        * zip => 3.0
+        * ruby-gtk2 => 0.90.5
+        * mc => 4.7.0.10
+        * qt4 => 4.7.1
+        * cups => 1.4.5
+        * bluez => 4.80
+        * perl-xml-parser => 2.40
+        * privoxy => 3.0.17
+        * glib => 2.26.1
+        * gtk+ => 2.22.1
+        * gphoto2 => 2.4.10
+        * filezilla => 3.3.5.1
+        * elinks => 0.13
+        * pcmciautils => 017
+        * pciutils => 3.1.7
+        * usbutils => 0.91
+        * pixman => 0.20.0
+        * zenity => 2.32.1
+        * claws-mail => 3.7.8
+        * xane => 0.998
+        * imagemagick => 6.6.5-9
+        * libxml2 => 2.7.8
+        * nano => 2.2.6
+        * scribus => 1.3.8
+        * busybox => 1.17.4
+        * x11vnc => 0.9.12
+        * uget => 1.6.1
+        * subversion => 1.6.15
+        * tor => 0.2.1.27
+        * gnumeric => 1.10.12
+        * dahdi-tools => 2.4.0
+        * rpm4 => 4.8.1
+        * hydra => 5.9
+        * libsoup => 2.32.2
+        * python => 2.7.1
+        * gstreamer => 0.10.31
+        * GConf => 2.32.1
+        * bind => 9.7.2-P3
+        * freetype => 2.4.4
+        * openssl => 1.0.0c
+        * geany => 0.19.2
+        * gajim => 0.14.1
+        * mpfr => 3.0.0p8
+        * poppler => 0.14.5
+        * pidgin-facebookchat => 1.69
+        * wine => 1.2.2
+        * twisted => 10.2.0
+        * git => 1.7.3.3
+
+===== Improvements =====
+
+        * slitaz-tools (3.9.1) 
+        * slitaz-tools-boxes (3.9.1)
+        * slitaz-configs (4.0)
+        * slitaz-base-files (4.1)
+        * slitaz-doc (4.1)
+        * tazpkg (4.1.1)
+
+===== Bugs =====
+
+\\
+
+^   Activity   ^    Open   ^    Closed  ^
+|    Bugs        |     107    |     90     |
+|    Features    |     41     |     32     |  
+|    Tasks       |     24     |     48     |
+
+
+	* Based on current figures 
+
+===== Cartoon =====
+
+{{http://people.slitaz.org/~paul/cartoons/cartoon%232.png}}
+
+===== Tips and Tricks =====
+
+        * Linux Server Troubleshooting With strace: http://www.linuxplanet.com/linuxplanet/tutorials/7229/1/
+
+===== Online =====
+
+        * SliTaz GNU/Linux 3.0 Screencast Review  - http://linuxfilesystem.com/uncategorized/slitaz-gnulinux-3-0-screencast-review	
+
+===== Old Issues =====
+
+        * Click [[en:newsletter:oldissues|here]]
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/newsletter/start.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/newsletter/start.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,246 @@
+====== Monthly Newsletter - Issue 22 ======
+Lang:[[cn:newsletter:start|cn]] [[start|en]] [[es:newsletter:start|es]] [[fr:newsletter:start|fr]] [[ru:newsletter:start|ru]]
+
+	* Written on 30th January 2011
+
+===== Latest News =====
+
+        * Website, Wiki, Labs updated
+        * Newsletter translated into Spanish (thanks seacat)
+
+===== New Packages =====
+
+        * ecm
+        * mdk3
+        * airoscript-ng
+        * php-dbase
+        * pycurl
+        * pidgin-musictracker
+        * linapple
+        * dvgrab
+        * ogmrip
+        * at
+        * chntpw
+        * disktype
+        * fakeroot
+        * xorg-xf86-input-vmmouse
+        * caps
+        * alsaequal
+        * linux-without-modules
+        * TeXmacs 
+        * bzflag
+        * pysqlite
+        * celestia
+        * perl-libwww
+        * pyrex
+        * pywebkitgtk
+        * pyorbit
+        * gnome-mime-data.
+        * php-soap
+        * phpvirtualbox
+        * libmicrohttpd
+        * gnome-vfs
+        * fcitx-zm
+        * gnome-python
+        * miro
+        * clisp
+        * cowpatty
+        * asleap
+        * scrub
+        * postfixadmin
+        * igmpproxy
+        * wyrd
+        * pktstat
+        * get-LibreOffice
+        * weechat
+        * qrencode
+        * phpqrcode
+        * perl-smtp-ssl
+        * cairo-dock
+        * cairo-dock-plugins
+        * gambas2
+        * util-linux-ng-setterm
+        * yajl
+        * urlgrabber
+        * perl-text-csv
+        * polkit
+        * garcon
+        * libxfce4ui
+        * gzip
+        * vzctl
+        * vzquota
+        * thunar-vfs
+        * ovz-web-panel
+        * sqlite3-ruby
+        * xorg-makedepend
+        * libQtTest
+        * libssh
+        * openmpi
+        * shellinabox
+        * freerdp
+        * remminia
+
+===== Updated  Packages (abridged) =====
+
+        * scribus => 1.3.9
+        * libogg => 1.2.2
+        * gpodder => 2.12
+        * gnutls => 2.10.4
+        * feh => 1.11
+        * xterm => 267
+        * gst-plugins-good => 0.10.26
+        * cairomm => 1.8.6
+        * lvm2 => 2.02.81
+        * clutter-gtk => 0.10.8
+        * aria2 => 1.10.9
+        * fotoxx => 11.01
+        * whois => 5.0.10
+        * py3k=> 3.1.3
+        * firefox => 3.6.13
+        * seamonkey => 2.0.11
+        * thunderbird => 3.1.7
+        * audacious => 2.4.3
+        * transmission => 2.13
+        * nasm => 2.09.04
+        * cherokee => 1.0.18
+        * libisofs => 0.6.40
+        * libburn => 0.9.0
+        * dhcp => 4.2.0-P2
+        * pcre => 8.12
+        * sqlite => 3.7.4
+        * php => 5.2.17
+        * docbook-xsl => 1.76.1
+        * zenity => 2.32.1
+        * gparted => 0.7.1
+        * xorg-server => 1.9.3
+        * buildbot => 0.8.2
+        * beautifulsoup => 3.2.0
+        * e2fsprogs => 1.41.14
+        * mixxx => 1.8.2
+        * curl => 7.21.3
+        * mysql => 5.1.54
+        * postgresql => 9.0.2
+        * postfix => 2.8.0
+        * freeciv => 2.2.4
+        * git => 1.7.3.5
+        * viewnoir => 1.1
+        * drupal => 6.20
+        * scite => 2.23
+        * udev => 1.6.5
+        * libdrm => 2.4.23
+        * terminal => 0.4.5
+        * evilvte => 0.4.7
+        * bogofilter=> 1.2.2
+        * bluez => 4.82
+        * pyneighborhood => 0.5.3
+        * lmms => 0.4.9
+        * wipe=> 2.3.1
+        * tor => 0.2.1.29
+        * pidgin => 2.7.9
+        * leafpad => 0.8.18.1
+        * zsh => 4.3.11
+        * snort => 2.9.0.3
+        * parcellite => 0.9.3
+        * busybox => 1.18.2
+        * netatalk=> 2.1.5
+        * lvm2 => 2.02.79
+        * winetricks => 20110123
+        * ethtool => 2.6.36
+        * speedometer => 2.7
+        * task => 1.9.3
+        * units=> 1.88
+        * cryptsetup => 1.2.0
+        * deadbeef => 0.4.4
+        * exiv => 0.20
+        * zile => 2.3.21
+        * sip => 4.12
+        * fsarchiver => 0.6.12
+        * ruby => 1.9.2-p136
+        * mc => 4.7.5
+        * vala => 0.10.2
+        * mercurial => 1.7.3
+        * wordpress => 3.0.4
+        * elfutils=> 0.151
+        * yad => 0.7.2
+        * libwebkit => 1.2.6
+        * rrdtool => 1.4.5
+        * htop => 0.9
+        * cups => 1.4.6
+        * geany => 0.20
+        * shell-fm => 0.7
+        * bash=> 4.1
+        * module-init-tools => 1.12
+        * make => 3.82
+        * coreutils => 0.9
+        * isomaster => 1.3.8
+        * ncmpcpp => 0.5.6
+        * sudo => 1.7.4p5
+        * wireshark => 1.4.3
+        * nicotine  => 1.2.16
+        * mlt => 0.6.0
+        * mpc => 0.20
+        * gnupg => 2.0.17
+        * dbus => 1.4.1
+        * file => 5.0.5
+        * exo => 0.6.0
+        * xfce4-* => 4.8.0
+        * dmidecode => 2.11
+        * gst-plugins-{good, bad, base, ugly} => 0.10.*
+        * libdrm => 2.4.23
+        * mesa => 7.10
+        * linux => 2.6.37
+        * aufs => 20110122
+        * catalyst => 10.12
+        * orage => 4.8.0
+        * kismet => 2011-01-R1
+        * murrine => 2011-01-R1
+        * ntfs-3g => 2011.1.15
+        * vlc => 1.1.6
+        * openssh => 5.7p1
+        * memtest => 4.20
+        * inkscape => 0.48.1
+        * nmap => 5.10
+        * ddrescue  => 1.14
+        * xz => 5.0.1
+        * mplayer => 1.0rc4
+        * xorg-xproto => 7.0.20
+
+===== Improvements =====
+
+        * slitaz-configs-base added (4.0) 
+        * slitaz-tools (4.0.2)
+        * slitaz-boot-scripts (3.4.3.1)
+        * slitaz-configs (4.1)
+        * slitaz-base-files (4.1.2)
+        * tazpkg (4.2.3)
+        * tazlito (3.3)
+        * tazchroot (0.0.4)
+        * libtaz (0.0.4)
+ 
+===== Bugs =====
+
+\\
+
+^   Activity   ^    Open   ^    Closed  ^
+|    Bugs        |     102    |     118    |
+|    Features    |     44     |     43     |  
+|    Tasks       |     22     |     79     |
+
+
+	* Based on current figures 
+
+===== Cartoon =====
+
+{{http://people.slitaz.org/~paul/cartoons/cartoon%233.png}}
+
+===== Tips and Tricks =====
+
+        * Python for Newbies – Part1: http://temporaryland.wordpress.com/2011/01/26/python-for-newbies/
+
+===== Online =====
+
+        * Install the SliTaz operating system in VirtualBox  - http://www.unixweblog.com/2011/01/installing-linux-slitaz-small-30-mb-linux-operating-system-in-virtualbox/		
+
+===== Old Issues =====
+
+        * Click [[en:newsletter:oldissues|here]]
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/references/start.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/references/start.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,13 @@
+This category is to provide useful linux references/articles/bookmarks. Please feel free to add any topic that you think may be useful for the community. 
+
+===== Development ======
+
+  * Writing Shell scripts: http://linuxcommand.org/
+  * ... 
+
+===== Linux References =====
+
+  * [[http://www.digilife.be/quickreferences/QRC/The%20One%20Page%20Linux%20Manual.pdf | One Page Manual]] (Not everything applies to Slitaz)
+  * [[http://www.pixelbeat.org/cmdline.html|Another command line reference]]
+  * Have a .tar.gz file? [[http://www.tuxfiles.org/linuxhelp/softinstall.html|Compiling Software in Linux]] - note you will probably need the //slitaz-toolchain// and a few //*-dev// packages (a few useful ones can be installed as //slitaz-dev-pkgs//.
+  * [[http://www.howtogeek.com/tag/linux/|Linux How-To Articles, Tips, and Guides]] :: How-To Geek
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/scratchbook/start.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/scratchbook/start.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,50 @@
+====== Scratchbook ======
+
+Index of documents, step by step construction of a mini GNU/LINUX LiveCD and installation instructions. 
+
+===== Introduction =====
+
+The scratchbook allows you to track the creation of the first public release of SliTaz and make a trip to the heart of GNU/LINUX. You'll be able to customize your new system or create your own autonomous distro running in system memory (RAM) that's fully installable on a hard drive or USB key. Once started you'll be able to remove the CD-ROM and still have SliTaz working. SliTaz can also be used as an environment in which we can chroot or use the cdrom for multitasking. The only prerequisite is a host distribution in which you can store libraries, use a compiler and development tools, etc. The host system can be a chrooted development environment, a minimal distro, SliTaz installed on a hard drive or a 'general' distro such as Debian, Slackware, Fedora, Gentoo, Mandriva, Arch, etc. Note that nothing is installed in the host system by our commands.
+
+SliTaz uses the 'Swiss Army Knife' BusyBox as the basis of the system and the Linux Kernel, it runs embedded using a small memory footprint and provides many files. BusyBox is our main source of information and it's a utility of the Debian project which we use and cherish.
+
+SliTaz uses the Syslinux bootloader and an archived initramfs compressed with cpio. This archive is then decompressed in memory at boot by the kernel into a system of no fixed size, retaining control over init. At the time of compilation or copying of applications, we use strip to clean the repositoiries. The system commands genisoimage or mkisofs are used to create the iso images. To finish, you can test the iso image with Qemu or engrave the generated iso on to a rewritable cdrom. 
+
+===== Organize a working directory =====
+
+To create SliTaz, we need a working directory and several subdirectories Whether you have a chrooted environment for developing or a host system, we advise to use a directory named //distro/// in which to work. The distro/ directory can be a simple folder or a partition, but you are obviously free to put all of this elsewhere.
+
+=== distro/ ===
+
+Contents of a working directory:
+
+    * rootfs/ --> The root filesystem - this is the root system, designed to operate in RAM, it is used to generate the initramfs image.
+    * rootfs.gz --> The initramfs image of our system - a cpio archive compressed with gzip.
+    * rootcd/ --> The rootcd. This is the root of the cdrom files.
+    * src/ --> The sources, Kernel, Syslinux, Busybox, Dropbear, etc (it can also be a symbolic link).
+
+Thereafter, the initramfs and bootable ISO image (slitaz-cooking.iso) will be created in the root directory of our work named SliTaz/.
+
+=== Option: rootfs.ext2 - using a virtual hard drive ===
+
+Option: rootfs.ext2 (root filesystem in ext2) is a virtual hard disk formatted with ext2 and mounted on a (rootfs) loop. A device loop allows a file to be used as a standard device (hard drive, floppy, etc) to build a filesystem inside. This file can be any number of megabytes, we propose 20,480, which corresponds to 20MB:
+
+ # dd if=/dev/zero of=rootfs.ext2 bs=1k count=20480 
+
+Create a //ext2// filesystem named //rootfs.ext2//, the option //-F// formats the file. Note that the //-m 0// option doesn't allocate any space for the user root - by default it occupies approximately 5% and the //-t// option defines the type of filesystem to be used, such as ext2 or ext3:
+
+ # mkfs -t ext2 -F -m 0 rootfs.ext2 
+
+We can now assemble //rootfs.ext2// with a loop, thanks to the //-o loop option// provided by the mount utility in the //rootfs/// directory. You can check if the assembly went well with the //df-h// command:
+
+
+ # mkdir rootfs
+ # mount -o loop rootfs.ext2 rootfs
+ # df -h
+
+
+At the end of the session, you can dismount the volume with umount:
+
+ # umount rootfs 
+
+Now we can proceed to the construction of the [[http://www.slitaz.org/en/doc/scratchbook/base-system.html|Base SliTaz system]]. 
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/start.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/start.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,39 @@
+====== English documentation ======
+
+
+This site provides SliTaz GNU/Linux official and community documentation.
+
+We believe that SliTaz users all over the world want to share their knowledge and experiences through writing. This is an open wiki that anybody can contribute to. We are very grateful to those who want to lend a hand to make SliTaz even easier to use. Welcome!
+
+
+===== Newsletter ======
+
+  * [[en:newsletter:start|Newsletter]] - The SliTaz Monthly Newsletter, news, tips and tricks.
+
+===== Guides ====== 
+
+  * [[en:guides:start|Guides]] - Small and concise guides from the community.
+  * [[en:references:start|References]] - Any interesting linux article/how-to/material you may want to share.
+  * [[en:devnotes:start|Development notes]] - Information about the development version (cooking).
+  * [[en:forum:start|Forum posts]] - Supplementary documentation from the user forums.
+
+==== Books ====
+
+  * [[en:handbook:start|Handbook]] - 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.
+  * [[en:cookbook:start|Cookbook]] - 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.
+  * [[en:scratchbook:start|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.
+
+
+==== Manuals ====
+
+All SliTaz related manuals are installed on each SliTaz distribution and can also be viewed online via the Mercurial web interface.
+
+  * [[http://hg.slitaz.org/tazpkg/raw-file/tip/doc/tazpkg.en.html|Tazpkg manual]] - SliTaz Package Manager.
+  * [[http://hg.slitaz.org/tazlito/raw-file/tip/doc/tazlito.en.html|Tazlito manual]] - SliTaz LiveCD utility.
+  * [[http://hg.slitaz.org/tazusb/raw-file/tip/doc/tazusb.en.html|TazUSB manual]] - SliTaz LiveUSB utility.
+  * [[http://hg.slitaz.org/tazwok/raw-file/tip/doc/tazwok.en.html|Tazwok manual]] - SliTaz Package Cooker.
+  * [[http://hg.slitaz.org/slitaz-tools/raw-file/tip/doc/burnbox.html|Burnbox manual]] - SliTaz utility to burn CD/DVDs
+
+==== SliTaz Terms & Dictionary ====
+
+[[en:terms:a]] - [[en:terms:b]] - [[en:terms:c]] - [[en:terms:d]] - [[en:terms:e]] - [[en:terms:f]] - [[en:terms:g]] - [[en:terms:h]] - [[en:terms:i]] - [[en:terms:j]] - [[en:terms:k]] - [[en:terms:l]] - [[en:terms:m]] - [[en:terms:n]] - [[en:terms:o]] - [[en:terms:p]] - [[en:terms:q]] - [[en:terms:r]] - [[en:terms:s]] - [[en:terms:t]] - [[en:terms:u]] - [[en:terms:v]] - [[en:terms:w]] - [[en:terms:x]] - [[en:terms:y]] - [[en:terms:z]]
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/terms/a.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/terms/a.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,5 @@
+===== A =====
+[[en:start|^]] [[en:terms:a]] - [[en:terms:b]] - [[en:terms:c]] - [[en:terms:d]] - [[en:terms:e]] - [[en:terms:f]] - [[en:terms:g]] - [[en:terms:h]] - [[en:terms:i]] - [[en:terms:j]] - [[en:terms:k]] - [[en:terms:l]] - [[en:terms:m]] - [[en:terms:n]] - [[en:terms:o]] - [[en:terms:p]] - [[en:terms:q]] - [[en:terms:r]] - [[en:terms:s]] - [[en:terms:t]] - [[en:terms:u]] - [[en:terms:v]] - [[en:terms:w]] - [[en:terms:x]] - [[en:terms:y]] - [[en:terms:z]]
+
+==== accessibility ====
+  * see [[en:handbook:accessibility|Assistive technology]]
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/terms/c.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/terms/c.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,9 @@
+===== C =====
+[[en:start|^]] [[en:terms:a]] - [[en:terms:b]] - [[en:terms:c]] - [[en:terms:d]] - [[en:terms:e]] - [[en:terms:f]] - [[en:terms:g]] - [[en:terms:h]] - [[en:terms:i]] - [[en:terms:j]] - [[en:terms:k]] - [[en:terms:l]] - [[en:terms:m]] - [[en:terms:n]] - [[en:terms:o]] - [[en:terms:p]] - [[en:terms:q]] - [[en:terms:r]] - [[en:terms:s]] - [[en:terms:t]] - [[en:terms:u]] - [[en:terms:v]] - [[en:terms:w]] - [[en:terms:x]] - [[en:terms:y]] - [[en:terms:z]]
+
+====chroot====
+  * see [[en:guides:chroot]], [[en:devnotes:cook-flavor-from-scratch?&#Explanation]]
+  * more: [[http://en.wikipedia.org/wiki/Chroot|wikipedia]]
+
+==== commands ====
+  * see [[en:handbook:commands|List of useful commands]]
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/terms/d.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/terms/d.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,5 @@
+===== D =====
+[[en:start|^]] [[en:terms:a]] - [[en:terms:b]] - [[en:terms:c]] - [[en:terms:d]] - [[en:terms:e]] - [[en:terms:f]] - [[en:terms:g]] - [[en:terms:h]] - [[en:terms:i]] - [[en:terms:j]] - [[en:terms:k]] - [[en:terms:l]] - [[en:terms:m]] - [[en:terms:n]] - [[en:terms:o]] - [[en:terms:p]] - [[en:terms:q]] - [[en:terms:r]] - [[en:terms:s]] - [[en:terms:t]] - [[en:terms:u]] - [[en:terms:v]] - [[en:terms:w]] - [[en:terms:x]] - [[en:terms:y]] - [[en:terms:z]]
+
+==== diff ====
+  * see [[http://www.slitaz.org/en/devel/#diff|Diff and patch]]
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/terms/f.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/terms/f.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,8 @@
+===== F =====
+[[en:start|^]] [[en:terms:a]] - [[en:terms:b]] - [[en:terms:c]] - [[en:terms:d]] - [[en:terms:e]] - [[en:terms:f]] - [[en:terms:g]] - [[en:terms:h]] - [[en:terms:i]] - [[en:terms:j]] - [[en:terms:k]] - [[en:terms:l]] - [[en:terms:m]] - [[en:terms:n]] - [[en:terms:o]] - [[en:terms:p]] - [[en:terms:q]] - [[en:terms:r]] - [[en:terms:s]] - [[en:terms:t]] - [[en:terms:u]] - [[en:terms:v]] - [[en:terms:w]] - [[en:terms:x]] - [[en:terms:y]] - [[en:terms:z]]
+
+
+==== Flavor ====
+  * new special distribution of SliTaz; cooked in the [[en:terms:W?&#wok|wok]]
+  * see [[en:cookbook:start]], [[en:devnotes:cook-flavor-from-scratch?&#explication]]
+  * de: [[de:terms:G?&#Geschmackrichtung|Geschmackrichtung, Rezept, eigene Distribution]], fr: [[fr:terms:S?&#saveur|saveur]]
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/terms/i.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/terms/i.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,5 @@
+===== i =====
+[[en:start|^]] [[en:terms:a]] - [[en:terms:b]] - [[en:terms:c]] - [[en:terms:d]] - [[en:terms:e]] - [[en:terms:f]] - [[en:terms:g]] - [[en:terms:h]] - [[en:terms:i]] - [[en:terms:j]] - [[en:terms:k]] - [[en:terms:l]] - [[en:terms:m]] - [[en:terms:n]] - [[en:terms:o]] - [[en:terms:p]] - [[en:terms:q]] - [[en:terms:r]] - [[en:terms:s]] - [[en:terms:t]] - [[en:terms:u]] - [[en:terms:v]] - [[en:terms:w]] - [[en:terms:x]] - [[en:terms:y]] - [[en:terms:z]]
+
+==== ISO file ====
+  * see [[en:tazlitomanual|SliTaz Live Tool]], numerous infos about ISO files or images in the Tazlito Handbook.
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/terms/l.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/terms/l.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,5 @@
+===== L =====
+[[en:start|^]] [[en:terms:a]] - [[en:terms:b]] - [[en:terms:c]] - [[en:terms:d]] - [[en:terms:e]] - [[en:terms:f]] - [[en:terms:g]] - [[en:terms:h]] - [[en:terms:i]] - [[en:terms:j]] - [[en:terms:k]] - [[en:terms:l]] - [[en:terms:m]] - [[en:terms:n]] - [[en:terms:o]] - [[en:terms:p]] - [[en:terms:q]] - [[en:terms:r]] - [[en:terms:s]] - [[en:terms:t]] - [[en:terms:u]] - [[en:terms:v]] - [[en:terms:w]] - [[en:terms:x]] - [[en:terms:y]] - [[en:terms:z]]
+
+==== liveCD ====
+  * see [[en:tazlitomanual|SliTaz Live Tool]], numerous infos about liveCD in the Tazlito Handbook.
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/terms/p.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/terms/p.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,7 @@
+===== P =====
+[[en:start|^]] [[en:terms:a]] - [[en:terms:b]] - [[en:terms:c]] - [[en:terms:d]] - [[en:terms:e]] - [[en:terms:f]] - [[en:terms:g]] - [[en:terms:h]] - [[en:terms:i]] - [[en:terms:j]] - [[en:terms:k]] - [[en:terms:l]] - [[en:terms:m]] - [[en:terms:n]] - [[en:terms:o]] - [[en:terms:p]] - [[en:terms:q]] - [[en:terms:r]] - [[en:terms:s]] - [[en:terms:t]] - [[en:terms:u]] - [[en:terms:v]] - [[en:terms:w]] - [[en:terms:x]] - [[en:terms:y]] - [[en:terms:z]]
+
+====Patch====
+  * see [[en:devnotes:cook-flavor-from-scratch?&#Explanation]]
+  * see [[http://www.slitaz.org/en/devel/#diff|Diff and patch]]
+  * more [[http://en.wikipedia.org/wiki/Patch_(Unix)|wikipedia]]
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/terms/q.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/terms/q.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,6 @@
+===== Q =====
+[[en:start|^]] [[en:terms:a]] - [[en:terms:b]] - [[en:terms:c]] - [[en:terms:d]] - [[en:terms:e]] - [[en:terms:f]] - [[en:terms:g]] - [[en:terms:h]] - [[en:terms:i]] - [[en:terms:j]] - [[en:terms:k]] - [[en:terms:l]] - [[en:terms:m]] - [[en:terms:n]] - [[en:terms:o]] - [[en:terms:p]] - [[en:terms:q]] - [[en:terms:r]] - [[en:terms:s]] - [[en:terms:t]] - [[en:terms:u]] - [[en:terms:v]] - [[en:terms:w]] - [[en:terms:x]] - [[en:terms:y]] - [[en:terms:z]]
+
+====Q====
+  * see 
+  * more
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/terms/r.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/terms/r.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,8 @@
+===== R =====
+[[en:start|^]] [[en:terms:a]] - [[en:terms:b]] - [[en:terms:c]] - [[en:terms:d]] - [[en:terms:e]] - [[en:terms:f]] - [[en:terms:g]] - [[en:terms:h]] - [[en:terms:i]] - [[en:terms:j]] - [[en:terms:k]] - [[en:terms:l]] - [[en:terms:m]] - [[en:terms:n]] - [[en:terms:o]] - [[en:terms:p]] - [[en:terms:q]] - [[en:terms:r]] - [[en:terms:s]] - [[en:terms:t]] - [[en:terms:u]] - [[en:terms:v]] - [[en:terms:w]] - [[en:terms:x]] - [[en:terms:y]] - [[en:terms:z]]
+
+
+==== root ====
+  * //root// has always at least two significations in linux
+  * //root// is the pseudonym of the administrator of the all system (see more under  [[en:terms:S?&#su|su]], [[en:terms:S?&#sudo|sudo]] and [[en:terms:C?&#chroot|chroot]])
+  * //root// is the name of the home directory of the administrator and is the place for important ressources for the all system; for this reason the directory /home has to be always in the same [[en:terms:P?&#partition|partition]] as the [[en:terms:M?&#main_directory|main directory /]]
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/terms/s.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/terms/s.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,11 @@
+===== S =====
+[[en:start|^]] [[en:terms:a]] - [[en:terms:b]] - [[en:terms:c]] - [[en:terms:d]] - [[en:terms:e]] - [[en:terms:f]] - [[en:terms:g]] - [[en:terms:h]] - [[en:terms:i]] - [[en:terms:j]] - [[en:terms:k]] - [[en:terms:l]] - [[en:terms:m]] - [[en:terms:n]] - [[en:terms:o]] - [[en:terms:p]] - [[en:terms:q]] - [[en:terms:r]] - [[en:terms:s]] - [[en:terms:t]] - [[en:terms:u]] - [[en:terms:v]] - [[en:terms:w]] - [[en:terms:x]] - [[en:terms:y]] - [[en:terms:z]]
+
+====Scratch ====
+  * see [[en:devnotes:cook-flavor-from-scratch?&#Explanation]]
+  * scratch is a computer freak slang to say ‘from the source code and without tools’
+
+====Source (code) ====
+  * see [[en:devnotes:cook-flavor-from-scratch?&#Explanation]] and search ‘scratch’
+  * more [[http://en.wikipedia.org/wiki/Source_code|wikipedia]]
+
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/terms/t.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/terms/t.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,5 @@
+===== T =====
+[[en:start|^]] [[en:terms:a]] - [[en:terms:b]] - [[en:terms:c]] - [[en:terms:d]] - [[en:terms:e]] - [[en:terms:f]] - [[en:terms:g]] - [[en:terms:h]] - [[en:terms:i]] - [[en:terms:j]] - [[en:terms:k]] - [[en:terms:l]] - [[en:terms:m]] - [[en:terms:n]] - [[en:terms:o]] - [[en:terms:p]] - [[en:terms:q]] - [[en:terms:r]] - [[en:terms:s]] - [[en:terms:t]] - [[en:terms:u]] - [[en:terms:v]] - [[en:terms:w]] - [[en:terms:x]] - [[en:terms:y]] - [[en:terms:z]]
+
+==== tazlito ====
+  * see [[en:tazlitomanual|SliTaz Live Tool]] in the Tazlito Handbook.
\ No newline at end of file
diff -r a779af7ea2b8 -r 70b5f3ae5339 pages/en/terms/w.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/en/terms/w.txt	Sat Feb 26 12:17:18 2011 +0000
@@ -0,0 +1,7 @@
+===== W =====
+[[en:start|^]] [[en:terms:a]] - [[en:terms:b]] - [[en:terms:c]] - [[en:terms:d]] - [[en:terms:e]] - [[en:terms:f]] - [[en:terms:g]] - [[en:terms:h]] - [[en:terms:i]] - [[en:terms:j]] - [[en:terms:k]] - [[en:terms:l]] - [[en:terms:m]] - [[en:terms:n]] - [[en:terms:o]] - [[en:terms:p]] - [[en:terms:q]] - [[en:terms:r]] - [[en:terms:s]] - [[en:terms:t]] - [[en:terms:u]] - [[en:terms:v]] - [[en:terms:w]] - [[en:terms:x]] - [[en:terms:y]] - [[en:terms:z]]
+
+
+====Wok====
+  * development environment of SliTaz; to cook [[en:terms:F?&#flavor|flavors]] and components!
+  * see [[en:cookbook:start]], [[en:devnotes:cook-flavor-from-scratch?&#explication]]