COMP 3000 2011 Report: SliTaz - Revision history

Bobbybobbets: /* Initialization */

2011-12-23T06:55:14Z

Initialization

← Older revision		Revision as of 06:55, 23 December 2011
Line 298:		Line 298:

	'''Analysis''' <br />		'''Analysis''' <br />
	As you can see, only the necessary processes for basic functionalities have been started. The first processes to be initialized are the daemons responsible for hardware management tasks, then processes that provide a basis for user interfaces, followed by the interfaces themselves, and finally the utility processes. This order is important because each layer is the basis for the one above it. This architecture is necessary in order to ease code portability, maximize code reuse and facilitate innovation. SliTaz is a very good example of this; the developers have only been able to achieve their goal because it could take advantage of modular design, giving ~~them~~ options ~~that fit~~ their needs.		As you can see, only the necessary processes for basic functionalities have been started. The first processes to be initialized are the daemons responsible for hardware management tasks, then processes that provide a basis for user interfaces, followed by the interfaces themselves, and finally the utility processes. This order is important because each layer is the basis for the one above it. This architecture is necessary in order to ease code portability, maximize code reuse and facilitate innovation. SliTaz is a very good example of this; the developers have only been able to achieve their goal because they could take advantage of modular design, giving the best options for their needs.

Bobbybobbets: /* Initialization */

2011-12-23T06:53:42Z

Initialization

