<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to FAQ</title><link>https://sourceforge.net/p/taz/wiki/FAQ/</link><description>Recent changes to FAQ</description><atom:link href="https://sourceforge.net/p/taz/wiki/FAQ/feed" rel="self"/><language>en</language><lastBuildDate>Fri, 16 Mar 2018 12:24:09 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/taz/wiki/FAQ/feed" rel="self" type="application/rss+xml"/><item><title>FAQ modified by Linux Scripts</title><link>https://sourceforge.net/p/taz/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v19
+++ v20
@@ -1,17 +1,10 @@
-Why is there a many-in-1 functionality at all ?
-The many-in-1 flavor functionality allows to add or drop some specific programs in the loading process during the boot. By eliminating the programs you won't need at that specific day, you'll speed up your system, and even more importantly, you can keep the size of the RAM you need low (which is essential for OS's that boot from RAM).
+Why is there boot setup functionality at all ?
+The boot setup functionality allows to add or drop some specific programs in the loading process during the boot. By eliminating the programs you won't need at that specific day, you'll speed up your system, and even more importantly, you can keep the size of the RAM you need low (which is essential for OS's that boot from RAM).

-What's the point in having many-in-1-flavors, even if you use it to add or drop (heavier) programs to increase speed ? Isn't it better to just have lightweight versions of the programs you're using instead (say mplayer2 or xmms instead of the mpv program you're using) ?
+What's the point in having boot setups, even if you use it to add or drop (heavier) programs to increase speed ? Isn't it better to just have lightweight versions of the programs you're using instead (say mplayer2 or xmms instead of the mpv program you're using) ?

