SliTaz Repositories

     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/pages/en/cookbook/advancedhg.txt	Sat Feb 26 12:17:18 2011 +0000
     1.3 @@ -0,0 +1,127 @@
     1.4 +====== Advanced usage of Mercurial ======
     1.5 +
     1.6 +==== Use an external tool to merge ====
     1.7 +
     1.8 +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:
     1.9 +
    1.10 +<code>
    1.11 +[ui]
    1.12 +merge = meld
    1.13 +</code>
    1.14 +
    1.15 +==== Useful extensions ====
    1.16 +
    1.17 +To add an extension, you can use the ~/.hgrc file:
    1.18 +<code>
    1.19 +[extensions]
    1.20 +name = adress
    1.21 +</code>
    1.22 +Some extensions are packed within Mercurial, so it's not necessary to give them addressess. It's the case of the four following:
    1.23 +
    1.24 +**color**
    1.25 +Add color in Mercurial. Useful when displaying differences between several versions of a file.
    1.26 +
    1.27 +**hgext.fetch**
    1.28 +Add the command hg fetch, which regroups hg pull && hg merge && hg update.
    1.29 +
    1.30 +**hgext.graphlog**
    1.31 +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.
    1.32 +
    1.33 +**mq**
    1.34 +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.
    1.35 +
    1.36 +
    1.37 +==== Basic functionality of MQ ====
    1.38 +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:
    1.39 +<code>hg qinit -c</code>
    1.40 +
    1.41 +Après avoir procédé à des modifications, les enregistrer en temps que patch plutôt que les commiter :
    1.42 +After modifications, save them as a patch instead of committing them:
    1.43 +<code>hg qnew nom_du_patch</code>
    1.44 +
    1.45 +List applied/unapplied patches:
    1.46 +<code>hg qseries -v</code>
    1.47 +
    1.48 +Add changes to the current patch (the last one applied):
    1.49 +<code>hg qrefresh</code>
    1.50 +
    1.51 +Apply the next patch from the queue:
    1.52 +<code>hg qpush</code>
    1.53 +
    1.54 +Apply all patches:
    1.55 +<code>hg qpush -a</code>
    1.56 +
    1.57 +Unapply current patch:
    1.58 +<code>hg qpop</code>
    1.59 +
    1.60 +Unapply all patches:
    1.61 +<code>hg qpop -a</code>
    1.62 +
    1.63 +Go to a given patch in the queue:
    1.64 +<code>hg qgoto patch</code>
    1.65 +
    1.66 +Add a message to the current patch (before committing it):
    1.67 +<code>hg qrefresh -m "Message"</code>
    1.68 +
    1.69 +Transform a patch into a commit:
    1.70 +<code>hg qfinish patch</code>
    1.71 +
    1.72 +Commit changes made in the patch repository:
    1.73 +<code>hg qcommit -m "Message de commit"</code>
    1.74 +
    1.75 +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.
    1.76 +
    1.77 +==== MQ & Merge ====
    1.78 +
    1.79 +**General idea**
    1.80 +
    1.81 +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:
    1.82 +
    1.83 +<code>
    1.84 +o New repository revision
    1.85 +|
    1.86 +|
    1.87 +| o Patches
    1.88 +| |
    1.89 +| /
    1.90 +|
    1.91 +o Repository before patch application
    1.92 +</code>
    1.93 +
    1.94 +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.
    1.95 +
    1.96 +Create the head patches:
    1.97 +<code>
    1.98 +qpush -a
    1.99 +hg tags  # Remember/Note the number of the revision qparent
   1.100 +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)
   1.101 +</code>
   1.102 +
   1.103 +Create the new head:
   1.104 +<code>
   1.105 +hg update -C <N°qparent> # Go to the revision noted before.
   1.106 +
   1.107 +# Next, do what you planned to:
   1.108 +# Update:
   1.109 +hg pull -u
   1.110 +# Commit new changes, make the modifications then:
   1.111 +hg commit -m "message"
   1.112 +# Edit a patch:
   1.113 +hg qgoto patch # Then do the modifications and:
   1.114 +hg qrefresh</code>
   1.115 +
   1.116 +To launch the merge:
   1.117 +<code>hg qpush -a -m</code>
   1.118 +
   1.119 +Clean the repository:
   1.120 +<code>
   1.121 +hg qpop -a
   1.122 +hg qpop -a -n patches.N
   1.123 +rm -r .hg/patches.N
   1.124 +</code>
   1.125 +
   1.126 +Save the changes made into the patch repository:
   1.127 +<code>hg qcommit -m "Updated to match rev???"</code>
   1.128 +
   1.129 +Re-apply the patch queue:
   1.130 +<code>hg qpush -a</code>
   1.131 \ No newline at end of file

     2.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     2.2 +++ b/pages/en/cookbook/bootscripts.txt	Sat Feb 26 12:17:18 2011 +0000
     2.3 @@ -0,0 +1,89 @@
     2.4 +====== Boot scripts ======
     2.5 +
     2.6 +The startup and shutdown scripts with their configuration files.
     2.7 +
     2.8 +    * SliTaz and startup.
     2.9 +    * /etc/init.d/* - Directory of scripts and daemons.
    2.10 +    * /etc/init.d/rcS - Primary initialization script.
    2.11 +    * Specific scripts and daemons - Scripts and daemons with a very specific task.
    2.12 +    * /etc/inittab - Configuration file init.
    2.13 +
    2.14 +===== SliTaz and startup =====
    2.15 +
    2.16 +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.
    2.17 +
    2.18 +===== /etc/init.d/* - Directory of scripts/daemons =====
    2.19 +
    2.20 +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:
    2.21 +
    2.22 +<code> # /etc/init.d/daemon [start|stop|restart] </code>
    2.23 +
    2.24 +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.
    2.25 +
    2.26 +===== /etc/init.d/rcS - Primary initialization script =====
    2.27 +
    2.28 +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:
    2.29 +
    2.30 +<code> # nano rootfs/etc/init.d/rcS </code>
    2.31 +
    2.32 +===== Specific scripts and daemons ======
    2.33 +
    2.34 +=== bootopts.sh - LiveCD mode options ===
    2.35 +
    2.36 +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.
    2.37 +
    2.38 +=== network.sh - Initializing the network ===
    2.39 +
    2.40 +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.
    2.41 +
    2.42 +=== i18n.sh - Internationalization ===
    2.43 +
    2.44 +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.
    2.45 +
    2.46 +=== local.sh - Local commands ===
    2.47 +
    2.48 +The ///etc/init.d/local.sh// script allows the system administrator to add local commands to be executed at boot. Example:
    2.49 +
    2.50 +<file>
    2.51 +#!/bin/sh
    2.52 +# /etc/init.d/local.sh: Local startup commands.
    2.53 +# All commands here will be executed at boot time.
    2.54 +#
    2.55 +. /etc/init.d/rc.functions
    2.56 +
    2.57 +echo "Starting local startup commands... "
    2.58 +</file>
    2.59 +
    2.60 +=== wpa_action.sh - Wireless network ===
    2.61 +
    2.62 +This script is applied by //network.sh// to start/restart the DHCP server if you use a dynamic IP.
    2.63 +
    2.64 +=== rc.shutdown ===
    2.65 +
    2.66 +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. 
    2.67 +
    2.68 +===== /etc/inittab - Configuration file init ======
    2.69 +
    2.70 +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]]:
    2.71 +
    2.72 +<file>
    2.73 +# /etc/inittab: init configuration for SliTaz GNU/Linux.
    2.74 +# Boot-time system configuration/initialization script.
    2.75 +#
    2.76 +::sysinit:/etc/init.d/rcS
    2.77 +
    2.78 +# /sbin/getty respawn shell invocations for selected ttys.
    2.79 +tty1::respawn:/sbin/getty 38400 tty1
    2.80 +tty2::respawn:/sbin/getty 38400 tty2
    2.81 +tty3::respawn:/sbin/getty 38400 tty3
    2.82 +tty4::respawn:/sbin/getty 38400 tty4
    2.83 +tty5::respawn:/sbin/getty 38400 tty5
    2.84 +tty6::respawn:/sbin/getty 38400 tty6
    2.85 +
    2.86 +# Stuff to do when restarting the init 
    2.87 +# process, or before rebooting.
    2.88 +::restart:/etc/init.d/rc.shutdown
    2.89 +::restart:/sbin/init
    2.90 +::ctrlaltdel:/sbin/reboot
    2.91 +::shutdown:/etc/init.d/rc.shutdown
    2.92 +</file>

     3.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     3.2 +++ b/pages/en/cookbook/buildbot.txt	Sat Feb 26 12:17:18 2011 +0000
     3.3 @@ -0,0 +1,59 @@
     3.4 +====== Build Bot (tazbb) ======
     3.5 +
     3.6 +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]]. 
     3.7 +
     3.8 +===== How it works =====
     3.9 +
    3.10 +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.
    3.11 +
    3.12 +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.
    3.13 +
    3.14 +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.
    3.15 +
    3.16 +When run with the option 'cook' - Tazbb will also remove old and corrupted packages and then execute <nowiki> 'tazwok genlist --text' </nowiki> 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//
    3.17 +
    3.18 +===== Commands =====
    3.19 +
    3.20 +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 //<nowiki>'--verbose'</nowiki>// option.
    3.21 +
    3.22 +===== Hg and chroot Wok =====
    3.23 +
    3.24 +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.
    3.25 +
    3.26 +===== Log files =====
    3.27 +
    3.28 +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//
    3.29 +
    3.30 +===== Web interface =====
    3.31 +
    3.32 +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
    3.33 +
    3.34 +===== Hg hook =====
    3.35 +
    3.36 +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:
    3.37 +
    3.38 +<file>
    3.39 +[hooks]
    3.40 +commit = tazbb cook-commit
    3.41 +</file>
    3.42 +
    3.43 +===== Cron Job =====
    3.44 +
    3.45 +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:
    3.46 +
    3.47 +<file>
    3.48 +*/2 * * * * /usr/bin/tazbb cook-commit
    3.49 +03 02 * * * /usr/bin/tazbb cook-all
    3.50 +</file>
    3.51 +
    3.52 +===== Database Files =====
    3.53 +
    3.54 +    * blocked : List of blocked packages
    3.55 +    * cooklist : Current or next cooklist
    3.56 +    * corrupted : Corrupted packages list
    3.57 +    * packaged : All packages from the build wok
    3.58 +    * removed : Last removed packages
    3.59 +    * report : Last report from check_{wok,commit}
    3.60 +    * running : Current task running
    3.61 +    * summary : Last summary for the web interface
    3.62 +    * unbuilt : List of unbuilt packages

     4.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     4.2 +++ b/pages/en/cookbook/buildhost.txt	Sat Feb 26 12:17:18 2011 +0000
     4.3 @@ -0,0 +1,89 @@
     4.4 +====== SliTaz Build Host (tank) ======
     4.5 +
     4.6 +SliTaz build host info and howto. 
     4.7 +
     4.8 +===== Folders in: /home/slitaz =====
     4.9 +
    4.10 +    * cooking/ - Cooking chroot and flavors.
    4.11 +    * stable/ - Stable tree.
    4.12 +    * repos/ - All the project repos (where the commits are pushed).
    4.13 +    * www/ - Virtual hosts (website, hg, boot, people, etc).
    4.14 +
    4.15 +===== Using tazdev =====
    4.16 +
    4.17 +To help maintain the mirror, flavors and other services, the tazdev command is used. It is mostly configured for the cooking version. Usage:
    4.18 +
    4.19 +<code>
    4.20 + $ tazdev usage
    4.21 +</code>
    4.22 +
    4.23 +===== Cooking undigest packages =====
    4.24 +
    4.25 +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.
    4.26 +
    4.27 +To build packages in the undigest wok and in the chroot environment: commands are sometimes better than a long text:
    4.28 +
    4.29 +<code>
    4.30 + $ ln -s /home/slitaz/cooking/chroot/home/undigest .
    4.31 +</code>
    4.32 +
    4.33 +You can copy files with gFTP-sftp-scp directly into the wok or from the current directory:
    4.34 +
    4.35 +<code>
    4.36 + $ cp -a package undigest/wok
    4.37 + $ su -c "tazdev chroot"
    4.38 + /# cd home/undigest
    4.39 + /# tazwok cook package
    4.40 + /# exit
    4.41 + $ ls undigest/packages
    4.42 +</code>
    4.43 +
    4.44 +===== Cooking official packages =====
    4.45 +
    4.46 +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).
    4.47 +
    4.48 +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:
    4.49 +
    4.50 +<code>
    4.51 + # tazdev chroot
    4.52 +</code>
    4.53 +
    4.54 +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:
    4.55 +
    4.56 +<code>
    4.57 + /# tazbb cook-commit
    4.58 +</code>
    4.59 +
    4.60 +If needed (tazbb does this automatically), you can remove all the old packages and then rebuild the lists manually:
    4.61 +
    4.62 +<code>
    4.63 + /# tazbb clean-up
    4.64 + /# tazwok gen-list --text
    4.65 + /# exit
    4.66 +</code>
    4.67 +
    4.68 +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.
    4.69 +
    4.70 +===== Stable packages =====
    4.71 +
    4.72 +Packages for the stable release are also built in a chroot environment like the Cooking packages:
    4.73 +
    4.74 +<code>
    4.75 + # tazdev chroot stable
    4.76 +</code>
    4.77 +
    4.78 +===== Upload by hand on mirror.slitaz.org =====
    4.79 +
    4.80 +Mirror maintainers can upload by hand with tazdev (-dp for a dry push):
    4.81 +
    4.82 +<code>
    4.83 + # tazdev -p $USER
    4.84 +</code>
    4.85 +
    4.86 +===== Update website by hand ======
    4.87 +
    4.88 +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):
    4.89 +
    4.90 +<code>
    4.91 + # tazdev update-www
    4.92 +</code>
    4.93 \ No newline at end of file

     5.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     5.2 +++ b/pages/en/cookbook/devcorner.txt	Sat Feb 26 12:17:18 2011 +0000
     5.3 @@ -0,0 +1,182 @@
     5.4 +====== Developer's Corner ======
     5.5 +
     5.6 +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. 
     5.7 +
     5.8 +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]]. 
     5.9 +
    5.10 +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.
    5.11 +
    5.12 +\\
    5.13 +
    5.14 +===== KISS & Comply to Standards =====
    5.15 +
    5.16 +  * First and foremost: keep it simple!
    5.17 +  * Follow the most reliable standards in coding, documenting and all other areas of development.
    5.18 +  * Carefully draft and write high quality documentation, including summarising complicated sections or processes, as well as detailed and informative tutorials.
    5.19 +  * 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.
    5.20 +  * 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.
    5.21 +  * The idea is to think small and not to duplicate.
    5.22 +
    5.23 +\\
    5.24 +
    5.25 +===== Tank - Build Host & Home =====
    5.26 +
    5.27 +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.  
    5.28 +
    5.29 +[[en:cookbook:buildhost|Instructions]] on using the build host are described in the Cookbook.
    5.30 +
    5.31 +\\
    5.32 +
    5.33 +===== SliTaz Packages =====
    5.34 +
    5.35 +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!
    5.36 +
    5.37 +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]]. 
    5.38 +
    5.39 +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. 
    5.40 +
    5.41 +\\
    5.42 +
    5.43 +===== Naming of Packages =====
    5.44 +
    5.45 +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//.
    5.46 +
    5.47 +\\
    5.48 +
    5.49 +===== Mercurial Repositories =====
    5.50 +
    5.51 +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:
    5.52 +
    5.53 +<code>
    5.54 + # tazpkg get-install mercurial
    5.55 +</code> 
    5.56 +
    5.57 +\\
    5.58 +
    5.59 +=== ~/.hgrc ===
    5.60 +
    5.61 +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: 
    5.62 +
    5.63 +<file>
    5.64 +[ui]
    5.65 +username = FirstName LastName <you@example.org>
    5.66 +</file>
    5.67 +
    5.68 +\\
    5.69 +
    5.70 +=== Clone, Modify, Commit, Push ===
    5.71 +
    5.72 +<note important>You must be in the repository to be able to use 'hg' commands.</note>
    5.73 +
    5.74 +  * Clone a repo, example for wok: 
    5.75 +
    5.76 +   $ hg clone http://repos.slitaz.org/wok
    5.77 +
    5.78 +  * Check all logs, or just the last log:  
    5.79 +
    5.80 +   $ hg log
    5.81 +   $ hg head
    5.82 +
    5.83 +  * Add or modify one or more files and commit:
    5.84 +
    5.85 +   $ hg add
    5.86 +   $ hg status
    5.87 +   $ hg commit -m "Log message..."
    5.88 +   $ hg log
    5.89 +
    5.90 +<note tip>You can use the command //rollback// to roll back to the last transaction.</note>
    5.91 +
    5.92 +  * Before pushing changes to the server, it is safe to pull once:
    5.93 +
    5.94 +   $ hg pull
    5.95 +   $ hg push
    5.96 +
    5.97 +Done! Your changes, code or corrections are now on the server. 
    5.98 +
    5.99 +\\
   5.100 +
   5.101 +=== Updating a Local Wok ===
   5.102 +
   5.103 +To update your working directory with the changes that others have since committed to the server (//pull// the changes):
   5.104 +
   5.105 +   $ hg pull
   5.106 +   $ hg update
   5.107 +
   5.108 +\\
   5.109 +
   5.110 +=== Useful Commands ===
   5.111 +
   5.112 +There are a number of commands that you may find useful:
   5.113 +  * **hg help** -- Display the full list of commands.
   5.114 +  * **hg rollback** -- Undo the last action performed (commit, pull, push).
   5.115 +  * **hg log //<package>//** -- Display a package log.
   5.116 +  * **hg head** -- Display the last log.
   5.117 +
   5.118 +\\
   5.119 +
   5.120 +===== Implementation of iconv() =====
   5.121 +
   5.122 +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. 
   5.123 +
   5.124 +\\
   5.125 +
   5.126 +===== Website Management and Books =====
   5.127 +
   5.128 +The website and books (Handbook and Cookbook) are managed via a Mercurial repository, they can be cloned by: 
   5.129 +
   5.130 +   $ hg clone http://hg.slitaz.org/website
   5.131 +
   5.132 +Or if you have the proper permissions:
   5.133 +
   5.134 +   $ hg clone http://repos.slitaz.org/website
   5.135 +
   5.136 +\\
   5.137 +
   5.138 +===== xHTML Coding Style =====
   5.139 +
   5.140 +The website must have a consistent look-and-feel; this is also used in the wiki pages and local documentation. To achieve this:
   5.141 +
   5.142 +  * The pages and books are written in xHTML 1.0 Transitional.
   5.143 +
   5.144 +  * The colours for the body and the titles are placed directly on the page so the links are easy to follow.
   5.145 +    *  The title, a Level 1 heading, is used only once (at the top);
   5.146 +    *  Level 2 is the title of the document;
   5.147 +    *  Levels 3 and 4 are then used for the subtitles.
   5.148 +
   5.149 +  * If a list is used instead with smart anchors, it starts at the top just after the title of level 2.
   5.150 +
   5.151 +  * Paragraphs are always contained in <p> tags.
   5.152 +
   5.153 +  * For indentation, we use tabs. The reasons being semantics and to take up less space in terms of octets (bytes).
   5.154 +
   5.155 +  * To put code, like the name of a command inside a paragraph, <code> tags is the preferred method.
   5.156 +
   5.157 +  * Commands and terminal output are displayed with <pre> tags -- example:
   5.158 +
   5.159 +   $ command
   5.160 +
   5.161 +  * To view text that can be copied and pasted, such as scripts, bits of code, sample configuration files etc., use <pre> tags but with a CSS class named "script". Example: 
   5.162 +
   5.163 +<file>
   5.164 +<pre class="script">
   5.165 +code...
   5.166 +</pre>
   5.167 +</file>
   5.168 +
   5.169 +  * To emphasize words, use <em> tags.
   5.170 +
   5.171 +  * Internal links are relative.
   5.172 +
   5.173 +  * Remember to check the validity of the code with the online validator of the W3C.
   5.174 +
   5.175 +\\
   5.176 +
   5.177 +===== The diff and patch Commands =====
   5.178 +
   5.179 +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: 
   5.180 +
   5.181 +   $ diff -u file.orig file.new > file.diff
   5.182 +
   5.183 +To apply a patch:
   5.184 +
   5.185 +   $ patch file.orig file.diff
   5.186 \ No newline at end of file

     6.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     6.2 +++ b/pages/en/cookbook/receipt.txt	Sat Feb 26 12:17:18 2011 +0000
     6.3 @@ -0,0 +1,158 @@
     6.4 +======= Recipes ======
     6.5 +
     6.6 +
     6.7 +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:
     6.8 +
     6.9 +<file># SliTaz package receipt </file>
    6.10 +
    6.11 +===== Variables =====
    6.12 +
    6.13 +
    6.14 +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:
    6.15 +<file>
    6.16 +PACKAGE="clex"
    6.17 +VERSION="3.16"
    6.18 +CATEGORY="base-apps"
    6.19 +SHORT_DESC="Text mode file manager."
    6.20 +MAINTAINER="pankso@slitaz.org"
    6.21 +</file>
    6.22 +
    6.23 +===== Variables (optional) =====
    6.24 +
    6.25 +
    6.26 +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.
    6.27 +
    6.28 +  * **$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:
    6.29 +
    6.30 +<file>DEPENDS="ncurses"</file>
    6.31 +
    6.32 +  * **$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:
    6.33 +
    6.34 +<file>BUILD_DEPENDS="ncurses-dev"</file>
    6.35 +
    6.36 +  * **$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):
    6.37 +
    6.38 +<file>TARBALL="$PACKAGE-$VERSION.tar.gz"</file>
    6.39 +
    6.40 +  * **$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: 
    6.41 +
    6.42 +<file>WEB_SITE="http://www.clex.sk/"</file>
    6.43 +
    6.44 +  * **$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:
    6.45 +
    6.46 +<file>WGET_URL="http://www.clex.sk/download/$TARBALL"</file>
    6.47 +
    6.48 +  * **$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:
    6.49 +
    6.50 + <file>CONFIG_FILES="/etc/netatalk/AppleVolumes.* /etc/netatalk/*.conf"</file>
    6.51 +
    6.52 +  * **$SUGGESTED :** Lists useful packages without being essential. Also used to activate optional features.
    6.53 +
    6.54 +  * **$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.
    6.55 +
    6.56 +  * **$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.
    6.57 +
    6.58 +  * **$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. \\
    6.59 +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.
    6.60 +
    6.61 +  * **$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. 
    6.62 +
    6.63 +===== Variables generated by Tazwok =====
    6.64 +
    6.65 +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.
    6.66 +
    6.67 +  * **$PACKED_SIZE :** Tazpkg file size.
    6.68 +
    6.69 +  * **$UNPACKED_SIZE :** Space taken up by the package after installation.
    6.70 +
    6.71 +  * **$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**.
    6.72 +
    6.73 +===== Variables used in functions =====
    6.74 +
    6.75 +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.
    6.76 +
    6.77 +  * **$src :** Defines the path to the directory of unarchived sources.
    6.78 +
    6.79 +  * **$_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.
    6.80 +
    6.81 +  * **$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.
    6.82 +
    6.83 +  * **$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. 
    6.84 +
    6.85 +===== Functions =====
    6.86 +
    6.87 +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.
    6.88 +
    6.89 +=== compile_rules() ===
    6.90 +
    6.91 +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:
    6.92 +
    6.93 +<file>
    6.94 +# Rules to configure and make the package.
    6.95 +compile_rules()
    6.96 +{
    6.97 +	cd $src
    6.98 +	./configure --prefix=/usr --infodir=/usr/share/info \
    6.99 +	--mandir=/usr/share/man $CONFIGURE_ARGS
   6.100 +	make
   6.101 +	make DESTDIR=$PWD/_pkg install
   6.102 +}
   6.103 +</file>
   6.104 +
   6.105 +=== genpkg_rules()===
   6.106 +
   6.107 +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:
   6.108 +
   6.109 +<file>
   6.110 +# Rules to gen a SliTaz package suitable for Tazpkg.
   6.111 +genpkg_rules()
   6.112 +{
   6.113 +	mkdir -p $fs/usr
   6.114 +	cp -a $_pkg/usr/bin $fs/usr
   6.115 +	strip -s $fs/usr/bin/*
   6.116 +}
   6.117 +</file>
   6.118 +
   6.119 +=== pre_install() and post_install()===
   6.120 +
   6.121 +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):
   6.122 +
   6.123 +<file>
   6.124 +# Pre and post install commands for Tazpkg.
   6.125 +pre_install()
   6.126 +{
   6.127 +	echo "Processing pre-install commands..."
   6.128 +}
   6.129 +post_install()
   6.130 +{
   6.131 +	echo "Processing post-install commands..."
   6.132 +}
   6.133 +</file>
   6.134 +
   6.135 +=== pre_remove() and post_remove() ===
   6.136 +
   6.137 +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):
   6.138 +
   6.139 +<file>
   6.140 +# Pre and post remove commands for Tazpkg.
   6.141 +pre_remove()
   6.142 +{
   6.143 +	echo "Processing pre-remove commands..."
   6.144 +}
   6.145 +post_remove()
   6.146 +{
   6.147 +	echo "Processing post-remove commands..."
   6.148 +}
   6.149 +</file>
   6.150 +
   6.151 +=== clean_wok() ===
   6.152 +
   6.153 +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:
   6.154 +
   6.155 +<file>
   6.156 +# clean commands for Tazwok.
   6.157 +clean_wok()
   6.158 +{
   6.159 +	rm -rf $WOK/$PACKAGE/vim71
   6.160 +}
   6.161 +</file>

     7.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     7.2 +++ b/pages/en/cookbook/releasetasks.txt	Sat Feb 26 12:17:18 2011 +0000
     7.3 @@ -0,0 +1,18 @@
     7.4 +====== Release tasks ======
     7.5 +
     7.6 +Things to do before publishing a new version.
     7.7 +
     7.8 +===== Check list =====
     7.9 +
    7.10 +    * 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.
    7.11 +    * Check that the SliTaz version specified in ///etc/issue// message is the same as displayed in isolinux.msg.
    7.12 +    * 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.
    7.13 +    * Test, test, and test ...
    7.14 +    * 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.
    7.15 +
    7.16 +===== Stable documentation =====
    7.17 +
    7.18 +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.
    7.19 +
    7.20 +    * [[http://hg.slitaz.org/slitaz-doc/ | SliTaz Doc repo]]
    7.21 +    * [[http://labs.slitaz.org/wiki/slitaz-doc | SliTaz Doc on the Labs]]

     8.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     8.2 +++ b/pages/en/cookbook/rootcd.txt	Sat Feb 26 12:17:18 2011 +0000
     8.3 @@ -0,0 +1,115 @@
     8.4 +====== Rootcd ======
     8.5 +
     8.6 +Descriptions of files contained on the cdrom. 
     8.7 +
     8.8 +===== Syslinux/isolinux =====
     8.9 +
    8.10 +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]].
    8.11 +
    8.12 +<file>
    8.13 +display isolinux.msg
    8.14 +default slitaz
    8.15 +label slitaz
    8.16 +	kernel /boot/bzImage
    8.17 +	append initrd=/boot/rootfs.gz rw root=/dev/null vga=788
    8.18 +implicit 0	
    8.19 +prompt 1	
    8.20 +timeout 80
    8.21 +F1 help.txt
    8.22 +F2 options.txt
    8.23 +F3 isolinux.msg
    8.24 +F4 display.txt
    8.25 +</file>
    8.26 +
    8.27 +===== Isolinux boot splash image =====
    8.28 +
    8.29 +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.
    8.30 +
    8.31 +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:
    8.32 +
    8.33 +<code> # echo -e "\24isplash.lss\n" > isolinux.msg </code>
    8.34 +
    8.35 +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.
    8.36 +
    8.37 +===== ISO bootable with isolinux =====
    8.38 +
    8.39 +To create a bootable ISO image using isolinux and genisoimage:
    8.40 +
    8.41 +<code>
    8.42 + # genisoimage -R -o slitaz-test.iso -b boot/isolinux/isolinux.bin \
    8.43 +   	-c boot/isolinux/boot.cat -no-emul-boot -boot-load-size 4 \
    8.44 +   	-V "SliTaz" -input-charset iso8859-1 -boot-info-table rootcd 
    8.45 +
    8.46 +</code>
    8.47 +
    8.48 +===== GRUB =====
    8.49 +
    8.50 +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:
    8.51 +
    8.52 +<code>
    8.53 + # mkdir -p rootcd/boot/grub
    8.54 + # cp /usr/lib/grub/i386-pc/stage2_eltorito \
    8.55 +   	rootcd/boot/grub
    8.56 +</code>
    8.57 +
    8.58 +The GRUB configuration file is called //menu.lst// and can be edited with your favorite text editor. Example:
    8.59 +
    8.60 +<file>
    8.61 +# By default, boot the first entry.
    8.62 +default 0
    8.63 +
    8.64 +# Boot automatically after 20 secs.
    8.65 +timeout 20
    8.66 +
    8.67 +# Change the colors.
    8.68 +color yellow/brown white/black
    8.69 +
    8.70 +title  SliTaz GNU/Linux 1.0 (vga 800x600) (Kernel 2.6.20)
    8.71 +       kernel /boot/bzImage root=/dev/null vga=788
    8.72 +       initrd /boot/rootfs.gz
    8.73 +
    8.74 +title  SliTaz GNU/Linux 1.0 (vga 1024x768) (Kernel 2.6.20)
    8.75 +       kernel /boot/bzImage root=/dev/null vga=771
    8.76 +       initrd /boot/rootfs.gz
    8.77 +</file>
    8.78 +
    8.79 +===== ISO bootable with GRUB =====
    8.80 +
    8.81 +To create a bootable ISO image using GRUB and genisoimage or mkisofs:
    8.82 +
    8.83 +<code>
    8.84 + # genisoimage -R -o slitaz-test.iso -b boot/grub/stage2_eltorito \
    8.85 +   	-no-emul-boot -V "SliTaz" -boot-load-size 4 -input-charset iso8859-1 \
    8.86 +   	-boot-info-table rootcd
    8.87 +</code>
    8.88 +
    8.89 +===== Memtest86 =====
    8.90 +
    8.91 +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:
    8.92 +
    8.93 +<code>
    8.94 + # mkdir -v -p src
    8.95 + # cd src
    8.96 + # wget http://www.memtest86.com/memtest86-3.2.tar.gz
    8.97 + # tar xzfv memtest86-3.2.tar.gz
    8.98 + # cd memtest86-3.2
    8.99 + (# more README)
   8.100 + # cp precomp.bin ../../rootcd/boot/memtest
   8.101 + # cd ../..
   8.102 +</code>
   8.103 +
   8.104 +Once installed, you can add the label for the memtest86 file to isolinux.cfg, specifing the path to the utility:
   8.105 +
   8.106 +<file>
   8.107 +label memtest
   8.108 +	kernel /boot/memtest
   8.109 +</file>
   8.110 +
   8.111 +Or if you want to use GRUB, here's the line to launch memtest86:
   8.112 +
   8.113 +<file>
   8.114 +title 	Memtest86 (Test system memory)
   8.115 +kernel 	/boot/memtest
   8.116 +</file>
   8.117 +
   8.118 +Once the lines are added, you can then create a new ISO and test. 
   8.119 \ No newline at end of file

     9.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     9.2 +++ b/pages/en/cookbook/slitaztools.txt	Sat Feb 26 12:17:18 2011 +0000
     9.3 @@ -0,0 +1,19 @@
     9.4 +====== SliTaz Tools ======
     9.5 +
     9.6 +The SliTaz Toolbox
     9.7 +
     9.8 +    * Mercurial repository.
     9.9 +    * <nowiki>*box </nowiki> - dialog/GTKdialog.
    9.10 +    * Archives source: [[http://download.tuxfamily.org/slitaz/sources/tools/|HTTP]].
    9.11 +
    9.12 +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.
    9.13 +
    9.14 +===== Mercurial repository =====
    9.15 +
    9.16 +The SliTaz Tools have their own Mercurial repository on the SliTaz server, they can be cloned via the command:
    9.17 +
    9.18 +<code> $ hg clone http://hg.slitaz.org/slitaz-tools/ </code>
    9.19 +
    9.20 +===== *box =====
    9.21 +
    9.22 +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. 
    9.23 \ No newline at end of file

    10.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    10.2 +++ b/pages/en/cookbook/start.txt	Sat Feb 26 12:17:18 2011 +0000
    10.3 @@ -0,0 +1,32 @@
    10.4 +====== Cookbook ======
    10.5 +
    10.6 +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.
    10.7 +
    10.8 +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. 
    10.9 +
   10.10 +==== Table of contents ====
   10.11 +
   10.12 +    * [[en:cookbook:devcorner|Developer's Corner]]  - ReadMe page for Developers.
   10.13 +    * [[en:cookbook:receipt|Receipts]]  - Receipts (recipes) for creating (cooking) SliTaz packages.
   10.14 +    * [[en:cookbook:wok|Wok]]  - Creating SliTaz packages from source using Tazwok. (Uses a receipt.)
   10.15 +    * [[en:cookbook:buildbot|Build Bot]] - Automated cooking, testing and reporting of Wok packages.
   10.16 +    * [[en:cookbook:buildhost|Build Host]]  - The SliTaz host.
   10.17 +    * [[en:cookbook:slitaztools|SliTaz Tools]]  - The Toolbox.
   10.18 +    * [[en:cookbook:advancedhg|Advanced usage of Mercurial]] - Add extensions to Mercurial and use MQ.
   10.19 +    * [[en:cookbook:releasetasks|Release Tasks]]  - List of things to do before publishing a new version.
   10.20 +    * [[en:cookbook:bootscripts|Boot Scripts]]  - The start-up and shut-down scripts.
   10.21 +    * [[en:cookbook:rootcd|Root cdrom (rootcd)]]  - Descriptions of files contained on the cdrom.
   10.22 +
   10.23 +---- 
   10.24 +\\
   10.25 +^  Page Review Section  ^^ 
   10.26 +|Quality| Medium  |
   10.27 +|Review| Minor Updates FIXME |
   10.28 +|Priority| Medium |
   10.29 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
   10.30 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
   10.31 +|How to Improve| Make all pages in cookbook current as of 3.0|
   10.32 +|::: |  |
   10.33 +
   10.34 +\\
   10.35 +----
   10.36 \ No newline at end of file

    11.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    11.2 +++ b/pages/en/cookbook/wok.txt	Sat Feb 26 12:17:18 2011 +0000
    11.3 @@ -0,0 +1,145 @@
    11.4 +====== Wok & Tools ======
    11.5 +
    11.6 +===== Overview =====
    11.7 +
    11.8 +[[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.
    11.9 +
   11.10 +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.
   11.11 +
   11.12 +<note tip>Developers and future contributors can refer to the [[http://doc.slitaz.org/en:cookbook:devcorner|development]] page that provides information on SliTaz project management.</note>
   11.13 +
   11.14 +=== Wok Structure and Organisation ===
   11.15 +
   11.16 +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.
   11.17 +
   11.18 +There is more than one Wok on the [[http://hg.slitaz.org|Mercurial repositories]]:
   11.19 +
   11.20 +  *  **wok-undigest**: //contributions awaiting testing/bug-fixing for inclusion in the unstable Wok//
   11.21 +  *  **wok**: //packages for the unstable, Cooking release//
   11.22 +  *  **wok-stable**: //packages for the stable SliTaz release//
   11.23 +
   11.24 +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.
   11.25 +
   11.26 +
   11.27 +===== Preparation =====
   11.28 +
   11.29 +The [[en:cookbook:devcorner#mercurial-repositories|Developer's Corner]] provides invaluable background information. Please ensure you have read and understood it before continuing.
   11.30 +
   11.31 +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//:
   11.32 +
   11.33 +<code>
   11.34 + # tazpkg recharge
   11.35 + # tazpkg get-install slitaz-toolchain
   11.36 +</code>
   11.37 +
   11.38 +To access the SliTaz repositories, you will need to install the //mercurial// package:
   11.39 +
   11.40 +<code>
   11.41 + # tazpkg get-install mercurial
   11.42 +</code>
   11.43 +
   11.44 +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]]".
   11.45 +
   11.46 +=== Cloning the Wok ===
   11.47 +
   11.48 +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.
   11.49 +
   11.50 +The usual destination for a Wok clone is ///home/slitaz/wok//:
   11.51 +
   11.52 +<code>
   11.53 + $ hg clone http://hg.slitaz.org/wok/ /home/slitaz/wok 
   11.54 +</code>
   11.55 +
   11.56 +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.
   11.57 +
   11.58 +<note important>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.</note>
   11.59 +
   11.60 +=== Creating a Personal Wok ===
   11.61 +
   11.62 +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. 
   11.63 +
   11.64 +<code> # tazwok gen-clean-wok </code>
   11.65 +
   11.66 +
   11.67 +===== Compiling and Generating Packages =====
   11.68 +
   11.69 +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:
   11.70 +
   11.71 +<code> # tazwok stats </code>
   11.72 +
   11.73 +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]].
   11.74 +
   11.75 +<note>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.</note>
   11.76 +
   11.77 +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//:
   11.78 +
   11.79 +<code> # tazwok cook m4 </code>
   11.80 +
   11.81 +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!
   11.82 +
   11.83 +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:
   11.84 +
   11.85 +<code> # tazwok new-tree <packageName> --interactive </code>
   11.86 +
   11.87 +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!
   11.88 +
   11.89 +
   11.90 +=== Cooking Multiple Packages with cook-list ===
   11.91 +
   11.92 +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:
   11.93 +
   11.94 +<code> # tazwok cook-list mypkgs.cooklist </code>
   11.95 +
   11.96 +<note tip>There are example lists in ///usr/share/examples/tazwok/cooklists//.</note>
   11.97 +
   11.98 +
   11.99 +===== Package Compilation Options =====
  11.100 +
  11.101 +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).
  11.102 +
  11.103 +
  11.104 +=== Package-Specific ===
  11.105 +
  11.106 +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//. 
  11.107 +
  11.108 +
  11.109 +=== Optimization ===
  11.110 +
  11.111 +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:
  11.112 +
  11.113 +<file>
  11.114 +CONFIGURE_ARGS="--build=i486-pc-linux-gnu --host=i486-pc-linux-gnu"
  11.115 +</file>
  11.116 +
  11.117 +
  11.118 +==== Files to Include/Exclude ====
  11.119 +
  11.120 +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.
  11.121 +
  11.122 +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.
  11.123 +
  11.124 +
  11.125 +===== Package Categories =====
  11.126 +
  11.127 +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'
  11.128 +
  11.129 +
  11.130 +===== Structure of a Wok Package =====
  11.131 +
  11.132 +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):
  11.133 +
  11.134 +    * **stuff/** : The material used to configure, compile and generate the package (patch(es), Makefile, pseudo fs, etc);
  11.135 +    * **receipt**: The ever-present [[en:cookbook:receipt|receipt]];
  11.136 +    * //**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//.//
  11.137 +    * //**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.//
  11.138 +
  11.139 +Tazwok will automatically call upon Tazpkg to package the //taz// directory. It also forwards any packaging instructions found in the receipt.
  11.140 +
  11.141 +===== Structure of a Tazpkg =====
  11.142 +
  11.143 +The SliTaz packages are cpio archives containing files and a file-system compressed with gzip:
  11.144 +
  11.145 +    * **fs/**: //Pseudo-file-system containing all the files to install.//
  11.146 +    * **receipt**: //The [[en:cookbook:receipt|receipt]].//
  11.147 +    * **files.list**: //A list of files in the package.//
  11.148 +    * //**description.txt**: The description of the package (optional).//

    12.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    12.2 +++ b/pages/en/devnotes/ash-benchmarks.txt	Sat Feb 26 12:17:18 2011 +0000
    12.3 @@ -0,0 +1,174 @@
    12.4 +Some tips to speed-up scripts... Add yours, and put the better ones on the top of page :)
    12.5 +
    12.6 +==== Sed substitution vs Variable substitution ====
    12.7 +
    12.8 +**Information**
    12.9 +
   12.10 +In some case, both tools can do the same job. As a build-in ash/bash command, variable substitution is a faster.
   12.11 +Note: this is always true - you can compare each type of variable substitution with an equivalent using an external tool.
   12.12 +
   12.13 +**Benchmark**
   12.14 +<code>
   12.15 +$ echo '#!/bin/sh
   12.16 +for i in $(seq 1 1000); do
   12.17 +	echo "slitaz" | sed 's/slitaz/SliTaz/'
   12.18 +done' > /tmp/slow
   12.19 +$ echo '#!/bin/sh
   12.20 +for i in $(seq 1 1000); do
   12.21 +	A=slitaz
   12.22 +	echo "${A/slitaz/SliTaz}"
   12.23 +done' > /tmp/speed
   12.24 +$ chmod +x /tmp/slow /tmp/speed
   12.25 +$ time /tmp/slow
   12.26 +> real	0m 12.40s
   12.27 +$ time /tmp/speed
   12.28 +> real	0m 0.04s
   12.29 +</code>
   12.30 +
   12.31 +==== Group command vs. Sub-process ====
   12.32 +
   12.33 +**Information**
   12.34 +
   12.35 +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
   12.36 +
   12.37 +//Note:// group command need a newline before closing - or "; }".
   12.38 +
   12.39 +**Benchmark**
   12.40 +<code>
   12.41 +$ echo '#!/bin/sh
   12.42 +for i in $(seq 1 10000); do
   12.43 +	( echo yo )
   12.44 +done' > /tmp/slow
   12.45 +$ echo '#!/bin/sh
   12.46 +for i in $(seq 1 10000); do
   12.47 +	{ echo yo; }
   12.48 +done' > /tmp/speed
   12.49 +$ chmod +x /tmp/slow /tmp/speed
   12.50 +$ time /tmp/slow
   12.51 +> real	0m 5.36s
   12.52 +$ time /tmp/speed
   12.53 +> real	0m 0.23s
   12.54 +</code>
   12.55 +
   12.56 +==== Grep vs Fgrep ====
   12.57 +
   12.58 +**Information**
   12.59 +
   12.60 +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.
   12.61 +
   12.62 +**Benchmark**
   12.63 +<code>
   12.64 +$ echo -e "line1\nline2\nline3" > /tmp/file
   12.65 +$ echo '#!/bin/sh
   12.66 +for i in $(seq 1 1000); do
   12.67 +	grep 3 /tmp/file
   12.68 +done' > /tmp/slow
   12.69 +$ echo '#!/bin/sh
   12.70 +for i in $(seq 1 1000); do
   12.71 +	fgrep 3 /tmp/file
   12.72 +done' > /tmp/speed
   12.73 +$ chmod +x /tmp/slow /tmp/speed
   12.74 +$ time /tmp/slow
   12.75 +> real	0m 11.87s
   12.76 +$ time /tmp/speed
   12.77 +> real	0m 3.21s
   12.78 +</code>
   12.79 +
   12.80 +==== [ -n "text" ] vs [ "text" ] ====
   12.81 +
   12.82 +**Information**
   12.83 +
   12.84 +The two commands test if "text" exists. Using -n slow the process a little and weight the script a little too.
   12.85 +
   12.86 +**Benchmark**
   12.87 +<code>
   12.88 +$ echo '#!/bin/sh
   12.89 +for i in $(seq 1 1000000); do
   12.90 +	[  -n "$i" ]
   12.91 +done' > /tmp/slow
   12.92 +$ echo '#!/bin/sh
   12.93 +for i in $(seq 1 1000000); do
   12.94 +	[ "$i" ]
   12.95 +done' > /tmp/speed
   12.96 +$ chmod +x /tmp/slow /tmp/speed
   12.97 +$ time /tmp/slow
   12.98 +> real	0m 15.56s
   12.99 +$ time /tmp/speed
  12.100 +> real	0m 14.11s
  12.101 +</code>
  12.102 +
  12.103 +==== [ -z "text" ] vs [ ! "text" ] vs ! [ "text" ] ====
  12.104 +
  12.105 +**Information**
  12.106 +
  12.107 +Theses three commands test if text doesn't exist. [ ! "text" ] and [ -z "text" ] have a similar processing time, while ! [ "text" ] is speeder.
  12.108 +
  12.109 +**Benchmark**
  12.110 +<code>
  12.111 +$ echo '#!/bin/sh
  12.112 +for i in $(seq 1 1000000); do
  12.113 +	[  -n "$i" ]
  12.114 +done' > /tmp/slow1
  12.115 +$ echo '#!/bin/sh
  12.116 +for i in $(seq 1 1000000); do
  12.117 +	[  -n "$i" ]
  12.118 +done' > /tmp/slow2
  12.119 +$ echo '#!/bin/sh
  12.120 +for i in $(seq 1 1000000); do
  12.121 +	[ "$i" ]
  12.122 +done' > /tmp/speed
  12.123 +$ chmod +x /tmp/slow1 /tmp/slow2 /tmp/speed
  12.124 +$ time /tmp/slow1
  12.125 +> real	0m 15.53s
  12.126 +$ time /tmp/slow2
  12.127 +> real	0m 15.60s
  12.128 +$ time /tmp/speed
  12.129 +> real	0m 14.27s
  12.130 +</code>
  12.131 +
  12.132 +==== Awk vs Cut ====
  12.133 +
  12.134 +**Information**
  12.135 +
  12.136 +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.
  12.137 + 
  12.138 +**Benchmark**
  12.139 +<code>
  12.140 +$ echo -e "field1\tfield2\tfield3" > /tmp/file
  12.141 +$ echo '#!/bin/sh
  12.142 +for i in $(seq 1 5000); do
  12.143 +	awk '"'"'{ print $2 }'"'"' /tmp/file
  12.144 +done' > /tmp/slow
  12.145 +$ echo '#!/bin/sh
  12.146 +for i in $(seq 5000); do
  12.147 +	cut -f2 /tmp/file
  12.148 +done' > /tmp/speed
  12.149 +$ chmod +x /tmp/slow /tmp/speed
  12.150 +$ time /tmp/slow
  12.151 +> real	0m 16.61s
  12.152 +$ time /tmp/speed
  12.153 +> real	0m 15.90s
  12.154 +</code>
  12.155 +
  12.156 +==== [ condition1 -a condition2 ] vs [ condition1 ] && [ condition2 ] ====
  12.157 +
  12.158 +**Information**
  12.159 +
  12.160 +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.
  12.161 +
  12.162 +**Benchmark**
  12.163 +<code>
  12.164 +$ echo '#!/bin/sh
  12.165 +for i in $(seq 1 1000000); do
  12.166 +	[ "$i" ] && [ "$i" ]
  12.167 +done' > /tmp/slow
  12.168 +$ echo '#!/bin/sh
  12.169 +for i in $(seq 1 1000000); do
  12.170 +	[  "$i"  -a "$i" ]
  12.171 +done' > /tmp/speed
  12.172 +$ chmod +x /tmp/slow /tmp/speed
  12.173 +$ time /tmp/slow
  12.174 +> real	0m 23.94s
  12.175 +$ time /tmp/speed
  12.176 +> real	0m 22.29s
  12.177 +</code>
  12.178 \ No newline at end of file

    13.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    13.2 +++ b/pages/en/devnotes/cook-flavor-from-scratch.txt	Sat Feb 26 12:17:18 2011 +0000
    13.3 @@ -0,0 +1,186 @@
    13.4 +====== Cook a flavor from scratch ======
    13.5 +
    13.6 +===== Introduction =====
    13.7 +
    13.8 +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).
    13.9 +
   13.10 +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.
   13.11 +
   13.12 +==== Explanation ====
   13.13 +
   13.14 +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]].
   13.15 +
   13.16 +**Tools needed**
   13.17 +  * 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.
   13.18 +  * tazwok-experimental-0.0.2, tazchroot-0.0.1 and libtaz-0.0.1. Note: installing tazwok-experimental removes tazwok legacy.
   13.19 +  * An internet connection to download sources.
   13.20 +
   13.21 +**Steps**
   13.22 +  * 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).
   13.23 +  * 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.
   13.24 +  * Cook the definitive toolchain.
   13.25 +  * Cook some of the other packages of one of the SliTaz flavors.
   13.26 +  * Create the iso.
   13.27 +  * Burn, boot & enjoy :).
   13.28 +
   13.29 +
   13.30 +==== Install the tools ====
   13.31 +
   13.32 +<note tip>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.</note>
   13.33 +
   13.34 +Add the cooking-experimental repository as undigest:
   13.35 +<code>
   13.36 +tazpkg add-undigest experimental http://people.slitaz.org/~gokhlayeh/experimental/packages
   13.37 +</code>
   13.38 +
   13.39 +Give it priority over the main repository:
   13.40 +<code>
   13.41 +echo experimental > /var/lib/tazpkg/priority
   13.42 +</code>
   13.43 +
   13.44 +Install the cooking tools:
   13.45 +<code>
   13.46 +tazpkg get-install tazwok-experimental
   13.47 +tazpkg get-install tazchroot
   13.48 +</code>
   13.49 +
   13.50 +==== Cook toolchain ====
   13.51 +
   13.52 +<note tip>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.</note>
   13.53 +
   13.54 +Configure the //chroot//:
   13.55 +<code>
   13.56 +tazwok configure-chroot --SLITAZ_VERSION=experimental
   13.57 +</code>
   13.58 +
   13.59 +If you have at least 1GB RAM free you can put the minimal chroot in RAM speeding-up the cooking process:
   13.60 +<code>
   13.61 +sed 's~chroot_dir=.*~chroot_dir=/tmp/chroot-experimental~' -i /home/slitaz/experimental/tazchroot.conf
   13.62 +</code>
   13.63 +
   13.64 +All-in-one command to cook the toolchain packages:
   13.65 +<code>
   13.66 +tazwok cook-toolchain --SLITAZ_VERSION=experimental
   13.67 +</code>
   13.68 +
   13.69 +At the end of this operation the chroot should be removed. If you have modified its address before, you have to do this manually:
   13.70 +<code>
   13.71 +rm -r /tmp/chroot-experimental
   13.72 +</code>
   13.73 +
   13.74 +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:
   13.75 +<code>
   13.76 +tazwok check-incoming --SLITAZ_VERSION=experimental
   13.77 +</code>
   13.78 +
   13.79 +You need to tell to tazpkg that you now have a local version of experimental:
   13.80 +<code>
   13.81 +# If you had already defined the experimental repository:
   13.82 +echo "/home/slitaz/experimental/packages" > /var/lib/tazpkg/undigest/experimental/mirror
   13.83 +tazpkg recharge
   13.84 +# Else:
   13.85 +tazpkg add-undigest experimental /home/slitaz/experimental/packages
   13.86 +echo experimental > /var/lib/tazpkg/priority
   13.87 +tazpkg recharge
   13.88 +</code>
   13.89 +
   13.90 +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:
   13.91 +<code>
   13.92 +tazwok chroot --SLITAZ_VERSION=experimental
   13.93 +tazwok build-depends toolchain-cooklist | sed '1,/^gcc$/d' > /tmp/consolidate.list
   13.94 +tazwok cook-list /tmp/consolidate.list
   13.95 +rm /tmp/consolidate.list
   13.96 +</code>
   13.97 +
   13.98 +As packages has been re-cooked, you have to update the packages repository once again:
   13.99 +<code>
  13.100 +tazwok check-incoming
  13.101 +</code>
  13.102 +
  13.103 +Still in the chroot for the next step.
  13.104 +==== Cook packages of a flavor ====
  13.105 +
  13.106 +First you need data about cooking flavors:
  13.107 +<code>
  13.108 +cd /home/slitaz/experimental/flavors
  13.109 +hg clone http://hg.slitaz.org/flavors .
  13.110 +</code>
  13.111 +
  13.112 +Generate the cooklist for a given flavor. Note: for the next step, use the chosen flavor name instead of FLAVOR in the command line:
  13.113 +<code>
  13.114 +tazwok gen-cooklist --list=/home/slitaz/experimental/flavors/FLAVOR/packages.list > /tmp/FLAVOR.list
  13.115 +</code>
  13.116 +
  13.117 +This list contains some already cooked packages, remove them:
  13.118 +<code>
  13.119 +cat /tmp/FLAVOR.list | while read p; do
  13.120 +	grep -q ^$p$ /home/slitaz/experimental/packages/packages.txt && \
  13.121 +		sed "/^$p$/d" -i /tmp/FLAVOR.list
  13.122 +done
  13.123 +</code>
  13.124 +
  13.125 +
  13.126 +The cooklist is now ready to create the packages:
  13.127 +<code>
  13.128 +tazwok cook-list /tmp/FLAVOR.list
  13.129 +</code>
  13.130 +
  13.131 +Update packages repository:
  13.132 +<code>
  13.133 +tazwok check-incoming
  13.134 +</code>
  13.135 +
  13.136 +<note tip>You can repeat these steps each time you wish to add new packages to your repository.</note>
  13.137 +
  13.138 +Still in chroot for the next step.
  13.139 +
  13.140 +==== Create the ISO ====
  13.141 +
  13.142 +Actually tazlito uses /home/slitaz/flavors. Create a symbolic link:
  13.143 +<code>
  13.144 +ln -s /home/slitaz/experimental/flavors /home/slitaz
  13.145 +</code>
  13.146 +
  13.147 +Set release as experimental for the future ISO:
  13.148 +<code>
  13.149 +cd  /home/slitaz/flavors/FLAVOR
  13.150 +mkdir -p rootfs/etc
  13.151 +echo experimental > rootfs/etc/slitaz-release
  13.152 +</code>
  13.153 +
  13.154 +Configure your ISO to use your local repository:
  13.155 +<code>
  13.156 +mkdir -p rootfs/var/lib/tazpkg
  13.157 +echo /home/slitaz/experimental/packages > rootfs/var/lib/tazpkg/mirror
  13.158 +</code>
  13.159 +
  13.160 +Use tazwok-experimental instead of tazwok and add tazchroot:
  13.161 +<code>
  13.162 +sed 's/tazwok/tazwok-experimental/' -i packages.list
  13.163 +echo tazchroot >> packages.list
  13.164 +</code>
  13.165 +
  13.166 +Pack FLAVOR:
  13.167 +<code>
  13.168 +tazlito pack-flavor FLAVOR
  13.169 +</code>
  13.170 +
  13.171 +Get FLAVOR:
  13.172 +<code>
  13.173 +tazlito get-flavor FLAVOR
  13.174 +</code>
  13.175 +
  13.176 +Generate ISO:
  13.177 +<code>
  13.178 +tazlito gen-distro
  13.179 +</code>
  13.180 +
  13.181 +Save ISO in your home dir:
  13.182 +<code>
  13.183 +mv /home/slitaz/distro/slitaz-FLAVOR.iso /home/slitaz/distro/slitaz-FLAVOR.md5 /home/slitaz/experimental/iso
  13.184 +</code>
  13.185 +
  13.186 +Exit chroot:
  13.187 +<code>
  13.188 +exit
  13.189 +</code>
  13.190 \ No newline at end of file

    14.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    14.2 +++ b/pages/en/devnotes/new-tazwok-illustrated.txt	Sat Feb 26 12:17:18 2011 +0000
    14.3 @@ -0,0 +1,270 @@
    14.4 +====== The new tazwok illustrated! ======
    14.5 +
    14.6 +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.
    14.7 +
    14.8 +By simplifying the writing of recipes, we simplify the work and contribution that benefits everyone! 
    14.9 +
   14.10 +==== DEPENDS/BUILD_DEPENDS : ====
   14.11 +Tazwok now uses the dependent variable for finding the necessary compilation dependencies. 
   14.12 +Here's how it works:
   14.13 +
   14.14 +	* Tazwok tree list of all dependencies from the dependent variable
   14.15 +	* For each package, if there is a shareholder *-dev package, it adds it to the dependencies
   14.16 +	* Tazwok done the same for BUILD_DEPENDS.
   14.17 +
   14.18 +So far, when a packet was both dependency and build dependency, the recipe looked like this:
   14.19 +
   14.20 +<file>
   14.21 +DEPENDS="pkgX"
   14.22 +BUILD_DEPENDS="pkgX pkgX-dev"
   14.23 +</file>
   14.24 +Now that is enough:
   14.25 +<file>
   14.26 +DEPENDS="pkgX"
   14.27 +</file>
   14.28 +Where there were trees more complex dependencies, the recipe looked like this:
   14.29 +<file>
   14.30 +# pkgY depend's on pkgX
   14.31 +DEPENDS="pkgY"
   14.32 +BUILD_DEPENDS="pkgY pkgY-dev pkgX pkgX-dev"
   14.33 +</file>
   14.34 +Now that is enough:
   14.35 +<file>
   14.36 +DEPENDS="pkgY"
   14.37 +</file>
   14.38 +
   14.39 +The recipes also contain many redundancies in the definition of addiction, for example:
   14.40 +<file>
   14.41 +# pkgY depend's on pkgX
   14.42 +DEPENDS="pkgY pkgX"
   14.43 +</file>
   14.44 +Here, needless to say since pkgX will be installed along pkgY anyway (Tazpkg manages dependencies automatically!).
   14.45 +
   14.46 +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!
   14.47 +
   14.48 +<note tip>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.</note>
   14.49 +
   14.50 +**Examples:**
   14.51 +	* graveman: http://hg.slitaz.org/wok/rev/7f0604e0bde0
   14.52 +	* enlightenment & cie: http://hg.slitaz.org/wok/rev/85cd798d6997
   14.53 +
   14.54 +==== TARBALL/WGET_URL/SOURCE/download from the VCS ====
   14.55 +
   14.56 +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).
   14.57 +
   14.58 +//The packets affected by this://
   14.59 +	* wget url for https, ftps and some URLs that busybox does not include
   14.60 +	* mercurial/subversion/git: they are used to obtain the source
   14.61 +	* tar/unzip: sometimes necessary to unpack the sources.
   14.62 +
   14.63 +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!
   14.64 +
   14.65 +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.
   14.66 +
   14.67 +Tazwok also supports the use of mercurial/subversion/git in WGET_URL. The syntax is:
   14.68 +<file>WGET_URL="subversion|svn://svn.mplayerhq.hu/mplayer/trunk</file>
   14.69 +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.
   14.70 +
   14.71 +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.
   14.72 +
   14.73 +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.
   14.74 +
   14.75 +**Examples:**
   14.76 +	* Here was necessary wget: http://hg.slitaz.org/wok/rev/012847ddd0cb
   14.77 +	* Tinyproxy did not report the URL of its source code is corrected: http://hg.slitaz.org/wok/rev/25967da0e1af
   14.78 +	* WGET_URL now supports xpi: http://hg.slitaz.org/wok/rev/37738b3ee08f
   14.79 +	* WGET_URL with a "weird" URL:  http://hg.slitaz.org/wok/rev/102de15fea8d
   14.80 +	* WGET_URL using git: http://hg.slitaz.org/wok/rev/e06d60ae03eb
   14.81 +	* WGET_URL using subversion: http://hg.slitaz.org/wok/rev/c4c54646489a
   14.82 +	* WGET_URL using mercurial: http://hg.slitaz.org/wok/rev/756ed4b1daac
   14.83 +	* It was difficult to choose how to define BRANCH and VERSION for aufs: http://hg.slitaz.org/wok/rev/67231cfc5475
   14.84 +	* Here are two sources of records were in conflict, resolved by SOURCE: http://hg.slitaz.org/wok/rev/b891cba4f48e
   14.85 +	* 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
   14.86 +
   14.87 +==== Exceptions dependencies cooking ====
   14.88 +In some cases, no dependence cooking is installed:
   14.89 +	* For recipes with WANTED
   14.90 +	* For recipes without compile_rules()
   14.91 +
   14.92 +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.
   14.93 +
   14.94 +If you do not compile_rules() but want to force the installation of all dependencies of cooking, there is a little hack:
   14.95 +<file>
   14.96 +compiles_rules()
   14.97 +{
   14.98 +	:
   14.99 +}
  14.100 +</file>
  14.101 +
  14.102 +**Examples:**
  14.103 +	* Removal of compiles_rules() to avoid installing unnecessary dependencies Cooking: http://hg.slitaz.org/wok/rev/f579356b437f
  14.104 +	* Remove a hack with fake compiles_rules was useless ... http://hg.slitaz.org/wok/rev/5b4581f8e476
  14.105 +
  14.106 +==== Define src/_pkg & move in the right place (hacks in the recipe) ====
  14.107 +
  14.108 +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.
  14.109 +
  14.110 +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.
  14.111 +
  14.112 +The hacks in the recipe source that move in the right place are no longer needed either, and can also cause problems.
  14.113 +
  14.114 +In conclusion, it is better to consider that $src/$_pkg are defined by default and try to rely as much as possible.
  14.115 +
  14.116 +** Examples: **
  14.117 +	* Removing src= by Godane: http://hg.slitaz.org/wok/rev/a1c1d35d9f92
  14.118 +	* src=/_pkg= can / should also be removed from WANTED: http://hg.slitaz.org/wok/rev/07adb7cbd0c8
  14.119 +	* Here, an old hack was the problem: http://hg.slitaz.org/wok/rev/62f6142d9fb3
  14.120 +	* Sources are now //always// placed in a sub-directory $src http://hg.slitaz.org/wok/rev/e64069568fe7
  14.121 +	* Another case: call the configure script from a folder separate compilation (*-build): http://hg.slitaz.org/wok/rev/7461a0c31d62
  14.122 +	* Fixed dmraid: http://hg.slitaz.org/wok/rev/f5b7e0c47763 http://hg.slitaz.org/wok/rev/59ea9409ad8a
  14.123 +
  14.124 +==== Set the default paths in configure: ====
  14.125 +<note tip>See /etc/slitaz/slitaz.conf, /etc/config.site and the new revenue model in place by New tazwok tree</note>
  14.126 +
  14.127 +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.
  14.128 +
  14.129 +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.
  14.130 +
  14.131 +** Examples: **
  14.132 +	* A file or did not install properly in acl is corrected by CONFIG_SITE: http://hg.slitaz.org/wok/rev/f831ecb652a6
  14.133 +	* Another example: http://hg.slitaz.org/wok/rev/259214792e30
  14.134 +
  14.135 +<note tip>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 ...)</note>
  14.136 +
  14.137 +==== DESTDIR=$PWD/_pkg ====
  14.138 +
  14.139 +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().
  14.140 +
  14.141 +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.
  14.142 +
  14.143 +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.
  14.144 +
  14.145 +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.
  14.146 +
  14.147 +** Examples: **
  14.148 +	* Remove _pkg= & DESTDIR= same time for this to work: http://hg.slitaz.org/wok/rev/cf088243a4a5
  14.149 +	* Remove references "useless" to $src to the sources are withdrawn: http://hg.slitaz.org/wok/rev/0731792c3994 http://hg.slitaz.org/wok/rev/5d6340961543
  14.150 +	* Bash does not take into account DESTDIR environment variable: http://hg.slitaz.org/wok/rev/fa7b7514e1d8
  14.151 + 	* acl attr does not include DESTDIR (in this installation the destination was still $PWD/_pkg): http://hg.slitaz.org/wok/rev/fa7b7514e1d8
  14.152 +
  14.153 +==== MAKEFLAGS ====
  14.154 +
  14.155 +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:
  14.156 +make $MAKEFLAGS
  14.157 +
  14.158 +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)
  14.159 +
  14.160 +**Problems MAKEFLAGS:**
  14.161 +
  14.162 +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.
  14.163 +
  14.164 +//Problem in compiling://
  14.165 +
  14.166 +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.
  14.167 +
  14.168 +//Problem in installation://
  14.169 +
  14.170 +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.
  14.171 +
  14.172 +** Examples: **
  14.173 +	* Several changes explained here in the recipe for gettext: http://hg.slitaz.org/wok/rev/9411655af0e2
  14.174 +
  14.175 +==== Variables $stuff, $wanted_stuff and $fs ====
  14.176 +
  14.177 +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
  14.178 +
  14.179 +** Examples: **
  14.180 +	* A commit with several changes regarding the variable $stuff: http://hg.slitaz.org/wok/rev/be13f25e790b
  14.181 +	* A correction necessary when we have made an absolute path $fs: http://hg.slitaz.org/wok/rev/8c897d2542ab
  14.182 +
  14.183 +==== Do not use 'exit' but 'return' ====
  14.184 +
  14.185 +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.
  14.186 +
  14.187 +**Example:**
  14.188 +	* Removing all exit the wok recipes: http://hg.slitaz.org/wok/rev/0b4cf0d9e1b5
  14.189 +
  14.190 +==== Conclusion - What to do when updating a recipe: ====
  14.191 +
  14.192 +	* Remove src=/_pkg= recipe and those who declare as WANTED.
  14.193 +	* 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.
  14.194 +	* Remove the definition of default paths and see if it works, otherwise leave.
  14.195 +	* 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.
  14.196 +	* Remove BUILD_DEPENDS / DEPENDS redundant.
  14.197 +	* Check that packages are created correctly, otherwise update the paths in genpkg_rules().
  14.198 +	* Try to declare all sources of revenue in that SliTaz can be compiled without internet connection (requires to download any source before).
  14.199 +	* Check that the package needed to download / extract the source code are defined in BUILD_DEPENDS.
  14.200 +	* Check as EXIT is not used in the recipe.
  14.201 +
  14.202 +==== Some more complex cases ... ====
  14.203 +
  14.204 +I put them there in the end because there are already too many to be integrated:)
  14.205 +The items below correspond to specific cases.
  14.206 +
  14.207 +== Variable COOK_OPT ==
  14.208 +
  14.209 +This new variable can contain options that alter the behavior of tazwok. They are useful in very special cases.
  14.210 +
  14.211 +**genpkg=**
  14.212 +
  14.213 +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)
  14.214 +
  14.215 +Used in glibc: http://hg.slitaz.org/wok/file/tip/glibc/receipt
  14.216 +
  14.217 +**!repack_src**
  14.218 +
  14.219 +Disable re-compression format sources .tar.lzma.
  14.220 +
  14.221 +Ruby-pkgconfig used for the sources remain in gem: http://hg.slitaz.org/wok/file/tip/ruby-pkgconfig/receipt
  14.222 +
  14.223 +**!unpack**
  14.224 +
  14.225 +Prevents decompression of the archive-source in the wok.
  14.226 +
  14.227 +This is used by ruby-pkgconfig as well (see link above)
  14.228 +
  14.229 +This is the only case yet!
  14.230 +
  14.231 +==== Cooking the toolchain ====
  14.232 +
  14.233 +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
  14.234 +
  14.235 +Additional features are:
  14.236 +	* Precook_tmp_toolchain() - Used only by gcc & binutils for the moment, because they are cooked twice during the preparation of the temporary toolchain.
  14.237 +	* 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.
  14.238 +
  14.239 +** Examples: **
  14.240 +	* Binutils: http://hg.slitaz.org/wok/file/tip/binutils/receipt
  14.241 +	* Gettext: http://hg.slitaz.org/wok/file/tip/gettext/receipt
  14.242 +	* Bash: http://hg.slitaz.org/wok/file/tip/bash/receipt
  14.243 +	* Patch does not need cook_tmp_toolchain(): http://hg.slitaz.org/wok/file/tip/patch/receipt
  14.244 +	* Autoconf either: http://hg.slitaz.org/wok/file/tip/autoconf/receipt
  14.245 +
  14.246 +== tazwok get-src / report in recipes ==
  14.247 +
  14.248 +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):
  14.249 +
  14.250 +<file>
  14.251 +compile_rules() # Per example
  14.252 +{
  14.253 +	report open-bloc #compiles_rules is a step, declaring that there will substeps
  14.254 +	report step "Action machin"
  14.255 +		...
  14.256 +	report step "Action truc"
  14.257 +		.. 
  14.258 +	report close-bloc #Close the open block previously
  14.259 +}
  14.260 +</file>
  14.261 +
  14.262 +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"
  14.263 +
  14.264 +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.
  14.265 +
  14.266 +The practical use of this tazwok get-src is that you can unpack the sources of designated PACKAGE at target.
  14.267 +
  14.268 +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.
  14.269 +
  14.270 +** Examples (recipe + log): **
  14.271 +	* 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
  14.272 +	* 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
  14.273 +	* 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
  14.274 \ No newline at end of file

    15.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    15.2 +++ b/pages/en/devnotes/prepare-experimental.txt	Sat Feb 26 12:17:18 2011 +0000
    15.3 @@ -0,0 +1,88 @@
    15.4 +====== Prepare the experimental wok ======
    15.5 +
    15.6 +==== Warning ====
    15.7 +
    15.8 +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.
    15.9 +
   15.10 +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).
   15.11 +
   15.12 +==== Enabling Mercurial Queue ====
   15.13 +
   15.14 +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:
   15.15 +
   15.16 +<code>
   15.17 +[extensions]
   15.18 +mq =
   15.19 +</code>
   15.20 +
   15.21 +==== Download cooking wok & patch it ====
   15.22 +
   15.23 +First check that the destination disk is mounted. In the directory which contains the data, create a repository called experimental and enter in it:
   15.24 +<code>
   15.25 +cd destination
   15.26 +mkdir experimental
   15.27 +cd experimental
   15.28 +</code>
   15.29 +
   15.30 +
   15.31 +Download the wok:
   15.32 +<code>
   15.33 +hg clone http://hg.slitaz.org/wok wok
   15.34 +</code>
   15.35 +
   15.36 +If you were root, enable read/write permissions to your normal account; then exit the root one:
   15.37 +<code>
   15.38 +chown tux.tux -R wok
   15.39 +</code>
   15.40 +
   15.41 +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.
   15.42 +Update the wok to the good revision:
   15.43 +<code>
   15.44 +hg update -C rev
   15.45 +</code>
   15.46 +
   15.47 +Download experimental patches:
   15.48 +<code>
   15.49 +cd .hg
   15.50 +hg clone http://hg.slitaz.org/wok-experimental patches
   15.51 +</code>
   15.52 +
   15.53 +Apply patches:
   15.54 +<code>
   15.55 +cd ..
   15.56 +hg qpush -a
   15.57 +</code>
   15.58 +
   15.59 +==== Update the experimental wok ====
   15.60 +
   15.61 +Go into the wok:
   15.62 +<code>
   15.63 +cd ?/wok
   15.64 +</code>
   15.65 +
   15.66 +Unapply patches (doesn't work if modifications are uncommitted):
   15.67 +<code>
   15.68 +hg qpop-a
   15.69 +</code>
   15.70 +
   15.71 +Update cooking wok:
   15.72 +<code>
   15.73 +hg pull
   15.74 +</code>
   15.75 +
   15.76 +Check the revision to use at http://hg.slitaz.org/wok-experimental and update the working directory to this revision:
   15.77 +<code>
   15.78 +hg update -C rev
   15.79 +</code>
   15.80 +
   15.81 +Update patches repository:
   15.82 +<code>
   15.83 +cd .hg/patches
   15.84 +hg pull -u
   15.85 +</code>
   15.86 +
   15.87 +Apply the new patches:
   15.88 +<code>
   15.89 +cd ../..
   15.90 +hg qpush -a
   15.91 +</code>
   15.92 \ No newline at end of file

    16.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    16.2 +++ b/pages/en/devnotes/start.txt	Sat Feb 26 12:17:18 2011 +0000
    16.3 @@ -0,0 +1,14 @@
    16.4 +====== Development Notes ======
    16.5 +
    16.6 +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.
    16.7 +
    16.8 +===== Information for users ===== 
    16.9 +
   16.10 +  * [[xorgserver-user|xorg-server-1.8]] - Update configuration
   16.11 +
   16.12 +===== Information for contributors =====
   16.13 +
   16.14 +  * [[xorgserver-contrib|xorg-server-1.8 ]] - Drivers pre-configuration
   16.15 +  * [[en:devnotes:prepare-experimental|Prepare the experimental wok]] - Howto use the experimentals patches with MQ
   16.16 +  * [[en:devnotes:ash-benchmarks|Ash benchmarks]] - How-to optimize ash scripts ?
   16.17 +  * [[en:devnotes:new-tazwok-illustrated|New Tazwok]] - How the new tazwok works ?
   16.18 \ No newline at end of file

    17.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    17.2 +++ b/pages/en/devnotes/xorgserver-contrib.txt	Sat Feb 26 12:17:18 2011 +0000
    17.3 @@ -0,0 +1,63 @@
    17.4 +====== xorg-server-1.8 ======
    17.5 +
    17.6 +===== Introduction =====
    17.7 +
    17.8 +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. 
    17.9 +
   17.10 +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 :
   17.11 +
   17.12 +  * 00 - ServerFlag
   17.13 +  * 05 - ServerLayout Tweaks
   17.14 +  * 10 - ServerLayout
   17.15 +  * 15 - Files Tweaks
   17.16 +  * 20 - Files
   17.17 +  * 25 - Modules Tweaks
   17.18 +  * 30 - Modules
   17.19 +  * 35 - InputClass/InputDevice Tweaks
   17.20 +  * 40 - InputClass/InputDevice
   17.21 +  * 45 - Monitor Tweaks
   17.22 +  * 50 - Monitor
   17.23 +  * 55 - Device Tweaks
   17.24 +  * 60 - Device
   17.25 +  * 65 - Screen Tweaks
   17.26 +  * 70 - Screen 
   17.27 +  * 75 - Modes Tweaks
   17.28 +  * 80 - Modes
   17.29 +  * 85 - DRI Tweaks
   17.30 +  * 90 - DRI
   17.31 +  * 95 - Extension Tweaks
   17.32 +  * 100 - Extension
   17.33 +
   17.34 +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. 
   17.35 +
   17.36 +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.
   17.37 +
   17.38 +Examples :
   17.39 +
   17.40 +  * [[http://hg.slitaz.org/wok/file/c29991cef110/xorg-xf86-input-evdev/stuff/40-evdev.conf|40-evedev.conf]] - Default configuration for all devices
   17.41 +  * [[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
   17.42 +  * 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
   17.43 +
   17.44 +===== Configuration files list =====
   17.45 +
   17.46 +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.
   17.47 +
   17.48 +tazx :
   17.49 +  * 10-ServerLayout.conf
   17.50 +  * 20-Files.conf
   17.51 +  * 30-Module.conf
   17.52 +  * 40-Keyboard.conf
   17.53 +  * 50-Monitor.conf
   17.54 +  * 60-Device.conf
   17.55 +  * 70-Screen.conf
   17.56 +tazhw :
   17.57 +  * 55-DeviceTweaks.conf
   17.58 +xorg-xf86-input-evdev :
   17.59 +  * 40-evdev.conf
   17.60 +xorg-xf86-input-synaptics :
   17.61 +  * 35-synaptics.conf
   17.62 +
   17.63 +===== TODO =====
   17.64 +
   17.65 +  * 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.
   17.66 +  * Pre-configure some drivers to make them work out-of-the-box.
   17.67 \ No newline at end of file

    18.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    18.2 +++ b/pages/en/devnotes/xorgserver-user.txt	Sat Feb 26 12:17:18 2011 +0000
    18.3 @@ -0,0 +1,29 @@
    18.4 +======= xorg-server-1.8 ======
    18.5 +
    18.6 +===== Upgrade Xorg configuration =====
    18.7 +
    18.8 +
    18.9 +Upgrade Slitaz :
   18.10 +<code># echo 'y' | tazpkg upgrade</code>
   18.11 +Backup xorg.conf :
   18.12 +<code># mv /etc/X11/xorg.conf /etc/X11/xorg.conf-backup</code>
   18.13 +Re-configure Xorg with tazx :
   18.14 +<code># tazx config-xorg</code>
   18.15 +
   18.16 +==== User tweaks ====
   18.17 +
   18.18 +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 :
   18.19 +
   18.20 +  * 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.
   18.21 +
   18.22 +  * You put them in the correct file in the directory ///etc/X11/xorg.conf.d.// SliTaz use two files for each Xorg section : 
   18.23 +          * n0-Section.conf for the default configuration and : 
   18.24 +          * (n-1)5-SectionTweaks.conf for the configurations which overwrite the default one.
   18.25 +
   18.26 +Example :
   18.27 +
   18.28 +//40-evdev.conf// contains the default configuration for all devices.
   18.29 +
   18.30 +//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).
   18.31 +
   18.32 +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.
   18.33 \ No newline at end of file

    19.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    19.2 +++ b/pages/en/forum/start.txt	Sat Feb 26 12:17:18 2011 +0000
    19.3 @@ -0,0 +1,3 @@
    19.4 +====== Forum posts ======
    19.5 +
    19.6 +[[http://forum.slitaz.org/index.php?p=/discussion/comment/5404/#Comment_5404|How to build your own kernel modules]]
    19.7 \ No newline at end of file

    20.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    20.2 +++ b/pages/en/guides/alsaequal.txt	Sat Feb 26 12:17:18 2011 +0000
    20.3 @@ -0,0 +1,84 @@
    20.4 +====== Alsaequal ======
    20.5 +
    20.6 +===== Installation (cooking only) =====
    20.7 +
    20.8 +First download alsaequal:
    20.9 +
   20.10 +<code># tazpkg get-install alsaequal</code>
   20.11 +
   20.12 +Then create a /home/tux/.asoundrc file:
   20.13 +
   20.14 +<file>
   20.15 +ctl.equal {
   20.16 +  type equal;
   20.17 +}
   20.18 +
   20.19 +pcm.plugequal {
   20.20 +  type equal;
   20.21 +  # Modify the line below if you don't
   20.22 +  # want to use sound card 0.
   20.23 +  # slave.pcm "plughw:0,0";
   20.24 +  # or if you want to use with multiple applications output to dmix
   20.25 +  slave.pcm "plug:dmix"
   20.26 +}
   20.27 +
   20.28 +pcm.equal {
   20.29 +  # Or if you want the equalizer to be your
   20.30 +  # default soundcard uncomment the following
   20.31 +  # line and comment the above line.
   20.32 +# pcm.!default {
   20.33 +  type plug;
   20.34 +  slave.pcm plugequal;
   20.35 +}
   20.36 +</file>
   20.37 +
   20.38 +===== mpg123 =====
   20.39 +
   20.40 +Change (cd) into your music directory and then run:
   20.41 +
   20.42 +<code>$ mpg123 -a equal *</code>
   20.43 +
   20.44 +Or
   20.45 +
   20.46 +<code>$ mpg123 -a equal track1</code>
   20.47 +
   20.48 +Now you should be able to open up a separate terminal and use:
   20.49 +
   20.50 +<code>$ alsamixer -D equal</code>
   20.51 +
   20.52 +===== mpd =====
   20.53 +
   20.54 +Just edit the audio_output section of your /etc/mpd.conf:
   20.55 +
   20.56 +<file>
   20.57 +audio_output {
   20.58 +	type		"alsa"
   20.59 +	name		"equal"
   20.60 +	device		"plug:plugequal"
   20.61 +##	format		"44100:16:2"	# optional
   20.62 +##	mixer_device	"default"	# optional
   20.63 +##	mixer_control	"PCM"		# optional
   20.64 +##	mixer_index	"0"		# optional
   20.65 +}
   20.66 +</file>
   20.67 +
   20.68 +And start/restart mpd and you should be able to use //$ alsamixer -D equal//
   20.69 +
   20.70 +===== moc =====
   20.71 +
   20.72 +Copy the config.example file in /usr/share/doc/moc to your ~/.moc folder:
   20.73 +
   20.74 +<code>$ cp /usr/share/doc/moc/config.example ~/.moc/config</code>
   20.75 +
   20.76 +Then change the alsa output device line to: 
   20.77 +
   20.78 +<file>
   20.79 +# ALSA output device
   20.80 +AlsaDevice    = equal
   20.81 +</file>		
   20.82 +
   20.83 +And then start/restart moc.
   20.84 +
   20.85 +===== References =====
   20.86 +
   20.87 +http://www.thedigitalmachine.net/alsaequal.html
   20.88 \ No newline at end of file

    21.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    21.2 +++ b/pages/en/guides/bluetooth.txt	Sat Feb 26 12:17:18 2011 +0000
    21.3 @@ -0,0 +1,131 @@
    21.4 +====== Bluetooth ======
    21.5 +
    21.6 +===== Introduction =====
    21.7 +
    21.8 +This guide will help you to configure bluetooth, e.g. to use your phone as a modem.
    21.9 +Do following steps as root.
   21.10 +First of all you must install Slitaz packages related to bluetooth:
   21.11 +  # tazpkg get-install bluez
   21.12 +  # tazpkg get-install linux-bluetooth
   21.13 +The first package contains the Official Linux Bluetooth protocol stack www.bluez.org and the second contains the kernel modules related to bluetooth.
   21.14 +Now you can launch the bluetooth daemon:
   21.15 +  # bluetoothd
   21.16 +And load the module required by your local bluetooth device, this is very likely btusb:
   21.17 +  # modprobe btusb
   21.18 +If btusb is the module you need the command "hcitool dev" to show you the local device address:
   21.19 +  root@slitaz:/home/tux# hcitool dev
   21.20 +  Devices:
   21.21 +          hci0    00:02:72:xx:xx:xx
   21.22 +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.
   21.23 +Now that you have hci* you can run the "hcitool scan" command to show you if there is any discoverable device nearby.
   21.24 +So if you are searching, e.g. your phone, remember to put it in discoverable mode:
   21.25 +  root@slitaz:/home/tux# hcitool scan
   21.26 +  Scanning ...
   21.27 +          00:18:C5:xx:xx:xx       Nokia 6151
   21.28 +  root@slitaz:/home/tux#
   21.29 +Now you can pair your locale device with your remote device. You use bluez-simple-agent to do that.
   21.30 +
   21.31 +If you want to start the pairing from the remote device you need to put your local device in discoverable mode:
   21.32 +  # hciconfig hci0 piscan
   21.33 +
   21.34 +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.
   21.35 +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:
   21.36 +  root@slitaz:/home/tux# hciconfig hci0 piscan
   21.37 +  root@slitaz:/home/tux# bluez-simple-agent
   21.38 +  Agent registered
   21.39 +  RequestPinCode (/org/bluez/2944/hci0/dev_00_18_C5_xx_xx_xx)
   21.40 +  Enter PIN Code: 1234
   21.41 +  ^CTraceback (most recent call last):
   21.42 +    File "/usr/bin/bluez-simple-agent", line 113, in <module>
   21.43 +      mainloop.run()
   21.44 +  KeyboardInterrupt
   21.45 +  root@slitaz:/home/tux#
   21.46 +Put your local device back in undiscoverable mode:
   21.47 +  # hciconfig hci0 pscan
   21.48 +
   21.49 +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:
   21.50 +  root@slitaz:/home/tux# bluez-simple-agent hci0 00:18:C5:xx:xx:xx
   21.51 +  RequestPinCode (/org/bluez/3078/hci0/dev_00_18_C5_xx_xx_xx)
   21.52 +  Enter PIN Code: 1234
   21.53 +  Release
   21.54 +  New device (/org/bluez/3078/hci0/dev_00_18_C5_xx_xx_xx)
   21.55 +  root@slitaz:/home/tux# 
   21.56 +Be fast because bluez-simple-agent has a timeout which I don't know how to set (suggestions?)
   21.57 +
   21.58 +===== Use a phone as a modem =====
   21.59 +
   21.60 +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.
   21.61 +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:
   21.62 +  root@slitaz:/home/tux# zcat /proc/config.gz | grep RFCOMM                    
   21.63 +  CONFIG_BT_RFCOMM=m
   21.64 +  # CONFIG_BT_RFCOMM_TTY is not set
   21.65 +  root@slitaz:/home/tux#
   21.66 +If CONFIG_BT_RFCOMM_TTY is not =y you must recompile the module with tty support. Install linux-source:
   21.67 +  # tazpkg get-install linux-source
   21.68 +cd in /usr/src/linux-`uname -r`/ and give this command:
   21.69 +  # make CONFIG_BT_RFCOMM=m CONFIG_BT_RFCOMM_TTY=y M=net/bluetooth/rfcomm
   21.70 +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.
   21.71 +Now you can delete the old rfcomm module and replace it with your module:
   21.72 +  # rm /lib/modules/`uname -r`/kernel/net/bluetooth/rfcomm/rfcomm.ko.gz
   21.73 +  # cp /usr/src/linux-`uname -r`/net/bluetooth/rfcomm/rfcomm.ko /lib/modules/`uname -r`/kernel/net/bluetooth/rfcomm/ 
   21.74 +  # depmod -a
   21.75 +Now that we have a working rfcomm module we must detect the channel where the phone dialup service is listening:
   21.76 +  # sdptool browse 00:18:C5:xx:xx:xx
   21.77 +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:
   21.78 +  Service Name: Dial-up networking
   21.79 +  Service RecHandle: 0x10000
   21.80 +  Service Class ID List:
   21.81 +    "Dialup Networking" (0x1103)
   21.82 +    "Generic Networking" (0x1201)
   21.83 +  Protocol Descriptor List:
   21.84 +    "L2CAP" (0x0100)
   21.85 +    "RFCOMM" (0x0003)
   21.86 +      Channel: 1
   21.87 +  Language Base Attr List:
   21.88 +    code_ISO639: 0x656e
   21.89 +    encoding:    0x6a
   21.90 +    base_offset: 0x100
   21.91 +  Profile Descriptor List:
   21.92 +    "Dialup Networking" (0x1103)
   21.93 +      Version: 0x0100
   21.94 +      
   21.95 +===== rfcomm.conf =====
   21.96 +
   21.97 +As you can see it is listening on channel 1, so you edit ///etc/bluetooth/rfcomm.conf// this way:
   21.98 +<file>
   21.99 +  #
  21.100 +  # RFCOMM configuration file.
  21.101 +  #
  21.102 +  rfcomm0 {
  21.103 +  #       # Automatically bind the device at startup
  21.104 +          bind yes;
  21.105 +  #
  21.106 +  #       # Bluetooth address of the device
  21.107 +          device 00:18:C5:xx:xx:xx;
  21.108 +  #
  21.109 +  #       # RFCOMM channel for the connection
  21.110 +          channel 1;
  21.111 +  #
  21.112 +  #       # Description of the connection
  21.113 +  #       comment "Example Bluetooth device";
  21.114 +  }
  21.115 +</file>
  21.116 +Now with:
  21.117 +  # modprobe rfcomm
  21.118 +  # rfcomm bind all
  21.119 +You can use /dev/rfcomm0 as a modem in a wvdial script.
  21.120 +You may want to check this guide http://doc.slitaz.org/en:guides:dialup
  21.121 +
  21.122 +---- 
  21.123 +\\
  21.124 +^  Page Review Section  ^^ 
  21.125 +|Quality| Good  |
  21.126 +|Review| Minor Updates  |
  21.127 +|Priority| Medium |
  21.128 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
  21.129 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
  21.130 +|How to Improve| Add tazhw setup bluetooth ; Please create "sections" for toc|
  21.131 +|::: |  |
  21.132 +
  21.133 +\\
  21.134 +----
  21.135 \ No newline at end of file

    22.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    22.2 +++ b/pages/en/guides/boottime.txt	Sat Feb 26 12:17:18 2011 +0000
    22.3 @@ -0,0 +1,40 @@
    22.4 +====== Boot time ======
    22.5 +
    22.6 +SliTaz boots fast! But most likely you haven't turned super fast boot on yet. To do this, just edit your ///etc/rcS.conf// :
    22.7 +<file> FAST_BOOT_X="yes" </file>
    22.8 +
    22.9 +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. 
   22.10 +
   22.11 +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. 
   22.12 +
   22.13 +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:
   22.14 +
   22.15 +<code> # tazpkg get-install pybootchartgui </code>
   22.16 +
   22.17 +Pybootchartgui will then create a chart automatically in ///var/log//. 
   22.18 +
   22.19 +Now, just edit your //menu.lst// file for grub and add init=/sbin/bootchartd. In my case, it's like this:
   22.20 +
   22.21 +<file>
   22.22 +title slitaz with bootchart
   22.23 +root (hd0,8)
   22.24 +kernel /boot/vmlinuz-2.6.30.6-slitaz root=/dev/sda9 init=/sbin/bootchartd quiet
   22.25 +</file>
   22.26 +
   22.27 +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!!!:
   22.28 +
   22.29 +{{ :en:guides:image:bootchart.png?100 |My bootchart}}
   22.30 +
   22.31 +---- 
   22.32 +\\
   22.33 +^  Page Review Section  ^^ 
   22.34 +|Quality| Good  |
   22.35 +|Review| Minor Updates  |
   22.36 +|Priority| Medium |
   22.37 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
   22.38 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
   22.39 +|How to Improve| Suggest briefly|
   22.40 +|::: |  |
   22.41 +
   22.42 +\\
   22.43 +----
   22.44 \ No newline at end of file

    23.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    23.2 +++ b/pages/en/guides/bugs.txt	Sat Feb 26 12:17:18 2011 +0000
    23.3 @@ -0,0 +1,19 @@
    23.4 +====== BUGS ======
    23.5 +
    23.6 +The problems listed in this page refer to the Slitaz 3.0 environment.
    23.7 +
    23.8 +===== Burning a CD with Burnbox =====
    23.9 +
   23.10 +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). 
   23.11 +
   23.12 +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.
   23.13 +
   23.14 +===== Abiword =====
   23.15 +
   23.16 +With AbiWord you MUST install glibc-locale too, it was forgotten as a dependency, but it is needed for AbiWord to work properly.
   23.17 +
   23.18 +===== Chat entry of the Internet menu =====
   23.19 +
   23.20 +This should install pidgin and skype. Practically it has sometimes (but not always) installed pidgin, and always failed to install Skype.
   23.21 +Install Pigin and Skype (well, get-skype) from the package manager.
   23.22 + 
   23.23 \ No newline at end of file

    24.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    24.2 +++ b/pages/en/guides/chroot.txt	Sat Feb 26 12:17:18 2011 +0000
    24.3 @@ -0,0 +1,96 @@
    24.4 +====== Chroot =======
    24.5 +
    24.6 +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.
    24.7 +
    24.8 +===== With Tazdev =====
    24.9 +
   24.10 +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:
   24.11 +
   24.12 +<code>
   24.13 +# tazpkg get-install slitaz-dev-tools
   24.14 +# tazdev gen-chroot
   24.15 +# tazdev chroot
   24.16 +</code>
   24.17 +
   24.18 +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.
   24.19 +
   24.20 +===== Create the chroot =====
   24.21 +<file>
   24.22 +#!/bin/sh
   24.23 +mkdir /home/chroot
   24.24 +# You can mount a device to /home/chroot
   24.25 +# with mountbox or mount
   24.26 +tazpkg get-install busybox --root="/home/chroot"
   24.27 +echo "No" | tazpkg get-install bash --root="/home/chroot"
   24.28 +tazpkg get-install slitaz-toolchain --root="/home/chroot"
   24.29 +tazpkg get-install tazwok --root="/home/chroot"
   24.30 +tazpkg get-install tazpkg --root="/home/chroot"
   24.31 +tazpkg get-install lzma --root="/home/chroot"
   24.32 +mkdir /home/chroot/home/slitaz</file>
   24.33 +
   24.34 +Note, you can keep these lines in a script file if needed. Just add #!/bin/sh to the first line and make executable with:
   24.35 +<code># chmod +x script_file</code>
   24.36 +
   24.37 +===== Add a script file to automate some actions =====
   24.38 +
   24.39 +<code># cat > /home/chroot/chroot_script.sh << "EOF"</code>
   24.40 +<file>
   24.41 +#!/bin/sh
   24.42 +/bin/sh --login
   24.43 +for pkg in $(cat /var/log/tazpkg.log | grep -v Removed | sed 's/\(.*\)\(- Installed - \)\(.*\)\( (.*\)/\3/'); do
   24.44 +	echo "y" | tazpkg remove $pkg
   24.45 +done
   24.46 +rm /var/log/tazpkg.log
   24.47 +
   24.48 +EOF
   24.49 +</file>
   24.50 +<code># chmod +x "/home/chroot/chroot_script.sh"</code>
   24.51 +
   24.52 +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.
   24.53 +
   24.54 +===== Add a script to mount and umount chroot =====
   24.55 +
   24.56 +<code># cat > /usr/bin/tazchroot << "EOF"</code>
   24.57 +<file>
   24.58 +#!/bin/sh
   24.59 +cat /etc/resolv.conf > /home/chroot/etc/resolv.conf
   24.60 +if [ ! -d "/home/chroot/proc/1" ]; then
   24.61 +	echo "Mounting virtual filesystems..."
   24.62 +	mount -t proc proc /home/chroot/proc
   24.63 +	mount -t sysfs sysfs /home/chroot/sys
   24.64 +	mount -t devpts devpts /home/chroot/dev/pts
   24.65 +	mount -t tmpfs shm /home/chroot/dev/shm
   24.66 +	mount /home/slitaz /home/chroot/home/slitaz
   24.67 +	chroot /home/chroot ./chroot_script.sh
   24.68 +	until [ "$ps" = "2" ]; do
   24.69 +		echo "Waiting for the end of all other chroot processes..."
   24.70 +		ps=$(ps | grep `basename $0` | grep -v grep | grep -v basename | wc -l)
   24.71 +		sleep 1
   24.72 +	done
   24.73 +	umount /home/chroot/home/slitaz
   24.74 +	umount /home/chroot/dev/shm
   24.75 +	umount /home/chroot/dev/pts
   24.76 +	umount /home/chroot/sys
   24.77 +	umount /home/chroot/proc
   24.78 +else
   24.79 +	echo "The chroot is already mounted"
   24.80 +fi
   24.81 +EOF
   24.82 +</file>
   24.83 +<code># chmod +x /usr/bin/tazchroot</code>
   24.84 +
   24.85 +Note, this script mounts ///home/slitaz// in your chroot, so you can use tazwok as if it was in your normal environment.
   24.86 +
   24.87 +---- 
   24.88 +\\
   24.89 +^  Page Review Section  ^^ 
   24.90 +|Quality| Good  |
   24.91 +|Review| Minor Updates  |
   24.92 +|Priority| Medium |
   24.93 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
   24.94 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
   24.95 +|How to Improve| Suggest briefly|
   24.96 +|::: |  |
   24.97 +
   24.98 +\\
   24.99 +----
  24.100 \ No newline at end of file

    25.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    25.2 +++ b/pages/en/guides/conspy.txt	Sat Feb 26 12:17:18 2011 +0000
    25.3 @@ -0,0 +1,107 @@
    25.4 +====== Conspy : tiny screen or VNC ======
    25.5 +
    25.6 +Slitaz core provides the 10Kb conspy to get remote control of Linux virtual consoles. See http://ace-host.stuart.id.au/russell/files/conspy/
    25.7 +
    25.8 +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).
    25.9 +
   25.10 +To exit from conspy (and the virtual console) press the escape key three times in quick succession.
   25.11 +
   25.12 +===== Conspy as screen (session manager) =====
   25.13 +
   25.14 +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.
   25.15 +You can open a new console / new session (say console 28) with //openvt -c 28 /bin/login// or //openvt -c 28 /bin/ash//.
   25.16 +You can free this virtual console with //deallocvt 28//.
   25.17 +
   25.18 +Example:
   25.19 +<code>
   25.20 +home$ ssh tux@slitazbox
   25.21 +box$ su
   25.22 +box# openvt -c 28 /bin/ash
   25.23 +box# conspy 28
   25.24 +# some commands
   25.25 +...
   25.26 +# <ESC><ESC><ESC>
   25.27 +box# exit
   25.28 +box$ exit
   25.29 +</code>
   25.30 +Later:
   25.31 +<code>
   25.32 +home$ ssh tux@slitazbox
   25.33 +box$ su
   25.34 +box# conspy 28
   25.35 +# more commands
   25.36 +...
   25.37 +# <ESC><ESC><ESC> 
   25.38 +box# exit
   25.39 +box$ exit
   25.40 +</code>
   25.41 +To close the session:
   25.42 +<code>
   25.43 +home$ ssh tux@slitazbox
   25.44 +box$ su
   25.45 +box# conspy 28
   25.46 +# exit
   25.47 +<ESC><ESC><ESC>
   25.48 +box# deallocvt 28
   25.49 +box# exit
   25.50 +box$ exit
   25.51 +</code>
   25.52 +If you prefer to use screen, see http://www.gnu.org/software/screen:
   25.53 +<code>
   25.54 +# tazpkg get-install screen
   25.55 +$ screen -S MySession
   25.56 +</code>
   25.57 +
   25.58 +===== Conspy as VNC (shared console) =====
   25.59 +
   25.60 +You can share a virtual console between two or more users.
   25.61 +Say RemoteUser wants to show some commands to SlitazUser using SlitazBox.
   25.62 +RemoteUser selects SlitazUser's console with //chvt//:
   25.63 +<code>
   25.64 +home$ ssh SlitazBox
   25.65 +SlitazBox$ su
   25.66 +SlitazBox# chvt 1
   25.67 +SlitazBox# conspy 1
   25.68 +</code>
   25.69 +Now both users show the same terminal. A third user can do //conspy 1// too.
   25.70 +
   25.71 +If you prefer to share the X11 display, install x11vnc (VNC server) and x11vnc-extra (java VNC client) see http://www.karlrunge.com/x11vnc/:
   25.72 +<code>
   25.73 +SlitazBox# tazpkg get-install x11vnc
   25.74 +SlitazBox# tazpkg get-install x11vnc-extra
   25.75 +SlitazBox# /etc/init.d/x11vnc start
   25.76 +</code>
   25.77 +<code>
   25.78 +home$ su
   25.79 +home# get-java-jre
   25.80 +home# exit
   25.81 +home$ firefox http://SlitazBox:5800/ultrasigned.vnc
   25.82 +</code>
   25.83 +
   25.84 +===== Conspy and slow connections =====
   25.85 +
   25.86 +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. 
   25.87 +===== Conspy and Busybox =====
   25.88 +
   25.89 +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:
   25.90 +  * -c to create missing devices (/dev/vcsaXX and /dev/ttyXX)
   25.91 +  * -d for screen shot<code># conspy -d 28 > screen28.txt</code>
   25.92 +  * -s to launch a shell<code># conspy -cs 28</code> (no more openvt)
   25.93 +  * -x COL -y LINE upper left corner position
   25.94 +  * -f follow cursor with automatic scrollings
   25.95 +
   25.96 +The conspy applet is enabled in the busybox package. The conspy package is no longer more useful than the recent busybox.
   25.97 +
   25.98 +---- 
   25.99 +\\
  25.100 +^  Page Review Section  ^^ 
  25.101 +|Quality| Good  |
  25.102 +|Review| Minor Updates  |
  25.103 +|Priority| Medium |
  25.104 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
  25.105 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
  25.106 +|How to Improve| Suggest briefly|
  25.107 +|::: |  |
  25.108 +
  25.109 +\\
  25.110 +----
  25.111 \ No newline at end of file

    26.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    26.2 +++ b/pages/en/guides/contributor.txt	Sat Feb 26 12:17:18 2011 +0000
    26.3 @@ -0,0 +1,68 @@
    26.4 +====== Contributing to SliTaz ======
    26.5 +
    26.6 +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!
    26.7 +
    26.8 +Post a quick message to the forum or mailing list if you're unsure about anything. We don't bite!
    26.9 +
   26.10 +<note tip>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!</note>
   26.11 +
   26.12 +\\
   26.13 +
   26.14 +===== Developers & Hackers =====
   26.15 +
   26.16 +=== Packaging ===
   26.17 +
   26.18 +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.
   26.19 +
   26.20 +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.
   26.21 +
   26.22 +=== Package Testing and Debugging ===
   26.23 +
   26.24 +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. 
   26.25 +
   26.26 +\\
   26.27 +
   26.28 +===== Writers & Translators =====
   26.29 +
   26.30 +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.
   26.31 +
   26.32 +There's many areas in which you can help:
   26.33 +
   26.34 +  * **Are you experienced with SliTaz?**
   26.35 +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!
   26.36 +
   26.37 +  * **Are you a general Linux user?**
   26.38 +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.
   26.39 +
   26.40 +  * **Do you speak non-English?**
   26.41 +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!
   26.42 +
   26.43 +\\
   26.44 +
   26.45 +===== Artists & Designers =====
   26.46 +
   26.47 +[[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!
   26.48 +
   26.49 +\\
   26.50 +
   26.51 +===== PR & Journalism =====
   26.52 +
   26.53 +//(Could we put together some blurbs or short pieces of writing for the press & community? Maybe contacts for them?)//
   26.54 +
   26.55 +\\
   26.56 +
   26.57 +
   26.58 +---- 
   26.59 +\\
   26.60 +^  Page Review Section  ^^ 
   26.61 +|Quality| Low  |
   26.62 +|Review| Major Updates FIXME  |
   26.63 +|Priority| High |
   26.64 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
   26.65 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
   26.66 +|How to Improve| Suggest briefly, e.g.,|
   26.67 +|::: | [[en:guides:start | Add link]]|
   26.68 +|::: | Add new rows like this ;-)  |
   26.69 +
   26.70 +\\
   26.71 +----

    27.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    27.2 +++ b/pages/en/guides/cpu-frequency.txt	Sat Feb 26 12:17:18 2011 +0000
    27.3 @@ -0,0 +1,93 @@
    27.4 +======= CPU Frequency Scaling =======
    27.5 +
    27.6 +==== Introduction ====
    27.7 +
    27.8 +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. 
    27.9 +
   27.10 +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.
   27.11 +
   27.12 +==== Installation ====
   27.13 +
   27.14 +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.
   27.15 +
   27.16 +<code># tazpkg get-install linux-cpufreq
   27.17 +# tazpkg get-install linux-acpi,
   27.18 +# wget http://mirror.slitaz.org/packages/cooking/cpufrequtils-008.tazpkg
   27.19 +# wget http://mirror.slitaz.org/packages/cooking/powertop-1.13.tazpkg
   27.20 +# tazpkg install cpufrequtils-008.tazpkg
   27.21 +# tazpkg install powertop-1.13.tazpkg
   27.22 +</code>
   27.23 +
   27.24 +==== Cpu driver ====
   27.25 +
   27.26 +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:
   27.27 +
   27.28 +<file> $ cat /proc/cpuinfo</file>
   27.29 +
   27.30 +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. 
   27.31 +
   27.32 +Generic ACPI P-States based driver:
   27.33 +<code> # modprobe acpi-cpufreq</code>
   27.34 +AMD mobile K6-2/3+ PowerNow!:
   27.35 +<code> # modprobe powernow-k6</code>
   27.36 +AMD mobile Athlon PowerNow!:
   27.37 +<code> # powernow-k7</code>
   27.38 +AMD Cool&Quiet PowerNow!(up to AMD "K10" CPU):
   27.39 +<code> # modprobe powernow-k8</code>
   27.40 +Intel SpeedStep using the SMI BIOS interface:
   27.41 +<code> # modprobe speedstep-smi</code>
   27.42 +Intel SpeedStep on ICH-based chipsets:
   27.43 +<code> # speedstep-ich</code>
   27.44 +Intel Enhanced SpeedStep (deprecated - use acpi-cpufreq):
   27.45 +<code> # modprobe speedstep-centrino</code>
   27.46 +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):
   27.47 +<code> # modprobe p4-clockmod</code>
   27.48 +NatSemi Geode GX / Cyrix MediaGXm:
   27.49 +<code> # modprobe gx-suspmod</code>
   27.50 +Transmeta Crusoe / Efficeon LongRun:
   27.51 +<code> # modprobe longrun</code>
   27.52 +VIA Cyrix Longhaul:
   27.53 +<code> # /sbin/modprobe longhaul</code>
   27.54 +nForce2 FSB changing cpufreq driver:
   27.55 +<code> # modprobe cpufreq-nforce2</code>
   27.56 +Enhanced PowerSaver driver for VIA C7 CPUs:
   27.57 + <code> # modprobe e_powersaver</code>
   27.58 +
   27.59 +==== Scaling governors ====
   27.60 +
   27.61 +Governors can be thought of as pre-configured power schemes for the CPU. 
   27.62 +
   27.63 +Available governors:
   27.64 +
   27.65 +**cpufreq_performance (default in SliTaz)** \\
   27.66 +The performance governor is built into the kernel and runs the CPU(s) at maximum clock speed 
   27.67 +
   27.68 +**cpufreq_ondemand (also built into the kernel)** \\ 
   27.69 +Dynamically increases/decreases the CPU(s) clock speed based on system load 
   27.70 +
   27.71 +**cpufreq_conservative** \\ 
   27.72 +Similar to ondemand, but more conservative (clock speed changes are more graceful) 
   27.73 +
   27.74 +**cpufreq_powersave** \\ 
   27.75 +Runs the CPU at minimum speed 
   27.76 +
   27.77 +**cpufreq_userspace** \\ 
   27.78 +Manually configured clock speeds by user 
   27.79 +
   27.80 +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). 
   27.81 +
   27.82 +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.
   27.83 +
   27.84 +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.
   27.85 +
   27.86 +==== Select the governor ====
   27.87 +
   27.88 +At this point everything is prepared but no active governor selected - so no power saving yet.
   27.89 +
   27.90 +Use the 'cpufreq-set' command to activate one of the governors - for example:
   27.91 +
   27.92 +<code> # cpufreq-set -g ondemand</code>
   27.93 +
   27.94 +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:
   27.95 +
   27.96 +<code> # cpufreq-set -c 0 -c 1 -g conservative</code>
   27.97 \ No newline at end of file

    28.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    28.2 +++ b/pages/en/guides/cricket-a600.txt	Sat Feb 26 12:17:18 2011 +0000
    28.3 @@ -0,0 +1,111 @@
    28.4 +====== Setting Up The Cricket A600 Broadband Modem ======
    28.5 +
    28.6 +===== Introduction =====
    28.7 +
    28.8 +First thing you need to do is download wvdial and all it's dependencies. It will do that automatically. From terminal as root:
    28.9 +<code> # tazpkg get-install wvdial</code>
   28.10 +
   28.11 +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:
   28.12 +<code> # tazpkg install /path/to/usb_modeswitch-1.0.5.tazpkg</code>
   28.13 +/path/to is where you downloaded it to. So you will need to adjust the above.
   28.14 +
   28.15 +Make a script called flipflop.sh You can place it anywhere but I am going to use where I have it as an example:
   28.16 +///home/tux/scripts///
   28.17 +
   28.18 +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:
   28.19 +<file>
   28.20 +/usr/sbin/usb_modeswitch
   28.21 +sleep 15
   28.22 +usb_modeswitch -v 0x1f28 -p 0x0020 -R 1
   28.23 +</file>
   28.24 +From terminal we need to chmod it so you can use the script: 
   28.25 +<code> # chmod a+x /home/tux/scripts/flipflop.sh</code>
   28.26 +Again if you have it saved somewhere else then adjust accordingly. Sorry to repeat that lol.
   28.27 +
   28.28 +===== wvdial.conf =====
   28.29 +
   28.30 +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:
   28.31 +<code> # leafpad /etc/wvdial.conf</code>
   28.32 +In wvdial.conf we need to make it look like this:
   28.33 +<file>
   28.34 +[Dialer Defaults]
   28.35 +Modem = /dev/ttyACM0
   28.36 +Baud = 460800
   28.37 +Stupid Mode = 1
   28.38 +Auto DNS = 1
   28.39 +Init1 = ATZ
   28.40 +Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
   28.41 +ISDN = 0
   28.42 +Modem Type = USB Modem
   28.43 +Phone = #777
   28.44 +FlowControl = Hardware (CRTSCTS)
   28.45 +Dial Command = ATDT
   28.46 +Username = Your Cricket Number Goes Here.
   28.47 +Password = Cricket
   28.48 +</file>
   28.49 +
   28.50 +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.
   28.51 +
   28.52 +Now again as root in terminal issue this command:
   28.53 +<code> # /home/tux/scripts/flipflop.sh</code>
   28.54 +
   28.55 +You should get something like this below:
   28.56 +<code>
   28.57 +Looking for target devices ...
   28.58 + No devices in target mode or class found
   28.59 +Looking for default devices ...
   28.60 + Found default devices (1)
   28.61 + Found a default device NOT in target class mode
   28.62 +Accessing device 003 on bus 002 ...
   28.63 +Using endpoints 0x08 (out) and 0x87 (in)
   28.64 +Inquiring device details; driver will be detached ...
   28.65 +Looking for active driver ...
   28.66 + OK, driver found ("dummy")
   28.67 + OK, driver "dummy" detached
   28.68 +
   28.69 +Received inquiry data (detailed identification)
   28.70 +-------------------------
   28.71 +  Vendor String: Cricket 
   28.72 +   Model String: T-Flash Disk    
   28.73 +Revision String: 2.31
   28.74 +-------------------------
   28.75 +
   28.76 +Device description data (identification)
   28.77 +-------------------------
   28.78 +Manufacturer: Cal-comp E&CC Limited 
   28.79 +     Product: USB Micro SD Storage
   28.80 +  Serial No.: XXXXXXXXXXXXXXX
   28.81 +-------------------------
   28.82 +Setting up communication with interface 0 ...
   28.83 +Trying to send the message to endpoint 0x08 ...
   28.84 + OK, message successfully sent
   28.85 + Device is gone, skipping any further commands
   28.86 +-> Run lsusb to note any changes. Bye.
   28.87 +
   28.88 +
   28.89 +Looking for target devices ...
   28.90 + No devices in target mode or class found
   28.91 +Looking for default devices ...
   28.92 + No default device found. Is it connected? Bye.
   28.93 +
   28.94 +tux@slitaz:~$
   28.95 +</code>
   28.96 +
   28.97 +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:
   28.98 +<code> # modprobe cdc_acm</code>
   28.99 +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.
  28.100 +
  28.101 +===== rcS.conf =====
  28.102 +
  28.103 +From terminal as root:
  28.104 +<code> # leafpad /etc/rcS.conf</code>
  28.105 +Go down to the following line:
  28.106 +<file>LOAD_MODULES="snd_intel8x0 yenta_socket rtc agpgart intel-agp"</file>
  28.107 +Add this to the line: "cdc_acm" It should now look like this:
  28.108 +<file>LOAD_MODULES="snd_intel8x0 yenta_socket rtc cdc_acm agpgart intel-agp"</file>
  28.109 +Save it and exit.
  28.110 +
  28.111 +We are almost done. From terminal as root again give this command:
  28.112 +<code>  # wvdial</code>
  28.113 +
  28.114 +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 
  28.115 \ No newline at end of file

    29.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    29.2 +++ b/pages/en/guides/dialup.txt	Sat Feb 26 12:17:18 2011 +0000
    29.3 @@ -0,0 +1,150 @@
    29.4 +====== 3G-UMTS =======
    29.5 +
    29.6 +The # sign means that you do this command as root on your console:
    29.7 +
    29.8 +===== Automatic Installation =====
    29.9 +
   29.10 +The new hwsetup in SliTaz 3.0 now adds automatic installation for 3G (still in trial version).
   29.11 +
   29.12 +<code># tazhw setup 3g-modem</code>
   29.13 +
   29.14 +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.
   29.15 +
   29.16 +===== Manual Installation =====
   29.17 +
   29.18 +<code>
   29.19 +# tazpkg get-install wvdial
   29.20 +# tazpkg get-install linux-dialup 
   29.21 +</code>
   29.22 +
   29.23 +You have to bring down your network, otherwise you will have a route problem:
   29.24 +
   29.25 +<code>
   29.26 +# ifconfig eth0 down
   29.27 +# ifconfig eth1 down
   29.28 +</code>
   29.29 +
   29.30 +You have to switch on the modem with:
   29.31 +
   29.32 +<code>
   29.33 +# modprobe option  (Huawei E220, E160g, Venus-VT12)
   29.34 +</code>
   29.35 +
   29.36 +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.
   29.37 +
   29.38 +There is an extra guide for the [[http://doc.slitaz.org/en-guides:cricket-a600|Cricket-a600]]
   29.39 +
   29.40 +For automatization load the module at startup with your Slitaz Control Box.
   29.41 +
   29.42 +===== wvdial.conf =====
   29.43 +
   29.44 +Check the modem if it is /dev/ttyUSB* or /dev/ttyACM* (e.g. with #dmesg) and edit your wvdial.conf (here as an example):
   29.45 +
   29.46 +<code>
   29.47 +# leafpad /etc/wvdial.conf
   29.48 +</code>
   29.49 +
   29.50 +<file>
   29.51 +[Dialer pin]
   29.52 +Modem = /dev/ttyUSB0
   29.53 +Init1 = AT+CPIN=1234...................,.....!!here's your pin!!
   29.54 +
   29.55 +[Dialer umts]
   29.56 +Modem = /dev/ttyUSB0
   29.57 +ISDN = off
   29.58 +Modem Type = USB Modem
   29.59 +Baud = 460800
   29.60 +Init = ATZ
   29.61 +Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
   29.62 +Dial Prefix =
   29.63 +Dial Attempts = 1
   29.64 +Dial Command = ATM1L3DT
   29.65 +Ask Password = off
   29.66 +Auto Reconnect = off
   29.67 +Abort on Busy = off
   29.68 +Carrier Check = on
   29.69 +Check Def Route = on
   29.70 +Abort on No Dialtone = on
   29.71 +Stupid Mode = off
   29.72 +Idle Seconds = 0
   29.73 +Init3 = AT+CGDCONT=1,"IP","drei.at".....!!here's your string!!
   29.74 +Username = drei.at...........................!!here's your Usern!!
   29.75 +Password = drei.at...........................!!here's your Passw!!
   29.76 +Phone = *99#.................................!!here's your Phone!!
   29.77 +</file>
   29.78 +
   29.79 +All the needed data can be found here:
   29.80 +
   29.81 +Austria, Germany,Switzerland: http://linux.frankenberger.at/Huawei_E220_Daten.html
   29.82 +
   29.83 +World:http://www.flexispy.com/Mobile%20APN%20Setting%20to%20use%20GPRS.htm
   29.84 +
   29.85 +But you can search the net with the name of your provider and wvdial.conf and I think you will need to.
   29.86 +
   29.87 +To connect do:
   29.88 +
   29.89 +<code>
   29.90 +# wvdial pin
   29.91 +# wvdial umts
   29.92 +</code>
   29.93 +
   29.94 +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.
   29.95 +
   29.96 +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).
   29.97 +
   29.98 +<code>
   29.99 +# leafpad /etc/resolv.conf
  29.100 +</code>
  29.101 +
  29.102 +<file>
  29.103 +nameserver 213.94.78.16........................!!here's your DNS!!
  29.104 +</file>
  29.105 +
  29.106 +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.
  29.107 +
  29.108 +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!
  29.109 +
  29.110 +<code bash>
  29.111 +#! /bin/bash
  29.112 +ifconfig eth0 down
  29.113 +ifconfig eth1 down
  29.114 +wvdial pin
  29.115 +wvdial umts
  29.116 +</code>
  29.117 +
  29.118 +But dont reconnect with this.
  29.119 +
  29.120 +===== Desktop entry =====
  29.121 +
  29.122 +You can also put a desktop entry in /usr/share/applications with the name umts.desktop 
  29.123 +
  29.124 +<file>
  29.125 +[Desktop Entry]
  29.126 +Encoding=UTF8
  29.127 +Name=UMTS connection
  29.128 +Name[de]=UMTS-Verbindung
  29.129 +Comment=UMTS-Verbindung
  29.130 +Type=Application
  29.131 +Exec=/usr/local/bin/umts-connect
  29.132 +Icon=/usr/share/icons/.................whatever you want
  29.133 +Categories=Application;Network;
  29.134 +</file>
  29.135 +
  29.136 +Please check Exec=/usr/local/bin/umts-connect for permissions.
  29.137 +
  29.138 +Here is the forum post about this: http://forum.slitaz.org/index.php/discussion/comment/440/#Comment_440
  29.139 +
  29.140 +
  29.141 +---- 
  29.142 +\\
  29.143 +^  Page Review Section  ^^ 
  29.144 +|Quality| Good  |
  29.145 +|Review| Minor Updates  |
  29.146 +|Priority| Medium |
  29.147 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
  29.148 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
  29.149 +|How to Improve| Suggest briefly|
  29.150 +|::: |  |
  29.151 +
  29.152 +\\
  29.153 +----
  29.154 \ No newline at end of file

    30.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    30.2 +++ b/pages/en/guides/dvd.txt	Sat Feb 26 12:17:18 2011 +0000
    30.3 @@ -0,0 +1,79 @@
    30.4 +====== All Slitaz resources on one DVD ======
    30.5 +
    30.6 +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:
    30.7 +
    30.8 +    * a Slitaz boot
    30.9 +    * a copy of the website
   30.10 +    * a snapshot of the wok
   30.11 +    * all official packages
   30.12 +
   30.13 +It is designed to be used without an internet connection.
   30.14 +
   30.15 +===== Hybrid ISO =====
   30.16 +
   30.17 +The ISO image should be burned onto a DVD using:
   30.18 +<code>
   30.19 +# wodim -v dev=/dev/dvd packages-cooking.iso
   30.20 +</code>
   30.21 +It can also be written onto a USB key (say the key is /dev/usbkey). USE WITH CAUTION this will erase all your data.
   30.22 +<code>
   30.23 +# dd if=packages-cooking.iso of=/dev/usbkey
   30.24 +</code>
   30.25 +After writing the USB key, you can create partitions to get back the remaining storage.
   30.26 +<code>
   30.27 +# fdisk /dev/usbkey
   30.28 +</code>
   30.29 +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.
   30.30 +
   30.31 +===== Burnable on CDROM =====
   30.32 +
   30.33 +The files on the ISO image are ordered in 5 groups:
   30.34 +
   30.35 +    - the boot files
   30.36 +    - the loram boot files
   30.37 +    - the website
   30.38 +    - the wok
   30.39 +    - the packages
   30.40 +
   30.41 +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)
   30.42 +<code>
   30.43 +# wodim -v dev=/dev/cdrom packages-cooking.iso
   30.44 +</code>
   30.45 +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.
   30.46 +
   30.47 +===== Dual boot =====
   30.48 +
   30.49 +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:
   30.50 +<code>
   30.51 +boot: loram screen=1280x1024
   30.52 +</code>
   30.53 +With core boot you can:
   30.54 +
   30.55 +    * unmount the DVD (umount /cdrom)
   30.56 +    * test (install) packages in RAM
   30.57 +
   30.58 +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.
   30.59 +
   30.60 +===== Auto install =====
   30.61 +
   30.62 +During boot the following is performed:
   30.63 +
   30.64 +    * the DVD is mounted in /cdrom, the wok is onto /home/slitaz/wok
   30.65 +    * a pseudo tazpkg recharge links packages from the DVD
   30.66 +    * the slitaz web site is installed in file:///cdrom/website/index.html//
   30.67 +
   30.68 +Note: USB key users should read USB key instead of DVD
   30.69 +
   30.70 +---- 
   30.71 +\\
   30.72 +^  Page Review Section  ^^ 
   30.73 +|Quality| Good  |
   30.74 +|Review| Minor Updates  |
   30.75 +|Priority| Medium |
   30.76 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
   30.77 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
   30.78 +|How to Improve| Suggest briefly|
   30.79 +|::: |  |
   30.80 +
   30.81 +\\
   30.82 +----
   30.83 \ No newline at end of file

    31.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    31.2 +++ b/pages/en/guides/faq-dependency.txt	Sat Feb 26 12:17:18 2011 +0000
    31.3 @@ -0,0 +1,29 @@
    31.4 +
    31.5 +====== An Application Cannot Find Libraries/Files ======
    31.6 +
    31.7 +===== Symptoms =====
    31.8 +
    31.9 +  *  When run in a Terminal, an application fails with the message:
   31.10 +<code> [name]: error while loading shared libraries: [library].so.*: cannot open shared object file: No such file or directory</code>
   31.11 +
   31.12 +===== Explanation =====
   31.13 +
   31.14 +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.
   31.15 +
   31.16 +===== Solution =====
   31.17 +
   31.18 +Check if the file required is available in another package. Use the package manager (TazPkg) to search for the file:
   31.19 +  * start the package manager
   31.20 +  * 'Recharge' the package lists, if necessary 
   31.21 +  * click the "Search" tab 
   31.22 +  * in the //Search// box, enter the file-name ([library].so) and click "Files"
   31.23 +  * install the package (pick that with the closest name if there is more than one) by double-clicking the entry and clicking //Install Package//
   31.24 +
   31.25 +Alternatively, run the following command from a terminal:
   31.26 +<code>tazpkg search-pkgname library.so</code>
   31.27 +
   31.28 +
   31.29 +... and install the appropriate package with:
   31.30 +<code> tazpkg get-install [package] </code>
   31.31 +
   31.32 +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.

    32.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    32.2 +++ b/pages/en/guides/faq-login.txt	Sat Feb 26 12:17:18 2011 +0000
    32.3 @@ -0,0 +1,37 @@
    32.4 +====== Cannot Login to Desktop ======
    32.5 +
    32.6 +===== Symptoms =====
    32.7 +
    32.8 +  * Slim, the SliTaz Login Manager, fails with the message:
    32.9 +<code> failed to execute login command </code>
   32.10 +
   32.11 +===== Explanation =====
   32.12 +
   32.13 +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:
   32.14 +  * .Xdefaults
   32.15 +  * .xinitrc
   32.16 +  * something else?
   32.17 +
   32.18 +===== Solution =====
   32.19 +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.
   32.20 +
   32.21 +Switch to the root (super) user:
   32.22 +<code> su root </code>
   32.23 +Change to the affected users /home directory:
   32.24 +<code> cd /home/USERNAME </code>
   32.25 +Set the shell options to allow the dot (.) to be included in file names:
   32.26 +<code> shopt -s dotglob </code>
   32.27 +Copy all files, recursively:
   32.28 +<code> cp -r /etc/skel/* /home/USERNAME </code>
   32.29 +Change ownership of all files and directories in the user's home to that of the affected user:
   32.30 +<code> chown -R USERNAME:USERGROUP /home/USERNAME/* </code>
   32.31 +Restore the shell options:
   32.32 +<code> shopt -u dotglob </code>
   32.33 +The essential files should now be restored!
   32.34 +
   32.35 +EDIT:
   32.36 +
   32.37 +<code> shopt -u dotglob </code>
   32.38 +is not working in slitaz-3.0.iso - instead of this run in addition:
   32.39 +<code> chown -R USERNAME:USERGROUP /home/USERNAME/.[a-zA-Z0-9]*</code>
   32.40 +----
   32.41 \ No newline at end of file

    33.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    33.2 +++ b/pages/en/guides/faq-pkgconv.txt	Sat Feb 26 12:17:18 2011 +0000
    33.3 @@ -0,0 +1,21 @@
    33.4 +====== Packages from Other Distributions ======
    33.5 +
    33.6 +===== Symptoms =====
    33.7 +
    33.8 +  * There is a useful package that is not yet available in the SliTaz repositories.
    33.9 +  * Can I use packages from other distributions on my SliTaz installation?
   33.10 +
   33.11 +===== Explanation =====
   33.12 +
   33.13 +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.
   33.14 +
   33.15 +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.
   33.16 +
   33.17 +===== Solution =====
   33.18 +
   33.19 +Simply run the following command in a Terminal:
   33.20 +''tazpkg convert //filename//''
   33.21 +
   33.22 +The converted Tazpkg will be created after auto-detection of the original format.
   33.23 +
   33.24 +<note important>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.</note>
   33.25 \ No newline at end of file

    34.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    34.2 +++ b/pages/en/guides/faq-programfailstorun.txt	Sat Feb 26 12:17:18 2011 +0000
    34.3 @@ -0,0 +1,17 @@
    34.4 +====== A Program Doesn't Run or Quits Unexpectedly ======
    34.5 +
    34.6 +===== Symptoms =====
    34.7 +
    34.8 +  * Nothing happens when an application is run from the Launch menu.
    34.9 +  * An application quits without warning.
   34.10 +
   34.11 +===== Explanation =====
   34.12 +
   34.13 +One or more of problems may have caused this. Run the program in a Terminal to see any error messages the program may deliver.
   34.14 +
   34.15 +===== Solution =====
   34.16 +
   34.17 +Launch a Terminal (command line) and run the application by typing in its name. See the following FAQs on solving common problems.
   34.18 +
   34.19 +
   34.20 +----
   34.21 \ No newline at end of file

    35.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    35.2 +++ b/pages/en/guides/faq-terminal.txt	Sat Feb 26 12:17:18 2011 +0000
    35.3 @@ -0,0 +1,27 @@
    35.4 +====== Overview ======
    35.5 +
    35.6 +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.
    35.7 +
    35.8 +<note tip>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''.</note>
    35.9 +
   35.10 +\\
   35.11 +----
   35.12 +====== XTerm ======
   35.13 +
   35.14 +===== Cannot Copy/Paste =====
   35.15 +
   35.16 +=== Symptoms ===
   35.17 +  * I cannot find the copy/paste feature
   35.18 +  * Right-click for a menu does not work as expected
   35.19 + 
   35.20 +=== Explanation ===
   35.21 +
   35.22 +XTerm does not have a right-click menu -- or any other menu for that matter -- but selection is activated by using the mouse buttons.
   35.23 +
   35.24 +=== Solution ===
   35.25 +
   35.26 +Selection, copy and paste is achievable using the mouse buttons. The three mouse buttons works thus:
   35.27 +
   35.28 +  * //left click// defines where the selection begins
   35.29 +  * //middle click// defines where the selection ends & copies it to clipboard 
   35.30 +  * //right click// pastes the clipboard contents to the current cursor, not mouse, position
   35.31 \ No newline at end of file

    36.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    36.2 +++ b/pages/en/guides/faq.txt	Sat Feb 26 12:17:18 2011 +0000
    36.3 @@ -0,0 +1,68 @@
    36.4 +====== Frequently Asked Questions ======
    36.5 +
    36.6 +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.
    36.7 +
    36.8 +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.
    36.9 +
   36.10 +\\
   36.11 +===== General  =====
   36.12 +  * [[faq-login|Log-In Problems]]
   36.13 +  * [[faq-terminal|Terminals (Copy/Paste etc.)]]
   36.14 +
   36.15 +\\
   36.16 +
   36.17 +===== Package or Software  =====
   36.18 +  * [[faq-dependency| An Application Cannot Find Libraries/Files ]]
   36.19 +  * [[faq-programfailstorun | A Program Doesn't Run or Quits Unexpectedly ]]
   36.20 +  * [[faq-pkgconv | Can I install a package on SliTaz from another distribution? ]] 
   36.21 +
   36.22 +\\
   36.23 +
   36.24 +===== Hardware  =====
   36.25 +  * ...
   36.26 +
   36.27 +\\
   36.28 +
   36.29 +===== Questions Still Unanswered? =====
   36.30 +
   36.31 +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]]!
   36.32 +
   36.33 +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.
   36.34 +
   36.35 +** Your first post should include the following things: **
   36.36 +
   36.37 +  * detailed information about your hardware
   36.38 +    *  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:
   36.39 + 
   36.40 +<code>
   36.41 +echo '=== PCI Devices: ===' >> SysInfo.txt && lspci >> SysInfo.txt && echo '=== USB Devices: ===' \ 
   36.42 +>> SysInfo.txt && lsusb >> SysInfo.txt && echo '=== Kernel Modules: ===' >> SysInfo.txt && lsmod >> SysInfo.txt
   36.43 +</code>
   36.44 +
   36.45 +  * precise information about your SliTaz installation:
   36.46 +    *  which version to you have? Stable or Cooking?
   36.47 +    *  are you using the standard ISO or a specific flavor (XVESA, Lo-RAM etc.)?
   36.48 +    *  is it installed on a HD or on an USB stick?
   36.49 +    *  do you know which file-system you used?
   36.50 +
   36.51 +  * identify when your problem appeared:
   36.52 +    *  was it just after installation or after an update?
   36.53 +    *  were there any changes to your normal usage pattern or configuration?
   36.54 +
   36.55 +This should provide enough system information for help to be provided.
   36.56 +
   36.57 +
   36.58 +---- 
   36.59 +\\
   36.60 +^  Page Review Section  ^^ 
   36.61 +|Quality| Low  |
   36.62 +|Review| Major Updates FIXME  |
   36.63 +|Priority| High |
   36.64 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
   36.65 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
   36.66 +|How to Improve| Suggest briefly, e.g.,|
   36.67 +|::: | [[en:guides:start | Add link]]|
   36.68 +|::: | Add new rows like this ;-)  |
   36.69 +
   36.70 +\\
   36.71 +----
   36.72 \ No newline at end of file

    37.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    37.2 +++ b/pages/en/guides/flash.txt	Sat Feb 26 12:17:18 2011 +0000
    37.3 @@ -0,0 +1,35 @@
    37.4 +====== How-To install Adobe Flash Player ======
    37.5 +
    37.6 +Open a terminal. Become super-user:
    37.7 +<code> $ su -
    37.8 +</code>
    37.9 +The default password for the root account is **//root//** .
   37.10 +
   37.11 +Type the following as one command:
   37.12 +
   37.13 +<code> # tazpkg get-install get-flash-plugin && get-flash-plugin
   37.14 +</code>
   37.15 +
   37.16 +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.
   37.17 +
   37.18 +By using this method the Flash plugin can be managed through tazpkg; it will update itself as the repo package is updated.
   37.19 +
   37.20 +When you install Flash to SliTaz 3.0 and Midori is not recognizing the plugin - just reinstall Midori with
   37.21 +<code> # tazpkg get-install midori --forced</code> Thats it.
   37.22 +
   37.23 +
   37.24 +// This was successfully tested in Midori, Firefox/Shiretoko & Opera, on Cooking 2010-03-14 (the v3 RC). //
   37.25 +
   37.26 +---- 
   37.27 +\\
   37.28 +^  Page Review Section  ^^ 
   37.29 +|Quality| Good  |
   37.30 +|Review| Minor Updates  |
   37.31 +|Priority| Medium |
   37.32 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
   37.33 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
   37.34 +|How to Improve| Suggest briefly|
   37.35 +|::: |  |
   37.36 +
   37.37 +\\
   37.38 +----
   37.39 \ No newline at end of file

    38.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    38.2 +++ b/pages/en/guides/frugal.txt	Sat Feb 26 12:17:18 2011 +0000
    38.3 @@ -0,0 +1,123 @@
    38.4 +====== Winboot ======
    38.5 +
    38.6 +===== Frugal install to Microsoft Windows partition =====
    38.7 +
    38.8 +Install [[http://grub4dos.sourceforge.net/wiki/index.php/Grub4dos_tutorial#Installation|Grub4dos]].
    38.9 +
   38.10 +This article will assume that your C: drive is //(hd0,0)//.
   38.11 +You need at least 160MB to run Slitaz cooking (128MB for Slitaz 1.0).
   38.12 +
   38.13 +Tested with Windows XP on FAT32 and on NTFS.
   38.14 +
   38.15 +For Windows XP, 2000 or NT, copy http://mirror.slitaz.org/boot/grldr
   38.16 +into C:\ and append to C:\boot.ini:
   38.17 +
   38.18 +<file>C:\grldr="Grub4DOS"</file>
   38.19 +
   38.20 +===== Traditional frugal install =====
   38.21 +
   38.22 +Copy http://download.tuxfamily.org/slitaz/boot/cooking/bzImage and
   38.23 +http://download.tuxfamily.org/slitaz/boot/cooking/rootfs.gz (both <30MB)
   38.24 +into C:\boot and append to C:\menu.lst the following text:
   38.25 +
   38.26 +<file>
   38.27 +title SliTaz cooking
   38.28 +  kernel (hd0,0)/boot/bzImage rw root=/dev/null vga=normal
   38.29 +  initrd (hd0,0)/boot/rootfs.gz
   38.30 +</file>
   38.31 +Works fine with Windows XP on FAT32 and on NTFS.
   38.32 +
   38.33 +===== ISO image install =====
   38.34 +
   38.35 +Copy http://download.tuxfamily.org/slitaz/iso/cooking/slitaz-cooking.iso (<30MB)
   38.36 +into C:\boot. Run defragmentation on C:. And append to C:\menu.lst the following text:
   38.37 +
   38.38 +<file>
   38.39 +title SliTaz cooking
   38.40 +  map (hd0,0)/boot/slitaz-cooking.iso (hd1)
   38.41 +  map --hook
   38.42 +  kernel (hd1)/boot/bzImage rw root=/dev/null vga=normal
   38.43 +  initrd (hd1)/boot/rootfs.gz
   38.44 +</file>
   38.45 +
   38.46 +Works fine with Windows XP on FAT32 and on NTFS. Using version 0.4.3.
   38.47 +The file C:\boot\slitaz-cooking.iso MUST be defragmented.
   38.48 +
   38.49 +You need 160MB or 256MB of RAM to run the slitaz-cooking.iso.
   38.50 +If you have less RAM try:
   38.51 +http://mirror.slitaz.org/iso/cooking/flavors/slitaz-cooking-base.iso or
   38.52 +http://mirror.slitaz.org/iso/cooking/flavors/slitaz-cooking-justX.iso or
   38.53 +http://mirror.slitaz.org/iso/cooking/flavors/slitaz-loram.iso instead:
   38.54 +
   38.55 +<file>
   38.56 +title SliTaz cooking base
   38.57 +  map (hd0,0)/boot/slitaz-cooking-base.iso (hd1)
   38.58 +  map --hook
   38.59 +  kernel (hd1)/boot/bzImage rw root=/dev/null vga=normal
   38.60 +  initrd (hd1)/boot/rootfs.gz
   38.61 +</file>
   38.62 +See http://community.slitaz.org/wiki/Loram
   38.63 +
   38.64 +===== Web boot install =====
   38.65 +
   38.66 +Copy http://download.tuxfamily.org/slitaz/boot/gpxe (<200KB)
   38.67 +into C:\boot and append to C:\menu.lst the following text:
   38.68 +
   38.69 +<file>
   38.70 +title SliTaz web
   38.71 +  kernel (hd0,0)/boot/gpxe
   38.72 +</file>
   38.73 +
   38.74 +Gpxe is provided by the SliTaz Live CD too:
   38.75 +<file>
   38.76 +title SliTaz web
   38.77 +  map (hd0,0)/boot/slitaz-cooking.iso (hd1)
   38.78 +  map --hook
   38.79 +  kernel (hd1)/boot/gpxe
   38.80 +</file>
   38.81 +This will boot the latest available version of SliTaz. See http://boot.slitaz.org/.
   38.82 +Works fine with Windows XP on FAT32 and on NTFS.
   38.83 +
   38.84 +===== Tuning the boot process =====
   38.85 +
   38.86 +Additional boot parameters may be appended. For example:
   38.87 +
   38.88 +<file>
   38.89 +title SliTaz cooking
   38.90 +  map (hd0,0)/boot/slitaz-cooking.iso (hd1)
   38.91 +  map --hook
   38.92 +  kernel (hd1)/boot/bzImage rw root=/dev/null vga=extended lang=fr_FR kmap=fr-latin1 laptop autologin config=/dev/hda1,boot/slitaz.sh
   38.93 +  initrd (hd1)/boot/rootfs.gz
   38.94 +</file>
   38.95 +
   38.96 +The file // /boot/slitaz.sh // in // /dev/hda1 // will be executed at the end of the boot script:
   38.97 +
   38.98 +<file>
   38.99 +  initrd (hd1)/boot/rootfs.gz (hd0,0)/boot/extra-softwares.gz (hd0,0)/boot/my-config-files.gz
  38.100 +</file>
  38.101 +
  38.102 +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.
  38.103 +
  38.104 +===== Automated Graphical Approach using UNetbootin =====
  38.105 +
  38.106 +A SliTaz Frugal Install or a Live USB installation can be performed using [[http://unetbootin.sourceforge.net/|UNetbootin]].
  38.107 +
  38.108 +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
  38.109 +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.
  38.110 +
  38.111 +To perform a Frugal Install, select “Hard Disk” under installation type;
  38.112 +to create a Live USB, select “USB Drive” under installation type.
  38.113 +
  38.114 +---- 
  38.115 +\\
  38.116 +^  Page Review Section  ^^ 
  38.117 +|Quality| Good  |
  38.118 +|Review| Minor Updates  |
  38.119 +|Priority| Medium |
  38.120 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
  38.121 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
  38.122 +|How to Improve| Suggest briefly|
  38.123 +|::: | Add new rows like this ;-)  |
  38.124 +
  38.125 +\\
  38.126 +----
  38.127 \ No newline at end of file

    39.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    39.2 +++ b/pages/en/guides/kernel.txt	Sat Feb 26 12:17:18 2011 +0000
    39.3 @@ -0,0 +1,86 @@
    39.4 +====== Build your own custom Linux Kernel for SliTaz ======
    39.5 +
    39.6 +===== Prepare your system =====
    39.7 +
    39.8 +
    39.9 +    * Install the slitaz-toolchain meta package. This package contains the required base files.
   39.10 +        * binutils
   39.11 +        * linux-headers
   39.12 +        * glibc-dev
   39.13 +        * gcc
   39.14 +        * make
   39.15 +
   39.16 +<code>
   39.17 +# tazpkg get-install slitaz-toolchain
   39.18 +</code>
   39.19 +
   39.20 +    * Install the packages required to configure and compile the kernel sources.
   39.21 +        * ncurses-dev
   39.22 +        * perl
   39.23 +
   39.24 +<code>
   39.25 +# tazpkg get-install ncurses-dev
   39.26 +# tazpkg get-install perl
   39.27 +</code>
   39.28 +
   39.29 +    * SliTaz provides a linux-source package. The kernel source tree will be downloaded from the mirror, installed to the /usr/src/linux-<VERSION> directory, and patched for SliTaz..
   39.30 +
   39.31 +<code>
   39.32 +# tazpkg get-install linux-source
   39.33 +# /usr/bin/get-linux-source
   39.34 +# ls -l /usr/src
   39.35 +lrwxrwxrwx    1 root     root           21 Jul 21 21:27 linux -> linux-2.6.25.5-slitaz
   39.36 +drwxrwxr-x   23 root     root         4096 Jul 21 22:41 linux-2.6.25.5-slitaz
   39.37 +-rw-r--r--    1 root     root     48589640 Jul 21 21:28 linux-2.6.25.5.tar.bz2
   39.38 +</code>
   39.39 +
   39.40 +===== Configure and Compile =====
   39.41 +
   39.42 +The Linux kernel source tree is now ready to configure and compile.
   39.43 +
   39.44 +    * Go to the directory that contains the kernel source tree.
   39.45 +<code>
   39.46 +# cd /usr/src/linux
   39.47 +</code>
   39.48 +
   39.49 +    * Prepare the build from the default configuration.
   39.50 +<code>
   39.51 +# make oldconfig && make prepare
   39.52 +</code>
   39.53 +
   39.54 +     * Modify the kernel configuration to your needs, and compile.
   39.55 +     * 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.
   39.56 +<code>
   39.57 +# make menuconfig
   39.58 +# make
   39.59 +# make modules 
   39.60 +# make modules_install
   39.61 +# cp arch/x86/boot/bzImage /boot
   39.62 +</code>
   39.63 +
   39.64 +    * Configure the boot-loader (optional)
   39.65 +<code>
   39.66 +# leafpad /boot/grub/menu.lst
   39.67 +</code>
   39.68 +
   39.69 +    * Add the new kernel to the list
   39.70 +<file>
   39.71 +# My kernel:
   39.72 +title 	SliTaz GNU/Linux (cooking) (Kernel <VERSION>)
   39.73 +		root (hd0,1)
   39.74 +		kernel /boot/bzImage root=/dev/sda2
   39.75 +</file>
   39.76 +
   39.77 +---- 
   39.78 +\\
   39.79 +^  Page Review Section  ^^ 
   39.80 +|Quality| Medium  |
   39.81 +|Review| Minor/Major Updates  |
   39.82 +|Priority| Medium |
   39.83 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
   39.84 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
   39.85 +|How to Improve| Add "tazwok cook linux"|
   39.86 +|::: |  |
   39.87 +
   39.88 +\\
   39.89 +----
   39.90 \ No newline at end of file

    40.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    40.2 +++ b/pages/en/guides/liveusb.txt	Sat Feb 26 12:17:18 2011 +0000
    40.3 @@ -0,0 +1,42 @@
    40.4 +====== LiveUSB ======
    40.5 +
    40.6 +===== From SliTaz =====
    40.7 +
    40.8 +Download > Burn > Boot a SliTaz ISO image. Open Terminal > type in (change ///dev/sda// if needed):
    40.9 +
   40.10 +<code>
   40.11 +$ su root
   40.12 +# tazusb format
   40.13 +</code>
   40.14 +Enter a name such as /dev/sda1 or type 'list'... wait ...
   40.15 +<code>
   40.16 +# tazusb gen-liveusb /dev/sda1
   40.17 +</code>
   40.18 +
   40.19 +Wait…. and then reboot!
   40.20 +
   40.21 +===== From Windows =====
   40.22 +
   40.23 +A SliTaz Live USB installation or a Frugal Install  can be performed using [[http://unetbootin.sourceforge.net/|UNetbootin]].
   40.24 +
   40.25 +You may either choose: 
   40.26 +  * 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 
   40.27 +  * a custom SliTaz version ([[http://unetbootin.sourceforge.net/unetbootin-windows-latest.exe|Windows]] | [[http://unetbootin.sourceforge.net/unetbootin-linux-latest|Linux]]).
   40.28 +
   40.29 +To create a Live USB, select “USB Drive” under installation type.
   40.30 +
   40.31 +You can also choose to do frugal install. To perform a Frugal Install, select “Hard Disk” under installation type;
   40.32 +
   40.33 +---- 
   40.34 +\\
   40.35 +^  Page Review Section  ^^ 
   40.36 +|Quality| Good  |
   40.37 +|Review| Minor Updates  |
   40.38 +|Priority| Medium |
   40.39 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
   40.40 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
   40.41 +|How to Improve| Add tazusb.exe, a SliTaz alternative to unetbootin |
   40.42 +|::: |   |
   40.43 +
   40.44 +\\
   40.45 +----
   40.46 \ No newline at end of file

    41.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    41.2 +++ b/pages/en/guides/lowramcd.txt	Sat Feb 26 12:17:18 2011 +0000
    41.3 @@ -0,0 +1,143 @@
    41.4 +====== Live CD for Low-RAM Systems ======
    41.5 +
    41.6 +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.
    41.7 +
    41.8 +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.
    41.9 +
   41.10 +    * //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
   41.11 +    * //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
   41.12 +    * //slitaz-loram-cdrom// will move the ///usr// tree onto the cdrom
   41.13 +
   41.14 +///usr// will be read-only. If the package //funionfs// or //aufs// is installed you will have read-write access to ///usr//.
   41.15 +
   41.16 +These packages patch ///etc/init.d/rcS// to mount ///usr// and install two scripts in ///etc/tazlito//:
   41.17 +
   41.18 +    * //loram.rootfs// is called by //tazlito gen-distro// to compress or move ///usr//
   41.19 +    * //loram.extract// is called by the //slitaz-installer// to uncompress or move ///usr// and install the same distribution as the SliTaz core LiveCD
   41.20 +
   41.21 +Let's build a //slitaz-loram-cdrom.iso// !
   41.22 +
   41.23 +===== slitaz-loram-cdrom =====
   41.24 +
   41.25 +We boot the LiveCD and install the slitaz-loram-cdrom package:
   41.26 +
   41.27 +<code> # tazpkg get-install slitaz-loram-cdrom </code>
   41.28 +
   41.29 +//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.
   41.30 +
   41.31 +<code> # rm -f /etc/tazlito/distro-packages.list ./distro-packages.list </code>
   41.32 +
   41.33 +Now we can build the iso image…
   41.34 +
   41.35 +<code> # tazlito gen-distro </code>
   41.36 +
   41.37 +…and burn it.
   41.38 +
   41.39 +<code># wodim dev=1,0,0 /home/slitaz/distro/slitaz-hacked.iso </code>
   41.40 +
   41.41 +===== Variations of slitaz-loram & slitaz-loram-cdrom =====
   41.42 +
   41.43 +//slitaz-loram// compresses ///usr// with //cromfs// by default, which gives a higher compression ratio but is very slow. You can use //squashfs// instead:
   41.44 +
   41.45 +    * refuse to install cromfs during the slitaz-loram installation
   41.46 +
   41.47 +<code> # yes n | tazpkg get-install slitaz-loram </code>
   41.48 +
   41.49 +    * install squashfs with its dependencies
   41.50 +
   41.51 +<code> # yes y | tazpkg get-install squashfs </code>
   41.52 +
   41.53 +//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.
   41.54 +
   41.55 +===== Let's build a slitaz-loram-cdrom-sqfs.iso!=====
   41.56 +
   41.57 +Install the package //slitaz-loram-cdrom// and //squashfs// (sqfs) on the host system:
   41.58 +
   41.59 +<code>
   41.60 + # tazpkg get-install slitaz-loram-cdrom
   41.61 + # yes y | tazpkg get-install squashfs
   41.62 +</code>
   41.63 +
   41.64 +Now we repeat the latter points of the above process:
   41.65 +<code>
   41.66 + # rm -f /etc/tazlito/distro-packages.list ./distro-packages.list
   41.67 + # tazlito gen-distro
   41.68 + # wodim dev=1,0,0 /home/slitaz/distro/slitaz-hacked.iso
   41.69 +</code>
   41.70 +
   41.71 +===== slitaz-loram-cdrom and Large Memory Systems =====
   41.72 +
   41.73 +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:
   41.74 +
   41.75 +    * a slitaz LiveCD (/usr was not compressed on the cdrom)
   41.76 +    * a slitaz-loram LiveCD (/usr was compressed on the cdrom by squashfs or cromfs)
   41.77 +
   41.78 +===== slitaz-loram-cdrom and Tiny Memory Systems =====
   41.79 +
   41.80 +The boot command line is usually:
   41.81 +
   41.82 +<code> boot: slitaz args... </code>
   41.83 +
   41.84 +Slitaz boots on a 9MB RAM system with the boot command:
   41.85 +
   41.86 +<code> boot: loram single root=/dev/hdc </code>
   41.87 +
   41.88 +Where ///dev/hdc// is the CD-ROM device, the loram boot entry avoids RAM disk creation and CD-ROM detection.
   41.89 +
   41.90 +<note tip>Note that on a system with such a low amount of memory, the first thing to do is add swap!</note>
   41.91 +
   41.92 +You need 10MB to use the boot scripts with:
   41.93 +
   41.94 +<code> boot: loram root=/dev/hdc </code>
   41.95 +
   41.96 +In this case you can add arguments like kmap=, config=, etc.
   41.97 +
   41.98 +===== slitaz-loram Auto-Extraction =====
   41.99 +
  41.100 +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.
  41.101 +
  41.102 +For example, assuming you boot the slitaz-loram-cdrom-sqfs:
  41.103 +
  41.104 +<code> boot: slitaz extract-loram </code>
  41.105 +
  41.106 +You will get:
  41.107 +
  41.108 +    * /usr read-only squashfs on a CD-ROM with a smaller RAM size
  41.109 +    * /usr read-only squashfs in RAM with a medium RAM size (like slitaz-loram)
  41.110 +    * /usr read-write tmpfs in RAM with a larger RAM size (like slitaz-core)
  41.111 +
  41.112 +===== Build a slitaz-loram with tazlitobox =====
  41.113 +
  41.114 +Since SliTaz 3.0, you can now build a slitaz-loram LiveCD more easily:
  41.115 +    * launch tazlitobox
  41.116 +    * click on the Low RAM tab
  41.117 +    * select //The filesystem is always in RAM// (for slitaz-loram) or //The filesystem may be on a CDROM// (for slitaz-loram-cdrom)
  41.118 +    * fill the ISO input with your Slitaz flavor (3.0 or more recent)
  41.119 +    * update the ISO output
  41.120 +    * click //build ISO//
  41.121 +
  41.122 +The filesystem root (/) is compressed (not /usr only) and mounted read-write thanks to the aufs package.
  41.123 +The //mount// and //df// commands will show a strange output, handy to detect that this kind of loram is running.
  41.124 +
  41.125 +You can also use the following command in text mode:
  41.126 +<code> # tazlito build-loram original.iso loram.iso</code>
  41.127 +or:
  41.128 +<code> # tazlito build-loram original.iso loram-cdrom.iso cdrom</code>
  41.129 +
  41.130 +Meta flavors are supported; you can loramize a slitaz-3in1.iso !
  41.131 +
  41.132 +===== And what to do with only 8MB RAM? =====
  41.133 +Try Tiny Slitaz : http://pizza.slitaz.org/tiny/ !
  41.134 +---- 
  41.135 +\\
  41.136 +^  Page Review Section  ^^ 
  41.137 +|Quality| Good  |
  41.138 +|Review| Minor Updates  |
  41.139 +|Priority| Medium |
  41.140 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
  41.141 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
  41.142 +|How to Improve|Needs a review by developers|
  41.143 +|::: | Add new rows like this ;-)  |
  41.144 +
  41.145 +\\
  41.146 +----
  41.147 \ No newline at end of file

    42.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    42.2 +++ b/pages/en/guides/manyinone.txt	Sat Feb 26 12:17:18 2011 +0000
    42.3 @@ -0,0 +1,48 @@
    42.4 +======= Create many-in-1 flavors =======
    42.5 +
    42.6 +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:
    42.7 +
    42.8 +    * define a flavor list (or an ISO list) where each flavor is nested in the previous one (like russian dolls),
    42.9 +    * define the minimum RAM quantity necessary for each flavor.
   42.10 +
   42.11 +The many-in-1 ISO may be a little bit larger than the largest
   42.12 +flavor. Sometimes the sizes are identical.
   42.13 +
   42.14 +We will build the official slitaz-3in1 flavor which boots:
   42.15 +
   42.16 +    * the core flavor with 160MB or more
   42.17 +    * the justx flavor with 96MB to 160MB
   42.18 +    * the base flavor with 32MB to 96MB
   42.19 +    * and displays an error message with less than 32MB...
   42.20 +
   42.21 +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).
   42.22 +
   42.23 +===== The best way: create a flavor =====
   42.24 +
   42.25 +A flavor holds all the necessary information to build a LiveCD.
   42.26 +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.
   42.27 +
   42.28 +[[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.
   42.29 +
   42.30 +A meta flavor has no rootfs, rootcd or packages.list.
   42.31 +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.
   42.32 +
   42.33 +<code>
   42.34 +ROOTFS_SELECTION="160M core 96M justx 32M base"
   42.35 +</code>
   42.36 +
   42.37 +The rootfs and the rootcd are taken from the largest flavor.
   42.38 +
   42.39 +===== The easy way: using tazlitobox =====
   42.40 +
   42.41 +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**.
   42.42 +
   42.43 +===== The cmdline way: using tazlito =====
   42.44 +
   42.45 +Usage: tazlito merge size1 iso size2 rootfs2 [sizeN rootfsN]...
   42.46 +
   42.47 +The largest flavor is given as an ISO file to get the additional rootcd files and will get the resulting ISO.
   42.48 +
   42.49 +<code>
   42.50 +tazlito merge 160M slitaz-core.iso 96M rootfs-justx.gz 32M rootfs-base.gz
   42.51 +</code>
   42.52 \ No newline at end of file

    43.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    43.2 +++ b/pages/en/guides/midori.txt	Sat Feb 26 12:17:18 2011 +0000
    43.3 @@ -0,0 +1,126 @@
    43.4 +====== Midori Tips & Tweaks ======
    43.5 +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]]
    43.6 +
    43.7 +
    43.8 +
    43.9 +Things that I will cover:
   43.10 +<code>
   43.11 +Ad Blocking
   43.12 +Custom Search Engines
   43.13 +Flash Blocking
   43.14 +UserScripts
   43.15 +Shortcuts
   43.16 +</code>
   43.17 +
   43.18 +===== Enabling Extensions =====
   43.19 +
   43.20 +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.
   43.21 +
   43.22 +===== Ad Blocking =====
   43.23 +In extensions enable: Advertisement blocker
   43.24 +
   43.25 +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:
   43.26 +
   43.27 +{{http://img541.yfrog.com/img541/4508/beforeadded.png}}
   43.28 +
   43.29 +From the picture you can see that adding a ruleset is pretty self explanatory. As an example click on Add, then insert this url: <code>http://easylist-downloads.adblockplus.org/easyprivacy.txt</code> 
   43.30 +
   43.31 +
   43.32 +{{http://img541.yfrog.com/img541/2485/added.png}}
   43.33 +
   43.34 +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.
   43.35 +===== Managing Search Engines ===== 
   43.36 +No extension needs to be enabled for this feature.
   43.37 +
   43.38 +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:
   43.39 +
   43.40 +{{http://img541.yfrog.com/img541/7471/manage.png}}
   43.41 +
   43.42 +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:
   43.43 +
   43.44 +{{http://img542.yfrog.com/img542/4866/yahoo.png}}
   43.45 +
   43.46 +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.
   43.47 +
   43.48 +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.
   43.49 +
   43.50 +For all you twitter users or people that like shortened urls. Add this to custom searches: 
   43.51 +<code>http://is.gd/create.php?longurl=</code>
   43.52 +{{http://img260.yfrog.com/img260/7176/isgd.png}}
   43.53 +
   43.54 +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]]
   43.55 +Result:[[http://img30.yfrog.com/img30/6563/shortened.png|Shortened URL]]
   43.56 +
   43.57 +For those who hate using the mouse like me and want to shorten url's you can do the same thing above like this: <code>Ctrl-L, Left Arrow key, type u, spacebar, then enter</code> If you have javascript enabled then the shortened url should already be highlighted. So a quick Ctrl-c should copy it for you.
   43.58 +    
   43.59 +
   43.60 +===== Flash Blocking =====
   43.61 +
   43.62 +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.
   43.63 +
   43.64 +First we need to make a folder if you don't already have it: <code>/home/tux/.local/share/midori/scripts</code>
   43.65 +"tux" is just used as an example. If you have a different user name then change accordingly. 
   43.66 +
   43.67 +These pictures are kind of big so I am just linking to them. Example before FlashBlock:
   43.68 +[[http://img180.yfrog.com/img180/7269/blocked.png|Flash Blocked]]
   43.69 +
   43.70 +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:
   43.71 +
   43.72 +[[http://img541.yfrog.com/img541/2801/notblocked.png|Flash Unblocked]]
   43.73 +===== User Scripts =====
   43.74 +
   43.75 +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.
   43.76 +
   43.77 +[[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. 
   43.78 +
   43.79 +[[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.
   43.80 +
   43.81 +[[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.  
   43.82 +
   43.83 +[[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. 
   43.84 +
   43.85 +[[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.
   43.86 +
   43.87 +===== Shortcuts =====
   43.88 +In extensions enable: shortcuts
   43.89 +
   43.90 +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:
   43.91 +
   43.92 +{{http://img21.yfrog.com/img21/1046/shortcuts.png}}
   43.93 +
   43.94 +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:
   43.95 +<code> Control, Alt, or either Winkeys</code>
   43.96 +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:
   43.97 +
   43.98 +<code>
   43.99 +Show/Hide Sidepanel   F2
  43.100 +Show/Hide Bookmarkbar F3
  43.101 +Show/Hide Menubar     F4
  43.102 +Refresh               F5
  43.103 +Preferences           F7
  43.104 +Focus Current Tab     F9
  43.105 +Full Screen           F11
  43.106 +Bookmarks             Ctrl+B
  43.107 +Add Bookmarks         Ctrl+D
  43.108 +Homepage              Ctrl+H
  43.109 +Highlight URLbar      Ctrl+L
  43.110 +Close Tab             Ctrl+W
  43.111 +Next Tab              Ctrl+Page Down
  43.112 +Previous Tab          Ctrl+Page Up
  43.113 +</code> 
  43.114 +
  43.115 +Just wanted to add that if you want to "disable" a shortcut. Pressing Backspace in "New accelarator..." will disable it.
  43.116 +
  43.117 +---- 
  43.118 +\\
  43.119 +^  Page Review Section  ^^ 
  43.120 +|Quality| Good  |
  43.121 +|Review| Minor Updates  |
  43.122 +|Priority| Medium |
  43.123 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
  43.124 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
  43.125 +|How to Improve| Suggest briefly|
  43.126 +|::: |  |
  43.127 +
  43.128 +\\
  43.129 +----
  43.130 \ No newline at end of file

    44.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    44.2 +++ b/pages/en/guides/modem.txt	Sat Feb 26 12:17:18 2011 +0000
    44.3 @@ -0,0 +1,17 @@
    44.4 +====== Hardware Guides: Modems ======
    44.5 +
    44.6 +[[cricket-a600|Cricket A600 Broadband Modem]]: - How to install a Cricket a600 Broadband Modem
    44.7 +
    44.8 +---- 
    44.9 +\\
   44.10 +^  Page Review Section  ^^ 
   44.11 +|Quality| Low  |
   44.12 +|Review| Major Updates  |
   44.13 +|Priority| Medium |
   44.14 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
   44.15 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
   44.16 +|How to Improve| Suggest briefly|
   44.17 +|::: |  |
   44.18 +
   44.19 +\\
   44.20 +----
   44.21 \ No newline at end of file

    45.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    45.2 +++ b/pages/en/guides/netstart.txt	Sat Feb 26 12:17:18 2011 +0000
    45.3 @@ -0,0 +1,57 @@
    45.4 +====== Web start and possible immediate installation ======
    45.5 +
    45.6 +===== Special figure in Slitaz ! =====
    45.7 +
    45.8 +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.
    45.9 +
   45.10 +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.
   45.11 +
   45.12 +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.
   45.13 +
   45.14 +The same technical ability can of course be used within a closed community.
   45.15 +
   45.16 +==== Where can I find the starting image for a starting floppy disk? ====
   45.17 +
   45.18 +http://mirror.slitaz.org/boot/floppy-grub4dos
   45.19 +
   45.20 +Please read more here:
   45.21 +
   45.22 +http://boot.slitaz.org/
   45.23 +
   45.24 +==== Where can I find the small ISO for a small starting CD rom? ====
   45.25 +
   45.26 +You can use the little flavor version
   45.27 + 
   45.28 +http://mirror.slitaz.org/iso/2.0/flavors/slitaz-2.0-base.iso
   45.29 +
   45.30 +for that.
   45.31 +
   45.32 +Only enter please "web" as commando line option!
   45.33 +
   45.34 +==== Starting from the net ====
   45.35 +
   45.36 +The start from net don't differ from usual start from the CD.
   45.37 +
   45.38 +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.
   45.39 +
   45.40 +==== Install Slitaz on the hard disk after the net start ====
   45.41 +
   45.42 +Of course here is an important difference compared with the usual start:
   45.43 +
   45.44 +There is no CD in the drive where the installation program can find the row files.
   45.45 +
   45.46 +.... 
   45.47 +
   45.48 +==== Regular net start in my community net (school etc.) ====
   45.49 +
   45.50 +=== Install the adequate Slitaz version on the own server ===
   45.51 +
   45.52 +....
   45.53 +
   45.54 +=== Limit access if required ===
   45.55 +
   45.56 +....
   45.57 +
   45.58 +=== Prepare an adequate ISO for a own starting check card mini CD ===
   45.59 +
   45.60 +....

    46.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
    46.2 +++ b/pages/en/guides/network-script.txt	Sat Feb 26 12:17:18 2011 +0000
    46.3 @@ -0,0 +1,158 @@
    46.4 +====== Secrets of /etc/init.d/network.sh ======
    46.5 +
    46.6 +===== Introduction =====
    46.7 +
    46.8 +SliTaz launches the /etc/init.d/network.sh at startup to initialize the network. It configures the hostname, loopback interface, and internet connection.
    46.9 +
   46.10 +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.
   46.11 +
   46.12 +===== Usage =====
   46.13 +
   46.14 +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.
   46.15 +
   46.16 +To start the default connection, as when booting:
   46.17 +
   46.18 +<code>
   46.19 +# /etc/init.d/network.sh start
   46.20 +</code>
   46.21 +
   46.22 +The start arg should be used only at boot. To stop the connection:
   46.23 +
   46.24 +<code>
   46.25 +# /etc/init.d/network.sh stop
   46.26 +</code>
   46.27 +
   46.28 +To stop and restart:
   46.29 +
   46.30 +<code>
   46.31 +# /etc/init.d/network.sh restart
   46.32 +</code>
   46.33 +
   46.34 +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.
   46.35 +
   46.36 +For example, we can create a directory /etc/network, containing some config files, named:
   46.37 +
   46.38 +    * Home, for home, using an ethernet connection and a static ip.
   46.39 +    * Desktop, for the desktop, with a wep encryption, and a static ip.
   46.40 +    * Univ, wifi without encryption, and with dhcp.
   46.41 +
   46.42 +Now to get connected at Home, later at a Desktop and finally at Univ, before stopping connection, we only have to:
   46.43 +
   46.44 +<code>
   46.45 +# /etc/init.d/network.sh restart /etc/network/Home
   46.46 +# /etc/init.d/network.sh restart /etc/network/Desktop
   46.47 +# /etc/init.d/network.sh restart /etc/network/Univ
   46.48 +# /etc/init.d/network.sh stop
   46.49 +</code>
   46.50 +
   46.51 +===== Sudo =====
   46.52 +
   46.53 +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:
   46.54 +
   46.55 +<code>
   46.56 +# tazpkg get-install sudo
   46.57 +</code>
   46.58 +
   46.59 +And then configure it:
   46.60 +
   46.61 +<code>
   46.62 +# visudo
   46.63 +</code>
   46.64 +
   46.65 +For user tux, which must use network.sh from every host; without a password you should add:
   46.66 +
   46.67 +<file>
   46.68 +tux  ALL=NOPASSWD: /etc/init.d/network.sh,
   46.69 +</file>
   46.70 +
   46.71 +For user tortux, which may only get connected from localhost, and which should use a password each time, you should add:
   46.72 +
   46.73 +<file>
   46.74 +tortux my_hostname=PASSWD: /etc/init.d/network.sh,
   46.75 +</file>
   46.76 +
   46.77 +If you forgot your hostname, just run:
   46.78 +
   46.79 +<code>
   46.80 +$ cat /etc/hostname
   46.81 +</code>
   46.82 +
   46.83 +Here is some help to use visudo:
   46.84 +
   46.85 +    * i insertion mode (to write).
   46.86 +    * Escape exit insertion mode.
   46.87 +    * :wq record and quit.
   46.88 +    * :q! quit without recording.
   46.89 +
   46.90 +===== Openbox =====
   46.91 +
   46.92 +All this is not that really user friendly...
   46.93 +
   46.94 +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:
   46.95 +
   46.96 +<code bash>
   46.97 +#!/bin/sh
   46.98 +#
   46.99 +# openbox pipe menu to start network connections
  46.100 +# (This script is only useful if sudo is installed, and correctly configured)
  46.101 +
  46.102 +echo ''
  46.103 +
  46.104 +# for default file:
  46.105 +echo ''
  46.106 +echo ''
  46.107 +echo 'sudo /etc/init.d/network.sh restart'
  46.108 +echo ''
  46.109 +
  46.110 +# for others files:
  46.111 +for file in $(ls /etc/network/)
  46.112 +	do
  46.113 +	echo -e ""
  46.114 +	echo ''
  46.115 +	echo "sudo /etc/init.d/network.sh restart /etc/network/$file"
  46.116 +	echo ''
  46.117 +	done
  46.118 +
  46.119 +# To stop connections:
  46.120 +echo ''
  46.121 +echo ''
  46.122 +echo 'sudo /etc/init.d/network.sh stop'
  46.123 +echo ''
  46.124 +
  46.125 +echo ''
  46.126 +</code>
  46.127 +
  46.128 +Make it executable:
  46.129 +
  46.130 +<code sh>
  46.131 +# chmod +x /usr/lib/openbox/network-menu.sh
  46.132 +</code>
  46.133 +
  46.134 +And now you only have to add these lines in //~/.config/openbox/menu.xml//:
  46.135 +
  46.136 +<file>
  46.137 + menu id="network-menu" label="Network" 
  46.138 +	execute="/usr/lib/openbox/network-menu.sh" />
  46.139 +</file>
  46.140 +
  46.141 +Then reconfigure openbox:
  46.142 + 
  46.143 +<code>
  46.144 +$ openbox --reconfigure
  46.145 +</code>
  46.146 +
  46.147 +Enjoy!
  46.148 +
  46.149 +---- 
  46.150 +\\
  46.151 +^  Page Review Section  ^^ 
  46.152 +|Quality| Good  |
  46.153 +|Review| Minor Updates  |
  46.154 +|Priority| Medium |
  46.155 +|Problems| add a [[http://forum.slitaz.org|forum post link]]|
  46.156 +|:::     | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]|
  46.157 +|How to Improve| Suggest briefly|
  46.158 +|::: |  |
  46.159 +
  46.160 +\\
  46.161 +----