← Older revision		Revision as of 06:53, 23 December 2011
Line 297:		Line 297:
	[http://pcmanfm.sourceforge.net/ PCMan File Manager] is the default file management system used by LXDE. It is detrimental for an OS to have such a system because dealing directly with the filesystem would be unmanageable. The process '''gam_server''' is a daemon associated with [http://en.wikipedia.org/wiki/Gamin Gamin], a monitoring system for files and directories. It is used to change the state of the files' meta information whenever they are being used. Both of these processes work together to provide a meaningful way of working with the filesystem. [http://en.wikipedia.org/wiki/Udhcpc Udhcpc] is a lightweight Dynamic Host Configuration Protocol(DHCP) client and is necessary in order to communicate over most networks.<br />		[http://pcmanfm.sourceforge.net/ PCMan File Manager] is the default file management system used by LXDE. It is detrimental for an OS to have such a system because dealing directly with the filesystem would be unmanageable. The process '''gam_server''' is a daemon associated with [http://en.wikipedia.org/wiki/Gamin Gamin], a monitoring system for files and directories. It is used to change the state of the files' meta information whenever they are being used. Both of these processes work together to provide a meaningful way of working with the filesystem. [http://en.wikipedia.org/wiki/Udhcpc Udhcpc] is a lightweight Dynamic Host Configuration Protocol(DHCP) client and is necessary in order to communicate over most networks.<br />

	'''Analysis'''		'''Analysis''' <br />
	As you can see, only the necessary processes for basic functionalities have been started. The first processes to be initialized are the daemons responsible for hardware management tasks, then processes that provide a basis for user interfaces, followed by the interfaces themselves, and finally the utility processes. This order is important because each layer is the basis for the one above it. This architecture is necessary in order to ease code portability, maximize code reuse and facilitate innovation. SliTaz is a very good example of this; the developers have only been able to achieve their goal because it could take advantage of modular design, giving them options that fit their needs.		As you can see, only the necessary processes for basic functionalities have been started. The first processes to be initialized are the daemons responsible for hardware management tasks, then processes that provide a basis for user interfaces, followed by the interfaces themselves, and finally the utility processes. This order is important because each layer is the basis for the one above it. This architecture is necessary in order to ease code portability, maximize code reuse and facilitate innovation. SliTaz is a very good example of this; the developers have only been able to achieve their goal because it could take advantage of modular design, giving them options that fit their needs.

Bobbybobbets: /* Initialization */

2011-12-23T06:53:31Z

Initialization

← Older revision		Revision as of 06:53, 23 December 2011
Line 297:		Line 297:
	[http://pcmanfm.sourceforge.net/ PCMan File Manager] is the default file management system used by LXDE. It is detrimental for an OS to have such a system because dealing directly with the filesystem would be unmanageable. The process '''gam_server''' is a daemon associated with [http://en.wikipedia.org/wiki/Gamin Gamin], a monitoring system for files and directories. It is used to change the state of the files' meta information whenever they are being used. Both of these processes work together to provide a meaningful way of working with the filesystem. [http://en.wikipedia.org/wiki/Udhcpc Udhcpc] is a lightweight Dynamic Host Configuration Protocol(DHCP) client and is necessary in order to communicate over most networks.<br />		[http://pcmanfm.sourceforge.net/ PCMan File Manager] is the default file management system used by LXDE. It is detrimental for an OS to have such a system because dealing directly with the filesystem would be unmanageable. The process '''gam_server''' is a daemon associated with [http://en.wikipedia.org/wiki/Gamin Gamin], a monitoring system for files and directories. It is used to change the state of the files' meta information whenever they are being used. Both of these processes work together to provide a meaningful way of working with the filesystem. [http://en.wikipedia.org/wiki/Udhcpc Udhcpc] is a lightweight Dynamic Host Configuration Protocol(DHCP) client and is necessary in order to communicate over most networks.<br />

	'''Analysis'''~~<br />~~		'''Analysis'''

	As you can see, only the necessary processes for basic functionalities have been started. The first processes to be initialized are the daemons responsible for hardware management tasks, then processes that provide a basis for user interfaces, followed by the interfaces themselves, and finally the utility processes. This order is important because each layer is the basis for the one above it. This architecture is necessary in order to ease code portability, maximize code reuse and facilitate innovation. SliTaz is a very good example of this; the developers have only been able to achieve their goal because it could take advantage of modular design, giving them options that fit their needs.		As you can see, only the necessary processes for basic functionalities have been started. The first processes to be initialized are the daemons responsible for hardware management tasks, then processes that provide a basis for user interfaces, followed by the interfaces themselves, and finally the utility processes. This order is important because each layer is the basis for the one above it. This architecture is necessary in order to ease code portability, maximize code reuse and facilitate innovation. SliTaz is a very good example of this; the developers have only been able to achieve their goal because it could take advantage of modular design, giving them options that fit their needs.

Bobbybobbets: /* Initialization */

2011-12-23T06:53:14Z

Initialization

← Older revision		Revision as of 06:53, 23 December 2011
Line 296:		Line 296:
	These are processes that help make the user experience more efficient. They can include file managers, internet protocols, login managers, or any other software that may help the usability of the distribution.		These are processes that help make the user experience more efficient. They can include file managers, internet protocols, login managers, or any other software that may help the usability of the distribution.
	[http://pcmanfm.sourceforge.net/ PCMan File Manager] is the default file management system used by LXDE. It is detrimental for an OS to have such a system because dealing directly with the filesystem would be unmanageable. The process '''gam_server''' is a daemon associated with [http://en.wikipedia.org/wiki/Gamin Gamin], a monitoring system for files and directories. It is used to change the state of the files' meta information whenever they are being used. Both of these processes work together to provide a meaningful way of working with the filesystem. [http://en.wikipedia.org/wiki/Udhcpc Udhcpc] is a lightweight Dynamic Host Configuration Protocol(DHCP) client and is necessary in order to communicate over most networks.<br />		[http://pcmanfm.sourceforge.net/ PCMan File Manager] is the default file management system used by LXDE. It is detrimental for an OS to have such a system because dealing directly with the filesystem would be unmanageable. The process '''gam_server''' is a daemon associated with [http://en.wikipedia.org/wiki/Gamin Gamin], a monitoring system for files and directories. It is used to change the state of the files' meta information whenever they are being used. Both of these processes work together to provide a meaningful way of working with the filesystem. [http://en.wikipedia.org/wiki/Udhcpc Udhcpc] is a lightweight Dynamic Host Configuration Protocol(DHCP) client and is necessary in order to communicate over most networks.<br />

			'''Analysis'''<br />

			As you can see, only the necessary processes for basic functionalities have been started. The first processes to be initialized are the daemons responsible for hardware management tasks, then processes that provide a basis for user interfaces, followed by the interfaces themselves, and finally the utility processes. This order is important because each layer is the basis for the one above it. This architecture is necessary in order to ease code portability, maximize code reuse and facilitate innovation. SliTaz is a very good example of this; the developers have only been able to achieve their goal because it could take advantage of modular design, giving them options that fit their needs.

Bobbybobbets: /* Initialization */

2011-12-23T06:47:04Z

Initialization

← Older revision		Revision as of 06:47, 23 December 2011
Line 273:		Line 273:
	== Initialization ==		== Initialization ==

	SliTaz does not use the usual initialization structure. Every script that must be run is specified in the $RUN_SCRIPTS variables and all deamons in the $RUN_DAEMONS variable. The initialization file /etc/init.d/rcS then uses the configuration file /etc/rcS to run the processes specified in the variables. This means that SliTaz does not use the runlevels to order the execution of the processes; instead, the boot order is specified in the script itself. The purpose of this is to centralize the main system boot initialization in one configuration file. Everything about the process is explained in /etc/init.d/README.<br />		SliTaz does not use the usual initialization structure. Every script that must be run is specified in the <code>$RUN_SCRIPTS</code> variables and all deamons in the <code>$RUN_DAEMONS</code> variable. The initialization file '''/etc/init.d/rcS''' then uses the configuration file '''/etc/rcS''' to run the processes specified in the variables. This means that SliTaz does not use the runlevels to order the execution of the processes; instead, the boot order is specified in the script itself. The purpose of this is to centralize the main system boot initialization in one configuration file. Everything about the process is explained in '''/etc/init.d/README'''.<br />

	Here is a list of all running processes right after the booting process.<br/><br/>		Here is a list of all running processes right after the booting process.<br/><br/>

Bobbybobbets: /* Initialization */

2011-12-23T06:45:52Z

Initialization

← Older revision		Revision as of 06:45, 23 December 2011
Line 295:		Line 295:

	These are processes that help make the user experience more efficient. They can include file managers, internet protocols, login managers, or any other software that may help the usability of the distribution.		These are processes that help make the user experience more efficient. They can include file managers, internet protocols, login managers, or any other software that may help the usability of the distribution.
	[http://pcmanfm.sourceforge.net/ PCMan File Manager] is the default file management system used by LXDE. It is detrimental for an OS to have such a system because dealing directly with the filesystem would be unmanageable. The process '''gam_server''' is a daemon associated with [http://en.wikipedia.org/wiki/Gamin Gamin], a monitoring system for files and directories. It is used to change the state of the files' meta information whenever they are being used. Both of these processes work together to provide a meaningful way of working with the filesystem. [http://en.wikipedia.org/wiki/Udhcpc Udhcpc] is a lightweight ~~dynamic host configuration protocol~~(DHCP) client and is necessary in order to communicate over most networks.<br />		[http://pcmanfm.sourceforge.net/ PCMan File Manager] is the default file management system used by LXDE. It is detrimental for an OS to have such a system because dealing directly with the filesystem would be unmanageable. The process '''gam_server''' is a daemon associated with [http://en.wikipedia.org/wiki/Gamin Gamin], a monitoring system for files and directories. It is used to change the state of the files' meta information whenever they are being used. Both of these processes work together to provide a meaningful way of working with the filesystem. [http://en.wikipedia.org/wiki/Udhcpc Udhcpc] is a lightweight Dynamic Host Configuration Protocol(DHCP) client and is necessary in order to communicate over most networks.<br />

Bobbybobbets: /* Initialization */

2011-12-23T06:41:59Z

Initialization

← Older revision		Revision as of 06:41, 23 December 2011
Line 286:		Line 286:
	Daemons are special processes that run in the background. They are not interactive and serve specific purposes such as logging('''syslogd''', '''klogd'''), event management('''udevd'''), and device management('''hald''', '''dbus'''). Some daemons are more important than others, such as '''udevd''', '''hald''' and '''dbus''', that take part in providing an Application programming interface(API) to other processes. In other words, any process which communicates with the hardware through these APIs should be started after the mentioned daemons. Out of the three, '''udevd''' must be started first because it is responsible for hotplug events(hardware recognition), then '''dbus''', a system used for inter-process commucations, and finally '''hald''', the hardware abstraction layer.<br />		Daemons are special processes that run in the background. They are not interactive and serve specific purposes such as logging('''syslogd''', '''klogd'''), event management('''udevd'''), and device management('''hald''', '''dbus'''). Some daemons are more important than others, such as '''udevd''', '''hald''' and '''dbus''', that take part in providing an Application programming interface(API) to other processes. In other words, any process which communicates with the hardware through these APIs should be started after the mentioned daemons. Out of the three, '''udevd''' must be started first because it is responsible for hotplug events(hardware recognition), then '''dbus''', a system used for inter-process commucations, and finally '''hald''', the hardware abstraction layer.<br />

	'''~~Graphical~~ interface'''<br />		'''User interface'''<br />
	Processes : Xorg, xterm, openbox, lxpanel		Processes : Xorg, xterm, openbox, lxpanel

	These are processes that allow users to effectively interact with the computer. '''Xorg''' is an open source software that serves as a hardware abstraction layer based on the [http://en.wikipedia.org/wiki/X_Window_System X Window System]. It was initially designed to create efficient and portable interfaces between terminals and servers running client applications. This client-server architecture is, however, also usable on a single computer and is therefore used by many operating systems as their basis for graphical interfaces. Operating systems use [http://en.wikipedia.org/wiki/Window_manager window managers] in order to create a proper desktop environment by having a properly managed windows system. '''Openbox''' is one of those window managers and is based on the '''Xorg''' API. The process '''lxpanel''' is part of a bigger desktop environment, [http://en.wikipedia.org/wiki/LXDE LXDE], also based on '''Xorg''', and is used to manage SliTaz's quick-launch menu.<br />		These are processes that allow users to effectively interact with the computer. '''Xorg''' is an open source software that serves as a hardware abstraction layer based on the [http://en.wikipedia.org/wiki/X_Window_System X Window System]. It was initially designed to create efficient and portable interfaces between terminals and servers running client applications. This client-server architecture is, however, also usable on a single computer and is therefore used by many operating systems as their basis for graphical interfaces. Operating systems use [http://en.wikipedia.org/wiki/Window_manager window managers] in order to create a proper desktop environment by having a properly managed windows system. '''Openbox''' is one of those window managers and is based on the '''Xorg''' API. The process '''lxpanel''' is part of a bigger desktop environment, [http://en.wikipedia.org/wiki/LXDE LXDE], also based on '''Xorg''', and is used to manage SliTaz's quick-launch menu.<br />

	'''~~File management~~'''<br />		'''Utility processes'''<br />
	Processes : pcmanfm, gam_server		Processes : pcmanfm, gam_server, udhcpc, slim

	[http://pcmanfm.sourceforge.net/ PCMan File Manager] is the default file management system used by LXDE. It is detrimental for an OS to have such a system because dealing directly with the filesystem would be unmanageable. The process '''gam_server''' is a daemon associated with [http://en.wikipedia.org/wiki/Gamin Gamin], a monitoring system for files and directories. It is used to change the state of the files' meta information whenever they are being used. Both of these processes work together to provide a meaningful way of working with the filesystem.<br />		These are processes that help make the user experience more efficient. They can include file managers, internet protocols, login managers, or any other software that may help the usability of the distribution.
			[http://pcmanfm.sourceforge.net/ PCMan File Manager] is the default file management system used by LXDE. It is detrimental for an OS to have such a system because dealing directly with the filesystem would be unmanageable. The process '''gam_server''' is a daemon associated with [http://en.wikipedia.org/wiki/Gamin Gamin], a monitoring system for files and directories. It is used to change the state of the files' meta information whenever they are being used. Both of these processes work together to provide a meaningful way of working with the filesystem. [http://en.wikipedia.org/wiki/Udhcpc Udhcpc] is a lightweight dynamic host configuration protocol(DHCP) client and is necessary in order to communicate over most networks.<br />

Bobbybobbets: /* Initialization */

2011-12-23T02:56:54Z

Initialization

← Older revision		Revision as of 02:56, 23 December 2011
Line 273:		Line 273:
	== Initialization ==		== Initialization ==

	SliTaz does not use the usual ~~initiation~~ structure. Every script that must be run is specified in the $RUN_SCRIPTS variables and all deamons in the $RUN_DAEMONS variable. The ~~initiation~~ file /etc/init.d/rcS~~, called by inittab ,~~ then uses the configuration file /etc/rcS to run the processes specified in the variables. This means that SliTaz does not use the runlevels to order the execution of the processes; instead, the boot order is specified in the script itself. The purpose of this is to centralize the main system boot initialization in one ~~config~~ file. Everything about the process is explained in /etc/init.d/README.<br />		SliTaz does not use the usual initialization structure. Every script that must be run is specified in the $RUN_SCRIPTS variables and all deamons in the $RUN_DAEMONS variable. The initialization file /etc/init.d/rcS then uses the configuration file /etc/rcS to run the processes specified in the variables. This means that SliTaz does not use the runlevels to order the execution of the processes; instead, the boot order is specified in the script itself. The purpose of this is to centralize the main system boot initialization in one configuration file. Everything about the process is explained in /etc/init.d/README.<br />

	Here's a list of all running processes right after the booting process.<br/><br/>		Here is a list of all running processes right after the booting process.<br/><br/>

	[[File:SliTaz_ps.png\|500px\|A look at Midori's rendering of Facebook]]		[[File:SliTaz_ps.png\|500px\|A look at Midori's rendering of Facebook]]
Line 284:		Line 284:
	Processes : udevd, syslogd, klogd, dbus-daemon, hald, hald-runner, hald-addon-input, hald-addon-storage, hald-addon-acpi, gam_server<br />		Processes : udevd, syslogd, klogd, dbus-daemon, hald, hald-runner, hald-addon-input, hald-addon-storage, hald-addon-acpi, gam_server<br />

	Daemons are special processes that run in the background. They are not interactive and serve specific purposes such as logging('''syslogd''', '''klogd'''), event management('''udevd'''), and device management('''hald''', '''dbus'''). Some daemons are more important than others, such as '''udevd''', '''hald''' and '''dbus''', ~~who~~ take part in providing an Application programming interface(API) to other processes. In other words, any process which ~~communicate~~ with the hardware through these APIs should be started after the mentioned daemons. Out of the three, '''udevd''' must be started first because it is responsible for hotplug events(hardware recognition), then '''dbus''', a system used for inter-process commucations, and finally '''hald''', the hardware abstraction layer.<br />		Daemons are special processes that run in the background. They are not interactive and serve specific purposes such as logging('''syslogd''', '''klogd'''), event management('''udevd'''), and device management('''hald''', '''dbus'''). Some daemons are more important than others, such as '''udevd''', '''hald''' and '''dbus''', that take part in providing an Application programming interface(API) to other processes. In other words, any process which communicates with the hardware through these APIs should be started after the mentioned daemons. Out of the three, '''udevd''' must be started first because it is responsible for hotplug events(hardware recognition), then '''dbus''', a system used for inter-process commucations, and finally '''hald''', the hardware abstraction layer.<br />

	'''Graphical interface'''<br />		'''Graphical interface'''<br />
	Processes : Xorg, xterm, openbox, lxpanel		Processes : Xorg, xterm, openbox, lxpanel

	These are processes that allow users to effectively interact with the computer. '''Xorg''' is an open source software that serves as a hardware abstraction layer based on the [http://en.wikipedia.org/wiki/X_Window_System X Window System]. It was initially designed to create efficient and portable interfaces between terminals and servers running client applications. This client-server architecture is however also ~~useable~~ on a single computer and is therefore used by many operating systems as their basis for graphical interfaces. Operating systems use [http://en.wikipedia.org/wiki/Window_manager window managers] in order to create a proper desktop environment by having a properly managed windows system. '''Openbox''' is one of those window managers and is based on the '''Xorg''' API. The process '''lxpanel''' is part of a bigger desktop environment, [http://en.wikipedia.org/wiki/LXDE LXDE], also based on '''Xorg''', and is used to manage SliTaz's quick-launch menu.<br />		These are processes that allow users to effectively interact with the computer. '''Xorg''' is an open source software that serves as a hardware abstraction layer based on the [http://en.wikipedia.org/wiki/X_Window_System X Window System]. It was initially designed to create efficient and portable interfaces between terminals and servers running client applications. This client-server architecture is, however, also usable on a single computer and is therefore used by many operating systems as their basis for graphical interfaces. Operating systems use [http://en.wikipedia.org/wiki/Window_manager window managers] in order to create a proper desktop environment by having a properly managed windows system. '''Openbox''' is one of those window managers and is based on the '''Xorg''' API. The process '''lxpanel''' is part of a bigger desktop environment, [http://en.wikipedia.org/wiki/LXDE LXDE], also based on '''Xorg''', and is used to manage SliTaz's quick-launch menu.<br />

	'''File management'''<br />		'''File management'''<br />

Bobbybobbets: /* Initialization */

2011-12-23T02:49:43Z

Initialization

← Older revision		Revision as of 02:49, 23 December 2011
Line 273:		Line 273:
	== Initialization ==		== Initialization ==

	SliTaz does not use the usual ~~init~~ structure. Every script that must be run is specified in the $RUN_SCRIPTS variables and all deamons in the $RUN_DAEMONS variable. The ~~init~~ file /etc/init.d/rcS, called by inittab , then uses the ~~config~~ file /etc/rcS to run the processes specified in the variables. This means that SliTaz does not use the runlevels to order the execution of the processes; instead, the boot order is specified in the script itself. The purpose of this is to centralize the main system boot initialization in one config file. Everything about the process is explained in /etc/init.d/README.<br />		SliTaz does not use the usual initiation structure. Every script that must be run is specified in the $RUN_SCRIPTS variables and all deamons in the $RUN_DAEMONS variable. The initiation file /etc/init.d/rcS, called by inittab , then uses the configuration file /etc/rcS to run the processes specified in the variables. This means that SliTaz does not use the runlevels to order the execution of the processes; instead, the boot order is specified in the script itself. The purpose of this is to centralize the main system boot initialization in one config file. Everything about the process is explained in /etc/init.d/README.<br />

	Here's a list of all running processes right after the booting process.<br/><br/>		Here's a list of all running processes right after the booting process.<br/><br/>

Bobbybobbets: /* Major package versions */

2011-12-23T02:46:54Z

Major package versions

← Older revision		Revision as of 02:46, 23 December 2011
Line 161:		Line 161:
	I believe that Linux was chosen because of its high customizability, unparalleled stability through years of testing, and wide adoption by the community.		I believe that Linux was chosen because of its high customizability, unparalleled stability through years of testing, and wide adoption by the community.

	Being able to customize the kernel allows the developers to make it as lean and fast as possible while giving the end users the possibility to add new modules to fill their needs. In addition, Linux is one of the most stable operating ~~system~~ because it has been tested for many years by a lot of different people. For the same reasons, a lot of documentation and help is available online which makes it much easier to fix potential problems. There is no doubt in my mind that using the Linux kernel was the right choice ~~to do~~ in this situation.		Being able to customize the kernel allows the developers to make it as lean and fast as possible while giving the end users the possibility to add new modules to fill their needs. In addition, Linux is one of the most stable operating systems because it has been tested for many years by a lot of different people. For the same reasons, a lot of documentation and help is available online which makes it much easier to fix potential problems. There is no doubt in my mind that using the Linux kernel was the right choice in this situation.

	<br/>		<br/>
Line 173:		Line 173:
	''Speculations''		''Speculations''

	There ~~isn't~~ much to say here; Pretty much every Linux distribution contains this library so it ~~isn't a surprise~~ that the SliTaz team decided to include it. It is one of the most complete c libraries out there.		There is not much to say here. Pretty much every Linux distribution contains this library so it is not surprising that the SliTaz team decided to include it. It is one of the most complete c libraries out there.

	<br/>		<br/>
Line 185:		Line 185:
	''Speculations''		''Speculations''

	Xorg was introduced in SliTaz version 3.0 to replace Xvesa. The overall feeling that I got while researching both of them was that Xvesa is leaner than Xorg but very limited in several aspects, such as video playback, refresh rate control and GLX compatibility. My hypothesis is that the SliTaz development team wanted to increase compatibility with a higher number of setups and was ready to sacrifice on size and ~~ressource~~ allocation. It must be noted that Xvesa is still supported and that the only drawback to including Xorg is the increased size of the ISO. I definitely think that the advantages ~~that~~ this move ~~adds~~ far ~~outweight~~ the small bump in size of the operating system.		Xorg was introduced in SliTaz version 3.0 to replace Xvesa. The overall feeling that I got while researching both of them was that Xvesa is leaner than Xorg, but very limited in several aspects, such as video playback, refresh rate control and GLX compatibility. My hypothesis is that the SliTaz development team wanted to increase compatibility with a higher number of setups and was ready to sacrifice on size and resource allocation. It must be noted that Xvesa is still supported and that the only drawback to including Xorg is the increased size of the ISO. I definitely think that the advantages added by this move far outweigh the small bump in size of the operating system.

	<br/>		<br/>
Line 197:		Line 197:
	''Speculations''		''Speculations''

	I think that GTK+ was chosen by the developers because it has much better potential than the competition for smaller applications. It ~~doesn't~~ need to pull in the whole GNOME framework and is the graphical backbone of most applications aimed at being lightweight, such as Abiword, Midori, GIMP and Pidgin. Given SliTaz's goal to be very small, it makes sense for it to use an environment that ~~doesn't~~ have a big footprint.		I think that GTK+ was chosen by the developers because it has much better potential than the competition for smaller applications. It does not need to pull in the whole GNOME framework and is the graphical backbone of most applications aimed at being lightweight, such as Abiword, Midori, GIMP and Pidgin. Given SliTaz's goal to be very small, it makes sense for it to use an environment that does not have a big footprint.

	<br/>		<br/>
Line 209:		Line 209:
	''Speculations''		''Speculations''

	Busybox was undoubtedly chosen because of its design philosophy, which is to work with systems that are very limited in ~~ressources~~. Again, this philosophy fits perfectly well with SliTaz's goal to be as lean as possible.		Busybox was undoubtedly chosen because of its design philosophy, which is to work with systems that are very limited in resources. Again, this philosophy fits perfectly well with SliTaz's goal to be as lean as possible.

	<br/>		<br/>
Line 221:		Line 221:
	''Speculations''		''Speculations''

	It is hard to say why they'd want to write their own package manager given the relatively big amount of free ones out there. I assume that none of them could run on the barebone configuration that SliTaz provides considering that Tazpkg is completely written in SHell script. It is also said to work well with Busybox, [http://en.wikipedia.org/wiki/Almquist_shell ash shell](BSD-licensed replacement for Bourne Shell) and bash - another reason why they might have needed a custom package manager.		It is hard to say why they would want to write their own package manager given the relatively big amount of free ones out there. I assume that none of them could run on the barebone configuration that SliTaz provides considering that Tazpkg is completely written in SHell script. It is also said to work well with Busybox, [http://en.wikipedia.org/wiki/Almquist_shell ash shell](BSD-licensed replacement for Bourne Shell) and bash - another reason why they might have needed a custom package manager.

	<br/>		<br/>
Line 233:		Line 233:
	''Speculations''		''Speculations''

	Midori is designed to be lightweight and fast. It uses the GTK+ 2 interface and renders the webpages using webkit, the same engine used by Safari and Google Chrome. All of these properties ~~about~~ the browser go hand in hand with SliTaz's philosophy of being as small as possible without sacrificing on usability.		Midori is designed to be lightweight and fast. It uses the GTK+ 2 interface and renders the webpages using webkit, the same engine used by Safari and Google Chrome. All of these properties possessed by the browser go hand in hand with SliTaz's philosophy of being as small as possible without sacrificing on usability.

	<br/>		<br/>
Line 245:		Line 245:
	''Speculations''		''Speculations''

	For SliTaz to be a proper workstation, it needs to have the necessary applications to communicate through the internet. This is where Pidgin comes in handy; It's a multi-platform messenger which ~~understand~~ almost all the protocols used by popular messengers, such as MSN Messenger, Google Talk and Facebook chat. It uses the GTK+ interface and the fact that it supports all these protocols means that the OS ~~doesn't~~ need to include all the other applications.		For SliTaz to be a proper workstation, it needs to have the necessary applications to communicate through the internet. This is where Pidgin comes in handy. It is a multi-platform messenger which understands almost all the protocols used by popular messengers, such as MSN Messenger, Google Talk and Facebook chat. It uses the GTK+ interface and the fact that it supports all these protocols means that the OS does not need to include all the other applications.

	<br/>		<br/>
Line 257:		Line 257:
	''Speculations''		''Speculations''

	SliTaz would be a good candidate to build a webserver on an old machine which could be used, for example, by a web developer to test his work or by a small company to run its intranet application. Sqlite can be used for purposes that don't require a high volume of requests; Since SliTaz is designed to run on old, slow computers, it ~~won't~~ be used for high traffic websites and therefore ~~won't~~ need anything more complex than ~~sqlite~~. It is important to note that ~~sqlite~~ has been shown to work flawlessly with websites getting up to 1 million requests per day.		SliTaz would be a good candidate to build a webserver on an old machine which could be used, for example, by a web developer to test his work or by a small company to run its intranet application. Sqlite can be used for purposes that don't require a high volume of requests. Since SliTaz is designed to run on old, slow computers, it will not be used for high traffic websites and therefore will not need anything more complex than Sqlite. It is important to note that Sqlite has been shown to work flawlessly with websites getting up to 1 million requests per day.

	<br/>		<br/>
Line 269:		Line 269:
	''Speculations''		''Speculations''

	Lua is a lightweight (150 kb) scripting language designed to be very extensible, which means that it can be used for pretty much any purpose. Given SliTaz's goal to be very slim, it makes sense to include a scripting language that can be customized by the ~~user~~ depending on ~~its~~ needs. The alternative would be to include many languages that fill different roles, but that ~~wouldn't~~ be very practical.		Lua is a lightweight (150 kb) scripting language designed to be very extensible, which means that it can be used for pretty much any purpose. Given SliTaz's goal to be very slim, it makes sense to include a scripting language that can be customized by the users depending on their needs. The alternative would be to include many languages that fill different roles, but that would not be very practical.

	== Initialization ==		== Initialization ==