COMP 3000 2011 Report: Swift Linux - Revision history

Mabadeer: /* Initialization */

2011-12-19T22:49:46Z

Initialization

← Older revision		Revision as of 22:49, 19 December 2011
Line 225:		Line 225:
	First of all, BIOS is started as soon as the system is turned on to perform the basic initialization of the hardware, and then it hands control over to the boot loader, which loads Swift system kernel image <code>/boot/vmlinuz</code> and root filesystem image <code>/boot/initrd.img</code>.		First of all, BIOS is started as soon as the system is turned on to perform the basic initialization of the hardware, and then it hands control over to the boot loader, which loads Swift system kernel image <code>/boot/vmlinuz</code> and root filesystem image <code>/boot/initrd.img</code>.

	After that, the main boot process is started by the init script <code>/sbin/init</code>. Swift goes into runlevel N (none) to initialize the system by scripts <code>/etc/inittab</code>, then the <code>inittab</code> script directs the boot process to <code>/etc/init.d/rcS</code>. rcS in Swift is to call all S** scripts in <code>/etc/rcS.d</code> in numerical order, The list in Swift is obtained by typing <code>cd /etc/rcS.d</code><ref>[http://www.yolinux.com/TUTORIALS/LinuxTutorialInitProcess.html Greg Ippolito, Linux Init Process/PC Boot Procedure, 2009, Last accessed: December 19, 2011]</ref>. The output is as follows:		After that, the main boot process is started by the <code>init</code> script <code>/sbin/init</code>. Swift goes into runlevel N (none) to initialize the system by scripts <code>/etc/inittab</code>, then the <code>inittab</code> script directs the boot process to <code>/etc/init.d/rcS</code>. rcS in Swift is to call all S** scripts in <code>/etc/rcS.d</code> in numerical order, The list in Swift is obtained by typing <code>cd /etc/rcS.d</code><ref>[http://www.yolinux.com/TUTORIALS/LinuxTutorialInitProcess.html Greg Ippolito, Linux Init Process/PC Boot Procedure, 2009, Last accessed: December 19, 2011]</ref>. The output is as follows:

	S09module-init-tools S15networking		S09module-init-tools S15networking
Line 251:		Line 251:
	* Runlevel 6 is reboot (/etc/rc6.d).		* Runlevel 6 is reboot (/etc/rc6.d).

	All actual script files executed by the init system are located in the directory <code>/etc/init.d</code>. As a single-user mode, scripts <code>/etc/rc1.d</code> starting with a "k" are executed in an alphabetical order to perform killing services, and script <code>/etc/rc1.d</code> names starting with an "S" are executed in alphabetical order to perform starting services. The single user will then be logged in to Swift.		All actual script files executed by the <code>init</code> system are located in the directory <code>/etc/init.d</code>. As a single-user mode, scripts <code>/etc/rc1.d</code> starting with a "k" are executed in an alphabetical order to perform killing services, and script <code>/etc/rc1.d</code> names starting with an "S" are executed in alphabetical order to perform starting services. The single user will then be logged in to Swift.

	Daemons started are, for example, xdm, gdm, kdm and wdm for device managers.		Daemons started are, for example, xdm, gdm, kdm and wdm for device managers.

Mabadeer: /* Major package versions */

2011-12-19T22:44:55Z

Major package versions

← Older revision		Revision as of 22:44, 19 December 2011
Line 173:		Line 173:
	To report on the version numbers and upstream source for some of the major software packages included in Swift Linux as part of the standard install, we can find package resource, and download the associate version online, and use <code>diff</code> command to compare them.		To report on the version numbers and upstream source for some of the major software packages included in Swift Linux as part of the standard install, we can find package resource, and download the associate version online, and use <code>diff</code> command to compare them.

	Briefly, all the packages investigated were not the most stable version except for GTK+, APT and Shell. The most commonality among the packages included is that they are all light-weighted. Below we explore in details 10 of those packages.		Briefly, all the packages investigated were not the most stable version except for GTK+, APT and Shell. The most significant commonality among the packages included is that they are all light-weighted. Below we explore in details 10 of those packages.

	* '''Linux Kernel'''		* '''Linux Kernel'''

Mabadeer: /* Major package versions */

2011-12-19T22:44:12Z

Major package versions

← Older revision		Revision as of 22:44, 19 December 2011
Line 171:		Line 171:
	===Major package versions===		===Major package versions===

	To report on the version numbers and upstream source for some of the major software packages included in Swift Linux as part of the standard install, we can find package resource, and download the associate version online, and use "diff" command to compare ~~then:~~		To report on the version numbers and upstream source for some of the major software packages included in Swift Linux as part of the standard install, we can find package resource, and download the associate version online, and use <code>diff</code> command to compare them.

	Briefly, all the packages investigated were not the most stable version except for GTK+, APT and Shell. The most commonality among the packages included is that they are all light-weighted. Below we explore in details 10 of those packages.		Briefly, all the packages investigated were not the most stable version except for GTK+, APT and Shell. The most commonality among the packages included is that they are all light-weighted. Below we explore in details 10 of those packages.

Mabadeer: /* Initialization */

2011-12-19T22:42:12Z

Initialization

← Older revision		Revision as of 22:42, 19 December 2011
Line 221:		Line 221:
	===Initialization===		===Initialization===

	Since Swift is based on Debian, the initialization process is similar to Debian OS. One main difference is that in Debian it ~~will add~~ kernel modules before the main boot process by running scripts under <code>/init</code> directory. There is no such scripts in Swift.		Since Swift is based on Debian, the initialization process is similar to Debian OS. One main difference is that in Debian it adds kernel modules before the main boot process by running scripts under <code>/init</code> directory. There is no such scripts in Swift.

	First of all, BIOS is started as soon as the system is turned on to perform the basic initialization of the hardware, and then it hands control over to the boot loader, which ~~will load the~~ Swift system kernel image <code>/boot/vmlinuz</code> and root filesystem image <code>/boot/initrd.img</code>.		First of all, BIOS is started as soon as the system is turned on to perform the basic initialization of the hardware, and then it hands control over to the boot loader, which loads Swift system kernel image <code>/boot/vmlinuz</code> and root filesystem image <code>/boot/initrd.img</code>.

	After that, the main boot process is started by the init script <code>/sbin/init</code>. Swift ~~will go~~ into runlevel N (none) to initialize the system by scripts <code>/etc/inittab</code>, then the <code>inittab</code> script ~~will direct~~ the boot process to <code>/etc/init.d/rcS</code>. rcS in Swift is to call all S** scripts in <code>/etc/rcS.d</code> in numerical order, The list in Swift is obtained by typing <code>cd /etc/rcS.d</code><ref>[http://www.yolinux.com/TUTORIALS/LinuxTutorialInitProcess.html Greg Ippolito, Linux Init Process/PC Boot Procedure, 2009, Last accessed: December 19, 2011]</ref>. The output is as follows:		After that, the main boot process is started by the init script <code>/sbin/init</code>. Swift goes into runlevel N (none) to initialize the system by scripts <code>/etc/inittab</code>, then the <code>inittab</code> script directs the boot process to <code>/etc/init.d/rcS</code>. rcS in Swift is to call all S** scripts in <code>/etc/rcS.d</code> in numerical order, The list in Swift is obtained by typing <code>cd /etc/rcS.d</code><ref>[http://www.yolinux.com/TUTORIALS/LinuxTutorialInitProcess.html Greg Ippolito, Linux Init Process/PC Boot Procedure, 2009, Last accessed: December 19, 2011]</ref>. The output is as follows:

	S09module-init-tools S15networking		S09module-init-tools S15networking
Line 244:		Line 244:
	S09ifupdown-clean S15antiX.sh		S09ifupdown-clean S15antiX.sh

	These S scripts are there for system initialization. For example, <code>S01mountkernfs.sh</code> mounts kernel filesystems in /proc and /sys, etc. Once all S scripts in <code>/ect/rcS.d</code> have been executed, Swift ~~will~~ executes the S and K scripts after changing the runlevel. Each runlevel uses a directory for its configuration as follows:		These S scripts are there for system initialization. For example, <code>S01mountkernfs.sh</code> mounts kernel filesystems in /proc and /sys, etc. Once all S scripts in <code>/ect/rcS.d</code> have been executed, Swift executes the S and K scripts after changing the runlevel. Each runlevel uses a directory for its configuration as follows:

	* Runlevel 0 is halt (/etc/rc0.d/);		* Runlevel 0 is halt (/etc/rc0.d/);

Mabadeer: /* Major package versions */

2011-12-19T22:40:52Z

Major package versions

← Older revision		Revision as of 22:40, 19 December 2011
Line 190:		Line 190:

	GTK+ version installed is 2.1.0-2 released on March 14, 2011 which is in fact the most up-to-date stable version. [http://git.gnome.org/browse/gtk+ Here] is the upstream source URL.		GTK+ version installed is 2.1.0-2 released on March 14, 2011 which is in fact the most up-to-date stable version. [http://git.gnome.org/browse/gtk+ Here] is the upstream source URL.
	Qt's installed version is 4.7.2-3 released on March 1, 2011 while the most up-to-date version is 4.7.4 released on September 1, 2011. [http://www.qtsoftware.com/ ~~Upstream~~]		Qt's installed version is 4.7.2-3 released on March 1, 2011 while the most up-to-date version is 4.7.4 released on September 1, 2011. [http://www.qtsoftware.com/ Here] is the upstream source.

	* '''Shell'''		* '''Shell'''

Mabadeer: /* Initialization */

2011-12-19T22:38:50Z

Initialization

← Older revision		Revision as of 22:38, 19 December 2011
Line 253:		Line 253:
	All actual script files executed by the init system are located in the directory <code>/etc/init.d</code>. As a single-user mode, scripts <code>/etc/rc1.d</code> starting with a "k" are executed in an alphabetical order to perform killing services, and script <code>/etc/rc1.d</code> names starting with an "S" are executed in alphabetical order to perform starting services. The single user will then be logged in to Swift.		All actual script files executed by the init system are located in the directory <code>/etc/init.d</code>. As a single-user mode, scripts <code>/etc/rc1.d</code> starting with a "k" are executed in an alphabetical order to perform killing services, and script <code>/etc/rc1.d</code> names starting with an "S" are executed in alphabetical order to perform starting services. The single user will then be logged in to Swift.

	~~For~~ example, ~~daemons started are~~ xdm, gdm, kdm and wdm for device managers.		Daemons started are, for example, xdm, gdm, kdm and wdm for device managers.

	As illustrated above, Swift linux initializes itself in a sequential order. The initialization process took less than 3 minutes.		As illustrated above, Swift linux initializes itself in a sequential order. The initialization process took less than 3 minutes.

Mabadeer: /* Initialization */

2011-12-19T22:37:22Z

Initialization

← Older revision		Revision as of 22:37, 19 December 2011
Line 225:		Line 225:
	First of all, BIOS is started as soon as the system is turned on to perform the basic initialization of the hardware, and then it hands control over to the boot loader, which will load the Swift system kernel image <code>/boot/vmlinuz</code> and root filesystem image <code>/boot/initrd.img</code>.		First of all, BIOS is started as soon as the system is turned on to perform the basic initialization of the hardware, and then it hands control over to the boot loader, which will load the Swift system kernel image <code>/boot/vmlinuz</code> and root filesystem image <code>/boot/initrd.img</code>.

	After that, the main boot process ~~will be~~ started by the init script <code>/sbin/init</code>. Swift will go into runlevel N (none) to initialize the system by scripts <code>/etc/inittab</code>, then the <code>inittab</code> script will direct the boot process to <code>/etc/init.d/rcS</code>. rcS in Swift is to call all S** scripts in <code>/etc/rcS.d</code> in numerical order, The list in Swift is obtained by typing <code>cd /etc/rcS.d</code><ref>[http://www.yolinux.com/TUTORIALS/LinuxTutorialInitProcess.html Greg Ippolito, Linux Init Process/PC Boot Procedure, 2009, Last accessed: December 19, 2011]</ref>. The output is as follows:		After that, the main boot process is started by the init script <code>/sbin/init</code>. Swift will go into runlevel N (none) to initialize the system by scripts <code>/etc/inittab</code>, then the <code>inittab</code> script will direct the boot process to <code>/etc/init.d/rcS</code>. rcS in Swift is to call all S** scripts in <code>/etc/rcS.d</code> in numerical order, The list in Swift is obtained by typing <code>cd /etc/rcS.d</code><ref>[http://www.yolinux.com/TUTORIALS/LinuxTutorialInitProcess.html Greg Ippolito, Linux Init Process/PC Boot Procedure, 2009, Last accessed: December 19, 2011]</ref>. The output is as follows:

	S09module-init-tools S15networking		S09module-init-tools S15networking

Mabadeer: /* Major package versions */

2011-12-19T22:35:41Z

Major package versions

← Older revision		Revision as of 22:35, 19 December 2011
Line 173:		Line 173:
	To report on the version numbers and upstream source for some of the major software packages included in Swift Linux as part of the standard install, we can find package resource, and download the associate version online, and use "diff" command to compare then:		To report on the version numbers and upstream source for some of the major software packages included in Swift Linux as part of the standard install, we can find package resource, and download the associate version online, and use "diff" command to compare then:

	Briefly, all the packages investigated were not the most stable version except for GTK+ and Shell. The most commonality among the packages included is that they are all light-weighted. Below we explore in details 10 of those packages.		Briefly, all the packages investigated were not the most stable version except for GTK+, APT and Shell. The most commonality among the packages included is that they are all light-weighted. Below we explore in details 10 of those packages.

	* '''Linux Kernel'''		* '''Linux Kernel'''
Line 203:		Line 203:
	* '''dpkg & apt'''		* '''dpkg & apt'''

	The distribution ~~in my laptop installed~~ dpkg, ~~whose version is~~ v1.16.0.2~~, However, the~~ latest stable version of dpkg ~~has updated to~~ v1.15.7.2, which is released in May, 2010. ~~and apt~~(advanced front-end for dpkg) is v0.8.14.1, the latest one. ~~This distribution~~ authors did not change much on dpkg and apt, ~~cause~~ it is core package management tool~~, no needs to do any updates~~. The dpkg itself is a low level tool, however, the APT ~~are~~ used to fetch packages from remote locations or deal with complex package relations, which are more commonly used than dpkg on its own, because they have a more sophisticated way of dealing with package relationships and a friendlier interface~~, these should be the reasons why distribution authors choose dpkg and apt to manage packages in SWIFT Linux~~.<ref>[http://en.wikipedia.org/wiki/Dpkg Wikipedia, dpkg - Wikipedia, the free encyclopedia, September 16, 2011, Last accessed: December 19, 2011]</ref>		The distribution comes with dpkg, v1.16.0.2. The latest stable version of dpkg is v1.15.7.2, which was released in May, 2010. APT (advanced front-end for dpkg) is v0.8.14.1, the latest one. Distribution authors did not change much on dpkg and apt, because it is core package management tool. The dpkg itself is a low level tool, however, the APT is used to fetch packages from remote locations or deal with complex package relations, which are more commonly used than dpkg on its own, because they have a more sophisticated way of dealing with package relationships and a friendlier interface.<ref>[http://en.wikipedia.org/wiki/Dpkg Wikipedia, dpkg - Wikipedia, the free encyclopedia, September 16, 2011, Last accessed: December 19, 2011]</ref>

	* '''iceape-browser'''		* '''iceape-browser'''
Line 209:		Line 209:
	[[File:SWIFT-web-browser.jpeg\|thumb\|Iceape-browser v2.0.13-1]]		[[File:SWIFT-web-browser.jpeg\|thumb\|Iceape-browser v2.0.13-1]]

	Iceape-browser v2.0.13-1 (2011 March) has been pre-installed in Swift. The version v2.0.14-9 was released recently. IceApe browser is distributed by the Debian project, it is based on [http://en.wikipedia.org/wiki/SeaMonkey SeaMonkey], however, it is not a stable and complex tool, and it lacks the development support within the Debian community. It is not commonly used by ~~really big~~ Linux distribution, but for a lightweight OS, it is good enough for Swift Linux thus the reason why it was chosen.		Iceape-browser v2.0.13-1 (2011 March) has been pre-installed in Swift. The version v2.0.14-9 was released recently. IceApe browser is distributed by the Debian project, it is based on [http://en.wikipedia.org/wiki/SeaMonkey SeaMonkey], however, it is not a stable and complex tool, and it lacks the development support within the Debian community. It is not commonly used by other major Linux distribution, but for a lightweight OS, it is good enough for Swift Linux thus the reason why it was chosen.

	* '''sylpheed'''		* '''sylpheed'''

	Swift Linux distribution chose sylpheed v3.2.0~beta1-1 as its light weight e-mail client with GTK+, it is released in July 1st, 2011. The latest development version is v3.2.0~beta-2 released in September 8th, 2011. So SWIFT Linux is taking the new version, Sylpheed is a free software distributed under the GNU GPL, and is designed for many platforms (Windows, Linux), so few changes needed to install Sylpheed to SWIFT Linux for distribution authors. Due to the Sylpheed is Lightweight operation and small, highly compatible, distribution authors ~~chosen~~ sylpheed for SWIFT Linux's standard install.		Swift Linux distribution chose sylpheed v3.2.0~beta1-1 as its light weight e-mail client with GTK+, it is released in July 1st, 2011. The latest development version is v3.2.0~beta-2 released in September 8th, 2011. So SWIFT Linux is taking the new version, Sylpheed is a free software distributed under the GNU GPL, and is designed for many platforms (Windows, Linux), so few changes needed to install Sylpheed to SWIFT Linux for distribution authors. Due to the Sylpheed is Lightweight operation and small, highly compatible, distribution authors chose sylpheed for SWIFT Linux's standard install.

	* '''netbase'''		* '''netbase'''

	Netbase is a basic TCP/IP networking system, Swift comes with v4.45. This version was released 6 months ago and the newest version 4.46 was released a month ago. The netbase provides the necessar infrastructure for basic TCP/IP based networking. Distribution authors removed some symlinks on upgrade, and change some commands as well. The netbase tool is also perfect choice for a lightweight OS like ~~SWIFT. So distribution authors chosen netbase as a standard install~~.		Netbase is a basic TCP/IP networking system, Swift comes with v4.45. This version was released 6 months ago and the newest version 4.46 was released a month ago. The netbase provides the necessar infrastructure for basic TCP/IP based networking. Distribution authors removed some symlinks on upgrade, and change some commands as well. The netbase tool is also perfect choice for a lightweight OS like Swift and that is why it was included.

	===Initialization===		===Initialization===

Mabadeer: /* Major package versions */

2011-12-19T22:30:25Z

Major package versions

← Older revision		Revision as of 22:30, 19 December 2011
Line 173:		Line 173:
	To report on the version numbers and upstream source for some of the major software packages included in Swift Linux as part of the standard install, we can find package resource, and download the associate version online, and use "diff" command to compare then:		To report on the version numbers and upstream source for some of the major software packages included in Swift Linux as part of the standard install, we can find package resource, and download the associate version online, and use "diff" command to compare then:

	Briefly, all the packages investigated were not the most stable version except for GTK+ and Shell. The most commonality among the packages included is that they are all light-weighted. Below we explore in ~~the~~ details 10 of those packages.		Briefly, all the packages investigated were not the most stable version except for GTK+ and Shell. The most commonality among the packages included is that they are all light-weighted. Below we explore in details 10 of those packages.

	* '''Linux Kernel'''		* '''Linux Kernel'''

Mabadeer: /* Initialization */

2011-12-19T22:24:25Z

Initialization

← Older revision		Revision as of 22:24, 19 December 2011
Line 225:		Line 225:
	First of all, BIOS is started as soon as the system is turned on to perform the basic initialization of the hardware, and then it hands control over to the boot loader, which will load the Swift system kernel image <code>/boot/vmlinuz</code> and root filesystem image <code>/boot/initrd.img</code>.		First of all, BIOS is started as soon as the system is turned on to perform the basic initialization of the hardware, and then it hands control over to the boot loader, which will load the Swift system kernel image <code>/boot/vmlinuz</code> and root filesystem image <code>/boot/initrd.img</code>.

	After that, the main boot process will be started by the init script <code>/sbin/init</code>. Swift will go into runlevel N (none) to initialize the system by scripts <code>/etc/inittab</code>, then the <code>inittab</code> script will direct the boot process to <code>/etc/init.d/rcS</code>. rcS in Swift is to call all S** scripts in <code>/etc/rcS.d</code> in numerical order, The list in Swift is obtained by typing <code>cd /etc/rcS.d</code><ref>[http://www.yolinux.com/TUTORIALS/LinuxTutorialInitProcess.html Linux ~~System Initialization~~]</ref>. The output is as follows:		After that, the main boot process will be started by the init script <code>/sbin/init</code>. Swift will go into runlevel N (none) to initialize the system by scripts <code>/etc/inittab</code>, then the <code>inittab</code> script will direct the boot process to <code>/etc/init.d/rcS</code>. rcS in Swift is to call all S** scripts in <code>/etc/rcS.d</code> in numerical order, The list in Swift is obtained by typing <code>cd /etc/rcS.d</code><ref>[http://www.yolinux.com/TUTORIALS/LinuxTutorialInitProcess.html Greg Ippolito, Linux Init Process/PC Boot Procedure, 2009, Last accessed: December 19, 2011]</ref>. The output is as follows:

	S09module-init-tools S15networking		S09module-init-tools S15networking