-Well, no. We have considered that approach, but there are issues with it. First of all, programs are developed by independant coders, so they're not always looking to make it particularly suited for use in a lightweight distro like slitaz or TAZ (instead they may want to make it for heavier distro's of which the users use computers with very high system specifications (meaning that however heavy they make their program, it won't even be noticed by their users). Sadly, lightweight distro's like ours can't use it then, if all programs (for all individual tasks) would then be loaded, so the only way to still be able to use these programs is by not loading whatever program you won't need at that particular time. Using lighter-weight programs (that have fewer functions, are older/no longer up-to-date, are less convenient in use, ...) can adress this issue while allowing the user to still load every program on his harddisk, but few people will actually want to use such programs.
-
-Why didn't you just strip TAZ of almost all programs (so have it have even far less programs than what's the case now) and just use the LES scripts to install the programs instead ? This would have been possible, as persistance is added anyhow.
-
-That would have been the preferred option, yes. However that solution is incompatible with the many-in-1 functionality (as the rootfs files need to be made in advance for this many-in-1 functionality, and need to contain all the installed programs/files). The LES scripts work in the other direction, having people install or not install programs which works fine for distro's that doesn't have a many-in-1 functionality, but not with those that do have it. So, feel free to use the LES scripts, but only with any distro that doesn't have the many-in-1 functionality.
-
-Can you give a short overview of how TAZ was made ?
-Sure. We started off with slitaz 4 core which had all standard packages updated, some packages removed (later changed to slitaz 5 RC3 !). The list of current packages (and those that were removed) can be found at this page: [slitaz_4_5_corepackagesfortaz]. 
-Then, we updated slitaz with the LES scripts, altered the many-in-1 boot setups, and altered some extra files/settings (such as default use of xvesa video drivers rather than the xorg video drivers, ...) and made the iso. For the experts: this was all done by first downloading and using the [slitaz-4.0-core iso in livecd mode](http://mirror.switch.ch/ftp/mirror/slitaz/iso/4.0/flavors/), then updating the packages with tazpkg, [then using tazlito writeiso none /media/disk, and tazlito extract-distro, then modifying the files further using and then making the new TAZ flavor](http://doc.slitaz.org/en:handbook:genlivecd) and then generating the iso from that (well, actually many iso's were made as we didn't do all this in one go; for the version history, see [TAZdevelopmenthistory]. The iso is available here at sourceforge. The files from the iso are placed on out github page so as to help further development. We expect to add in the jailbreaked slitaz package manager and replace udev by mdev soon.
+Well, no. We have considered that approach, but there are issues with it. First of all, programs are developed by independant coders, so they're not always looking to make it particularly suited for use in a lightweight distro like TAZ (instead they may want to make it for heavier distro's of which the users use computers with very high system specifications (meaning that however heavy they make their program, it won't even be noticed by their users). Sadly, lightweight distro's like ours can't use it then, if all programs (for all individual tasks) would then be loaded, so the only way to still be able to use these programs is by not loading whatever program you won't need at that particular time. Using lighter-weight programs (that have fewer functions, are older/no longer up-to-date, are less convenient in use, ...) can adress this issue while allowing the user to still load every program on his harddisk, but few people will actually want to use such programs.

 Can I support TAZ somehow ?
-Glad you ask. Yes, you can. You can offer to help out in the coding work (contact us via e-mail and/or help out in making packages via [our Tazpkg Development Community](http://brenton.nom.za/forum/). Note that [our github page](https://github.com/ecocomputing/TAZ) can also be useful for making these packages (could be useful for sharing unfinished code between developers). You can also become a patron via our [patreon site](https://www.patreon.com/TeamTAZ?ty=h) if you're not a programmer and can help out this way. Note that the first option will help us out the most at present.
+Glad you ask. Yes, you can. You can offer to help out in the coding work (contact us via e-mail).
+You can also become a patron via our [patreon site](https://www.patreon.com/TeamTAZ?ty=h) if you're not a programmer and can help out this way. Note that the first option will help us out the most at present.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Linux Scripts</dc:creator><pubDate>Fri, 16 Mar 2018 12:24:09 -0000</pubDate><guid>https://sourceforge.net8f0fe72142e11eb4fbd23be6be7d85065a430bbb</guid></item><item><title>FAQ modified by Linux Scripts</title><link>https://sourceforge.net/p/taz/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v18
+++ v19
@@ -14,4 +14,4 @@
 Then, we updated slitaz with the LES scripts, altered the many-in-1 boot setups, and altered some extra files/settings (such as default use of xvesa video drivers rather than the xorg video drivers, ...) and made the iso. For the experts: this was all done by first downloading and using the [slitaz-4.0-core iso in livecd mode](http://mirror.switch.ch/ftp/mirror/slitaz/iso/4.0/flavors/), then updating the packages with tazpkg, [then using tazlito writeiso none /media/disk, and tazlito extract-distro, then modifying the files further using and then making the new TAZ flavor](http://doc.slitaz.org/en:handbook:genlivecd) and then generating the iso from that (well, actually many iso's were made as we didn't do all this in one go; for the version history, see [TAZdevelopmenthistory]. The iso is available here at sourceforge. The files from the iso are placed on out github page so as to help further development. We expect to add in the jailbreaked slitaz package manager and replace udev by mdev soon.

 Can I support TAZ somehow ?
-Glad you ask. Yes, you can. You can offer to help out in the coding work (contact us via e-mail and/or help out in making packages via [our Tazpkg Development Community](http://brenton.nom.za/forum/). Note that [our github page](https://github.com/ecocomputing/TAZ) can also be useful for making these packages (could be useful for sharing unfinished code between developers). You can also do a monetary donation at [our [patreon site](https://www.patreon.com/TeamTAZ?ty=h) if you're not a programmer and can help out this way. Note that the first option will help us out the most at present.
+Glad you ask. Yes, you can. You can offer to help out in the coding work (contact us via e-mail and/or help out in making packages via [our Tazpkg Development Community](http://brenton.nom.za/forum/). Note that [our github page](https://github.com/ecocomputing/TAZ) can also be useful for making these packages (could be useful for sharing unfinished code between developers). You can also become a patron via our [patreon site](https://www.patreon.com/TeamTAZ?ty=h) if you're not a programmer and can help out this way. Note that the first option will help us out the most at present.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Linux Scripts</dc:creator><pubDate>Thu, 07 Dec 2017 13:27:56 -0000</pubDate><guid>https://sourceforge.net4a12e2f0313dc1e8b742af5746252a14bc1103be</guid></item><item><title>FAQ modified by Linux Scripts</title><link>https://sourceforge.net/p/taz/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v17
+++ v18
@@ -14,4 +14,4 @@
 Then, we updated slitaz with the LES scripts, altered the many-in-1 boot setups, and altered some extra files/settings (such as default use of xvesa video drivers rather than the xorg video drivers, ...) and made the iso. For the experts: this was all done by first downloading and using the [slitaz-4.0-core iso in livecd mode](http://mirror.switch.ch/ftp/mirror/slitaz/iso/4.0/flavors/), then updating the packages with tazpkg, [then using tazlito writeiso none /media/disk, and tazlito extract-distro, then modifying the files further using and then making the new TAZ flavor](http://doc.slitaz.org/en:handbook:genlivecd) and then generating the iso from that (well, actually many iso's were made as we didn't do all this in one go; for the version history, see [TAZdevelopmenthistory]. The iso is available here at sourceforge. The files from the iso are placed on out github page so as to help further development. We expect to add in the jailbreaked slitaz package manager and replace udev by mdev soon.

 Can I support TAZ somehow ?
-Glad you ask. Yes, you can. You can offer to help out in the coding work (contact us via e-mail and/or just clone repositories via [our github page](https://github.com/ecocomputing/TAZ) ), and/or you can do a donation at [our patreon site](https://www.patreon.com/TeamTAZ?ty=h). Note that the first option will help us out the most at present.
+Glad you ask. Yes, you can. You can offer to help out in the coding work (contact us via e-mail and/or help out in making packages via [our Tazpkg Development Community](http://brenton.nom.za/forum/). Note that [our github page](https://github.com/ecocomputing/TAZ) can also be useful for making these packages (could be useful for sharing unfinished code between developers). You can also do a monetary donation at [our [patreon site](https://www.patreon.com/TeamTAZ?ty=h) if you're not a programmer and can help out this way. Note that the first option will help us out the most at present.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Linux Scripts</dc:creator><pubDate>Fri, 01 Jul 2016 07:53:35 -0000</pubDate><guid>https://sourceforge.net27af0b02fa452859817057a3a2e5acc65c58d9dd</guid></item><item><title>FAQ modified by Linux Scripts</title><link>https://sourceforge.net/p/taz/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v16
+++ v17
@@ -10,7 +10,7 @@
 That would have been the preferred option, yes. However that solution is incompatible with the many-in-1 functionality (as the rootfs files need to be made in advance for this many-in-1 functionality, and need to contain all the installed programs/files). The LES scripts work in the other direction, having people install or not install programs which works fine for distro's that doesn't have a many-in-1 functionality, but not with those that do have it. So, feel free to use the LES scripts, but only with any distro that doesn't have the many-in-1 functionality.

 Can you give a short overview of how TAZ was made ?
-Sure. We started off with slitaz 4 core which had all standard packages updated, some packages removed (later changed to slitaz 5 RC3 !). The list of current packages (and those that were removed) can be found at this page: [slitaz4corepackagesfortaz]. 
+Sure. We started off with slitaz 4 core which had all standard packages updated, some packages removed (later changed to slitaz 5 RC3 !). The list of current packages (and those that were removed) can be found at this page: [slitaz_4_5_corepackagesfortaz]. 
 Then, we updated slitaz with the LES scripts, altered the many-in-1 boot setups, and altered some extra files/settings (such as default use of xvesa video drivers rather than the xorg video drivers, ...) and made the iso. For the experts: this was all done by first downloading and using the [slitaz-4.0-core iso in livecd mode](http://mirror.switch.ch/ftp/mirror/slitaz/iso/4.0/flavors/), then updating the packages with tazpkg, [then using tazlito writeiso none /media/disk, and tazlito extract-distro, then modifying the files further using and then making the new TAZ flavor](http://doc.slitaz.org/en:handbook:genlivecd) and then generating the iso from that (well, actually many iso's were made as we didn't do all this in one go; for the version history, see [TAZdevelopmenthistory]. The iso is available here at sourceforge. The files from the iso are placed on out github page so as to help further development. We expect to add in the jailbreaked slitaz package manager and replace udev by mdev soon.

 Can I support TAZ somehow ?
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Linux Scripts</dc:creator><pubDate>Wed, 09 Dec 2015 12:35:48 -0000</pubDate><guid>https://sourceforge.netd92727bc8e5401862d56d63daf7bb933319b76ff</guid></item><item><title>FAQ modified by Linux Scripts</title><link>https://sourceforge.net/p/taz/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v15
+++ v16
@@ -10,7 +10,7 @@
 That would have been the preferred option, yes. However that solution is incompatible with the many-in-1 functionality (as the rootfs files need to be made in advance for this many-in-1 functionality, and need to contain all the installed programs/files). The LES scripts work in the other direction, having people install or not install programs which works fine for distro's that doesn't have a many-in-1 functionality, but not with those that do have it. So, feel free to use the LES scripts, but only with any distro that doesn't have the many-in-1 functionality.

 Can you give a short overview of how TAZ was made ?
-Sure. We started off with slitaz 4 core which had all standard packages updated, some packages removed. The list of current packages (and those that were removed) can be found at this page: [slitaz4corepackagesfortaz]. 
+Sure. We started off with slitaz 4 core which had all standard packages updated, some packages removed (later changed to slitaz 5 RC3 !). The list of current packages (and those that were removed) can be found at this page: [slitaz4corepackagesfortaz]. 
 Then, we updated slitaz with the LES scripts, altered the many-in-1 boot setups, and altered some extra files/settings (such as default use of xvesa video drivers rather than the xorg video drivers, ...) and made the iso. For the experts: this was all done by first downloading and using the [slitaz-4.0-core iso in livecd mode](http://mirror.switch.ch/ftp/mirror/slitaz/iso/4.0/flavors/), then updating the packages with tazpkg, [then using tazlito writeiso none /media/disk, and tazlito extract-distro, then modifying the files further using and then making the new TAZ flavor](http://doc.slitaz.org/en:handbook:genlivecd) and then generating the iso from that (well, actually many iso's were made as we didn't do all this in one go; for the version history, see [TAZdevelopmenthistory]. The iso is available here at sourceforge. The files from the iso are placed on out github page so as to help further development. We expect to add in the jailbreaked slitaz package manager and replace udev by mdev soon.

 Can I support TAZ somehow ?
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Linux Scripts</dc:creator><pubDate>Fri, 04 Dec 2015 09:59:49 -0000</pubDate><guid>https://sourceforge.netf91b8b87512f803638f6a72a3b8e08d411ff3de9</guid></item><item><title>FAQ modified by Linux Scripts</title><link>https://sourceforge.net/p/taz/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v14
+++ v15
@@ -11,7 +11,7 @@

 Can you give a short overview of how TAZ was made ?
 Sure. We started off with slitaz 4 core which had all standard packages updated, some packages removed. The list of current packages (and those that were removed) can be found at this page: [slitaz4corepackagesfortaz]. 
-Then, we updated slitaz with the LES scripts, altered the many-in-1 boot setups, and altered some extra files/settings (such as default use of xvesa video drivers rather than the xorg video drivers, ...) and made the iso. For the experts: this was all done by first downloading and using the [slitaz-4.0-core iso in livecd mode](http://mirror.switch.ch/ftp/mirror/slitaz/iso/4.0/flavors/), then updating the packages with tazpkg, [then using tazlito writeiso none /media/disk, and tazlito extract-distro, then modifying the files further using and then making the new TAZ flavor](http://doc.slitaz.org/en:handbook:genlivecd) and then generating the iso from that. The iso is available here at sourceforge. The files from the iso are placed on out github page so as to help further development. We expect to add in the jailbreaked slitaz package manager and replace udev by mdev soon.
+Then, we updated slitaz with the LES scripts, altered the many-in-1 boot setups, and altered some extra files/settings (such as default use of xvesa video drivers rather than the xorg video drivers, ...) and made the iso. For the experts: this was all done by first downloading and using the [slitaz-4.0-core iso in livecd mode](http://mirror.switch.ch/ftp/mirror/slitaz/iso/4.0/flavors/), then updating the packages with tazpkg, [then using tazlito writeiso none /media/disk, and tazlito extract-distro, then modifying the files further using and then making the new TAZ flavor](http://doc.slitaz.org/en:handbook:genlivecd) and then generating the iso from that (well, actually many iso's were made as we didn't do all this in one go; for the version history, see [TAZdevelopmenthistory]. The iso is available here at sourceforge. The files from the iso are placed on out github page so as to help further development. We expect to add in the jailbreaked slitaz package manager and replace udev by mdev soon.

 Can I support TAZ somehow ?
 Glad you ask. Yes, you can. You can offer to help out in the coding work (contact us via e-mail and/or just clone repositories via [our github page](https://github.com/ecocomputing/TAZ) ), and/or you can do a donation at [our patreon site](https://www.patreon.com/TeamTAZ?ty=h). Note that the first option will help us out the most at present.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Linux Scripts</dc:creator><pubDate>Tue, 01 Dec 2015 17:41:04 -0000</pubDate><guid>https://sourceforge.net1a8ec11cc4a11ad39b39a712d30426eb36810081</guid></item><item><title>FAQ modified by Linux Scripts</title><link>https://sourceforge.net/p/taz/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v13
+++ v14
@@ -11,7 +11,7 @@

 Can you give a short overview of how TAZ was made ?
 Sure. We started off with slitaz 4 core which had all standard packages updated, some packages removed. The list of current packages (and those that were removed) can be found at this page: [slitaz4corepackagesfortaz]. 
-Then, we updated slitaz with the LES scripts, altered the many-in-1 boot setups, and altered some extra files/settings (such as default use of xvesa video drivers rather than the xorg video drivers, ...) and made the iso. For the experts: this was all done by first downloading and using the [slitaz-4.0-core iso in livecd mode](http://mirror.switch.ch/ftp/mirror/slitaz/iso/4.0/flavors/), then updating the packages with tazpkg, [then using tazlito writeiso none /media/disk, and tazlito extract-distro, then modifying the files further using and then making the new TAZ flavor](http://doc.slitaz.org/en:handbook:genlivecd) and then generating the iso from that. The iso is available here at sourceforge. The files from the iso are placed on out github page so as to help further development. We expect to add in the pacman package manager and replace udev by mdev soon.
+Then, we updated slitaz with the LES scripts, altered the many-in-1 boot setups, and altered some extra files/settings (such as default use of xvesa video drivers rather than the xorg video drivers, ...) and made the iso. For the experts: this was all done by first downloading and using the [slitaz-4.0-core iso in livecd mode](http://mirror.switch.ch/ftp/mirror/slitaz/iso/4.0/flavors/), then updating the packages with tazpkg, [then using tazlito writeiso none /media/disk, and tazlito extract-distro, then modifying the files further using and then making the new TAZ flavor](http://doc.slitaz.org/en:handbook:genlivecd) and then generating the iso from that. The iso is available here at sourceforge. The files from the iso are placed on out github page so as to help further development. We expect to add in the jailbreaked slitaz package manager and replace udev by mdev soon.

 Can I support TAZ somehow ?
 Glad you ask. Yes, you can. You can offer to help out in the coding work (contact us via e-mail and/or just clone repositories via [our github page](https://github.com/ecocomputing/TAZ) ), and/or you can do a donation at [our patreon site](https://www.patreon.com/TeamTAZ?ty=h). Note that the first option will help us out the most at present.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Linux Scripts</dc:creator><pubDate>Thu, 26 Nov 2015 10:11:28 -0000</pubDate><guid>https://sourceforge.net1224bd942def481a69ce9bba94e119f500792417</guid></item><item><title>FAQ modified by Linux Scripts</title><link>https://sourceforge.net/p/taz/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v12
+++ v13
@@ -11,7 +11,7 @@

 Can you give a short overview of how TAZ was made ?
 Sure. We started off with slitaz 4 core which had all standard packages updated, some packages removed. The list of current packages (and those that were removed) can be found at this page: [slitaz4corepackagesfortaz]. 
-Then, we updated slitaz with the LES scripts, altered the many-in-1 boot setups, and altered some extra files/settings (such as default use of xvesa video drivers rather than the xorg video drivers, ...) and made the iso. For the experts: this was all done by first downloading and using the [slitaz-4.0-core iso](http://mirror.switch.ch/ftp/mirror/slitaz/iso/4.0/flavors/), [then using tazlito extract-distro, then modifying the files and then making the new TAZ flavor](http://doc.slitaz.org/en:handbook:genlivecd) and then generating the iso from that. The iso is available here at sourceforge. The files from the iso are placed on out github page so as to help further development. We expect to add in the pacman package manager and replace udev by mdev soon.
+Then, we updated slitaz with the LES scripts, altered the many-in-1 boot setups, and altered some extra files/settings (such as default use of xvesa video drivers rather than the xorg video drivers, ...) and made the iso. For the experts: this was all done by first downloading and using the [slitaz-4.0-core iso in livecd mode](http://mirror.switch.ch/ftp/mirror/slitaz/iso/4.0/flavors/), then updating the packages with tazpkg, [then using tazlito writeiso none /media/disk, and tazlito extract-distro, then modifying the files further using and then making the new TAZ flavor](http://doc.slitaz.org/en:handbook:genlivecd) and then generating the iso from that. The iso is available here at sourceforge. The files from the iso are placed on out github page so as to help further development. We expect to add in the pacman package manager and replace udev by mdev soon.

 Can I support TAZ somehow ?
 Glad you ask. Yes, you can. You can offer to help out in the coding work (contact us via e-mail and/or just clone repositories via [our github page](https://github.com/ecocomputing/TAZ) ), and/or you can do a donation at [our patreon site](https://www.patreon.com/TeamTAZ?ty=h). Note that the first option will help us out the most at present.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Linux Scripts</dc:creator><pubDate>Thu, 26 Nov 2015 09:08:13 -0000</pubDate><guid>https://sourceforge.netde573aa8648abb8f8dd6a93d56f8922a02670664</guid></item><item><title>FAQ modified by Linux Scripts</title><link>https://sourceforge.net/p/taz/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v11
+++ v12
@@ -10,7 +10,8 @@
 That would have been the preferred option, yes. However that solution is incompatible with the many-in-1 functionality (as the rootfs files need to be made in advance for this many-in-1 functionality, and need to contain all the installed programs/files). The LES scripts work in the other direction, having people install or not install programs which works fine for distro's that doesn't have a many-in-1 functionality, but not with those that do have it. So, feel free to use the LES scripts, but only with any distro that doesn't have the many-in-1 functionality.

 Can you give a short overview of how TAZ was made ?
-Sure. We started off with slitaz 4 core which had all standard packages updated, some packages removed. The list of current packages (and those that were removed) can be found at this page: [slitaz4corepackagesfortaz]. Then, we updated slitaz with the LES scripts, altered the many-in-1 boot setups, and altered some extra files/settings (such as default use of xvesa video drivers rather than the xorg video drivers, ...) and made the iso. For the experts: this was all done by first [making a recipe, then creating a full slitaz flavor, then modifying the files](http://doc.slitaz.org/en:handbook:genlivecd) and then generating the iso from that. The iso is available here at sourceforge. The files from the iso are placed on out github page so as to help further development. We expect to add in the pacman package manager and replace udev by mdev soon.
+Sure. We started off with slitaz 4 core which had all standard packages updated, some packages removed. The list of current packages (and those that were removed) can be found at this page: [slitaz4corepackagesfortaz]. 
+Then, we updated slitaz with the LES scripts, altered the many-in-1 boot setups, and altered some extra files/settings (such as default use of xvesa video drivers rather than the xorg video drivers, ...) and made the iso. For the experts: this was all done by first downloading and using the [slitaz-4.0-core iso](http://mirror.switch.ch/ftp/mirror/slitaz/iso/4.0/flavors/), [then using tazlito extract-distro, then modifying the files and then making the new TAZ flavor](http://doc.slitaz.org/en:handbook:genlivecd) and then generating the iso from that. The iso is available here at sourceforge. The files from the iso are placed on out github page so as to help further development. We expect to add in the pacman package manager and replace udev by mdev soon.

 Can I support TAZ somehow ?
 Glad you ask. Yes, you can. You can offer to help out in the coding work (contact us via e-mail and/or just clone repositories via [our github page](https://github.com/ecocomputing/TAZ) ), and/or you can do a donation at [our patreon site](https://www.patreon.com/TeamTAZ?ty=h). Note that the first option will help us out the most at present.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Linux Scripts</dc:creator><pubDate>Wed, 25 Nov 2015 14:42:18 -0000</pubDate><guid>https://sourceforge.net0e69b9a4acbe3f4800529b88d6f713fe23ca196f</guid></item><item><title>FAQ modified by Linux Scripts</title><link>https://sourceforge.net/p/taz/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v10
+++ v11
@@ -10,7 +10,7 @@
 That would have been the preferred option, yes. However that solution is incompatible with the many-in-1 functionality (as the rootfs files need to be made in advance for this many-in-1 functionality, and need to contain all the installed programs/files). The LES scripts work in the other direction, having people install or not install programs which works fine for distro's that doesn't have a many-in-1 functionality, but not with those that do have it. So, feel free to use the LES scripts, but only with any distro that doesn't have the many-in-1 functionality.

 Can you give a short overview of how TAZ was made ?
-Sure. We started off with slitaz 4 core which had all standard packages updated, some packages removed. The list of current packages (and those that were removed) can be found at this page: [slitaz4corepackagesfortaz]. Then, we updated slitaz with the LES scripts, altered the many-in-1 boot setups, and altered some extra files/settings (such as default use of xvesa video drivers rather than the xorg video drivers, ...) and made the iso. The iso is available here at sourceforge. The files from the iso are placed on out github page so as to help further development. We expect to add in the pacman package manager and replace udev by mdev soon.
+Sure. We started off with slitaz 4 core which had all standard packages updated, some packages removed. The list of current packages (and those that were removed) can be found at this page: [slitaz4corepackagesfortaz]. Then, we updated slitaz with the LES scripts, altered the many-in-1 boot setups, and altered some extra files/settings (such as default use of xvesa video drivers rather than the xorg video drivers, ...) and made the iso. For the experts: this was all done by first [making a recipe, then creating a full slitaz flavor, then modifying the files](http://doc.slitaz.org/en:handbook:genlivecd) and then generating the iso from that. The iso is available here at sourceforge. The files from the iso are placed on out github page so as to help further development. We expect to add in the pacman package manager and replace udev by mdev soon.

 Can I support TAZ somehow ?
 Glad you ask. Yes, you can. You can offer to help out in the coding work (contact us via e-mail and/or just clone repositories via [our github page](https://github.com/ecocomputing/TAZ) ), and/or you can do a donation at [our patreon site](https://www.patreon.com/TeamTAZ?ty=h). Note that the first option will help us out the most at present.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Linux Scripts</dc:creator><pubDate>Wed, 25 Nov 2015 08:45:39 -0000</pubDate><guid>https://sourceforge.netbb437d1469a57b17e804242ef705b9bd4a7f8846</guid></item></channel></rss>