VectorLinux - Revision history

Judethedude: /* Background */

2011-12-19T23:41:20Z

Background

← Older revision		Revision as of 23:41, 19 December 2011
Line 15:		Line 15:


	VectorLinux is a Linux distribution designed for the x86 platform. It strives to diverge from other OS distributions by focusing its resources to speed, performance, and stability rather than visual display and graphics. It keeps everything as small as possible while letting the user decide what their operating system is going to be. Vector Linux can be used and enjoyed by a variety of users; however it is geared towards casual users with its ease and simplicity.<ref>[http://vectorlinux.com/table.php?distribution=vec vectorlinux.com: Goals]: Outlines the goals of VectorLinux from developers ~~persepctive~~ (Last accessed 2011-10-17).</ref> This OS distribution can be obtained by visiting the VectorLinux main website in the [http://vectorlinux.com/downloads Download page]. From the download menu the user has a choice between 4 different versions of the OS for specific uses. These include; SOHO edition (contains productivity applications – 1346.01MB in size), standard edition gold (most famous and most used – 699.57MB in size), Kde-classic edition (contains the basics of VectorLinux – 685.03MB in size), light edition (low memory requirements– 617.22MB in size). VectorLinux is derived from the [http://en.wikipedia.org/wiki/Slackware Slackware] Linux distribution, which is one of the earliest operating systems to be created on top of the Linux kernel.		VectorLinux is a Linux distribution designed for the x86 platform. It strives to diverge from other OS distributions by focusing its resources to speed, performance, and stability rather than visual display and graphics. It keeps everything as small as possible while letting the user decide what their operating system is going to be. Vector Linux can be used and enjoyed by a variety of users; however it is geared towards casual users with its ease and simplicity.<ref>[http://vectorlinux.com/table.php?distribution=vec vectorlinux.com: Goals]: Outlines the goals of VectorLinux from developers perspective (Last accessed 2011-10-17).</ref> This OS distribution can be obtained by visiting the VectorLinux main website in the [http://vectorlinux.com/downloads Download page]. From the download menu the user has a choice between 4 different versions of the OS for specific uses. These include; SOHO edition (contains productivity applications – 1346.01MB in size), standard edition gold (most famous and most used – 699.57MB in size), Kde-classic edition (contains the basics of VectorLinux – 685.03MB in size), light edition (low memory requirements– 617.22MB in size). VectorLinux is derived from the [http://en.wikipedia.org/wiki/Slackware Slackware] Linux distribution, which is one of the earliest operating systems to be created on top of the Linux kernel.
	<ref>[http://www.tuxmachines.org/node/24148/table.php?distribution=about tuxmachines.org: About]: Various details about Slackware OS (Last accessed 2011-10-18).</ref>		<ref>[http://www.tuxmachines.org/node/24148/table.php?distribution=about tuxmachines.org: About]: Various details about Slackware OS (Last accessed 2011-10-18).</ref>

Judethedude: /* Initialization */

2011-12-19T23:40:12Z

Initialization

← Older revision		Revision as of 23:40, 19 December 2011
Line 350:		Line 350:


	During VectorLinux boot-up, there are many processes that run during the login process in order to set up the system for start-up. First of all the kernel starts up and runs init or more specifically the script ''/sbin/init''. Init is in charge of starting all the background processes necessary for the system to run. These first scripts that run on init are the kill-scripts, these are the processes whose name start with a "K' when the command ps -A is entered, such as ksuspend_usbd. These scripts automatically kill (stop) processes that have unexpected behavior and are also used for system cleanup. For example '''ksuspend_usbd''' monitors the usb and suspends the usb subsystem when it's not being used. The next course of action carried out by init is to run the start scripts, these processes mostly start with the letter "S". This is done by init for every run level. Init runs the initialization script /etc/rc.d/rc.S which performs a variety of tasks such as mount file systems (/proc and sysfs, local system files), loads kernel modules, removes unnecessary files and sets the system time. The next script ''/etc/rc.d/rc.vlinit'' sets up and starts services with the particular run level that the system is being run on(some of these services are VectorLinux specific). <ref>[http://vlcore.vectorlinux.com/svn/vlcore/vlinit/etc/rc.d/rc.vlinit: code]: (Last accessed 2011-12-17).</ref> This script is responsible for the bulk of processes found during start-up, such as '''ata_aux'''(a hard drive controller), <ref>[-> http://ircanswers.com/ubuntu/525616/anyone-ata_aux-process-bandwidth-production: ata]_aux: (Last accessed 2011-12-17).</ref>'''cupsd'''( a common Unix printing system daemon). The process '''pdflush''' may also be used here a few times in order to write data out from dirty page caches(temporary storage used instead of writing the data) to disk when needed.<ref>[http://www.linuxask.com/questions/what-are-the-pdflush-processes: pdflush]: (Last accessed 2011-12-17).</ref> Note that you can switch run levels with the "init <run_level>" command. Afterwards the script ''/etc/rc.d/rc.local'' runs which performs tasks such as setting up the log in message, and setting up the Linux logo text found in /etc/issue. Init then forks a getty processes for each of the 6 virtual machines offered by VectorLinux. The Getty processes open tty lines for each console and sets their modes. Getty then prompts for the username and initiates the login process for that user by calling '''klogd''' ( the secured log in daemon) and '''syslogd''' (the log in application). '''Open SSH''' then runs which is a Secure Shell daemon that starts up a secure logging in process. SSH, which stands for Secure Shell, is a program for logging into a remote machine and for executing commands on a remote machine. It replaces '''rsh''' and '''rlogin''', and it provides secure encrypted communications between two un-trusted hosts over a network that is not secure. After the password is checked, the user's shell is started and most of the GUI processes are started such as xfce-4-panel (a bar which can hold many applications),'''xfce-4-session'''(allows the user to save sessions and restore them in terms of user accounts), and '''xfdesktop''' (provides the main functionality of the desktop)<ref>[http://www.xfce.org/projects/xfdesktop : xfdesktop]: (Last accessed 2011-12-17).</ref> .During the running of the user shell the script ''/etc/rc.d/rc.X'' runs which lunches the display manager, as long as the system is running in a GUI mode (user level 4 or 5).		During VectorLinux boot-up, there are many processes that run during the login process in order to set up the system for start-up. First of all the kernel starts up and runs init or more specifically the script ''/sbin/init''. Init is in charge of starting all the background processes necessary for the system to run. These first scripts that run on init are the kill-scripts, these are the processes whose name start with a "K' when the command ps -A is entered, such as ksuspend_usbd. These scripts automatically kill (stop) processes that have unexpected behavior and are also used for system cleanup. For example '''ksuspend_usbd''' monitors the usb and suspends the usb subsystem when it's not being used. The next course of action carried out by init is to run the start scripts, these processes mostly start with the letter "S". This is done by init for every run level. Init runs the initialization script /etc/rc.d/rc.S which performs a variety of tasks such as mount file systems (/proc and sysfs, local system files), loads kernel modules, removes unnecessary files and sets the system time. The next script ''/etc/rc.d/rc.vlinit'' sets up and starts services with the particular run level that the system is being run on(some of these services are VectorLinux specific). <ref>[http://vlcore.vectorlinux.com/svn/vlcore/vlinit/etc/rc.d/rc.vlinit: code]: Code of the script rc.vlinit (Last accessed 2011-12-17).</ref> This script is responsible for the bulk of processes found during start-up, such as '''ata_aux'''(a hard drive controller), <ref>[-> http://ircanswers.com/ubuntu/525616/anyone-ata_aux-process-bandwidth-production: ata]_aux: drive controller details(Last accessed 2011-12-17).</ref>'''cupsd'''( a common Unix printing system daemon). The process '''pdflush''' may also be used here a few times in order to write data out from dirty page caches(temporary storage used instead of writing the data) to disk when needed.<ref>[http://www.linuxask.com/questions/what-are-the-pdflush-processes: pdflush]: A forum on basic Linux questions (Last accessed 2011-12-17).</ref> Note that you can switch run levels with the "init <run_level>" command. Afterwards the script ''/etc/rc.d/rc.local'' runs which performs tasks such as setting up the log in message, and setting up the Linux logo text found in /etc/issue. Init then forks a getty processes for each of the 6 virtual machines offered by VectorLinux. The Getty processes open tty lines for each console and sets their modes. Getty then prompts for the username and initiates the login process for that user by calling '''klogd''' ( the secured log in daemon) and '''syslogd''' (the log in application). '''Open SSH''' then runs which is a Secure Shell daemon that starts up a secure logging in process. SSH, which stands for Secure Shell, is a program for logging into a remote machine and for executing commands on a remote machine. It replaces '''rsh''' and '''rlogin''', and it provides secure encrypted communications between two un-trusted hosts over a network that is not secure. After the password is checked, the user's shell is started and most of the GUI processes are started such as xfce-4-panel (a bar which can hold many applications),'''xfce-4-session'''(allows the user to save sessions and restore them in terms of user accounts), and '''xfdesktop''' (provides the main functionality of the desktop)<ref>[http://www.xfce.org/projects/xfdesktop : xfdesktop]: xfdesktop details (Last accessed 2011-12-17).</ref> .During the running of the user shell the script ''/etc/rc.d/rc.X'' runs which lunches the display manager, as long as the system is running in a GUI mode (user level 4 or 5).

Judethedude: /* Major package versions */

2011-12-19T23:37:20Z

Major package versions

← Older revision		Revision as of 23:37, 19 December 2011
Line 260:		Line 260:


	The version of the Linux Kernel included in the standard install of VectorLinux 6 was Released on July 29th 2010. Many versions of this kernel were later introduced, the latest stable version, version 3.1.1 was released on November 11th 2011. <ref> http://www.kernel.org/]: (Last accessed 2011-11-15).</ref> This package has also been lightly modified from the Linux kernel found in Slackware. One of which includes a major vulnerability fix in terms of Multiple Memory Access that was created in a previous modification found in the Slackware distribution. <ref> http://forum.vectorlinux.com/index.php?topic=10367.0]: (Last accessed 2011-11-15).</ref> Optimization fixes when extracting the kernel from Slackware were added and often needed due to the amount of programs installed on the system. Additional compatibility updates such as fixes that involve VectorLinux specific programs were also later implemented but these were often created by the community and must be downloaded separate from the standard install. <ref> http://forum.vectorlinux.com/index.php?board=5.0]: (Last accessed 2011-11-15).</ref> VectorLinux's main reason for inclusion is most likely because the kernel had previously been incorporated into Slackware which VectorLinux was based on and it had been the most stable Linux kernel at the time. Also note that VectorLinux version 7, (newly released) includes Linux Kernel: 3.0.8.		The version of the Linux Kernel included in the standard install of VectorLinux 6 was Released on July 29th 2010. Many versions of this kernel were later introduced, the latest stable version, version 3.1.1 was released on November 11th 2011. <ref> http://www.kernel.org/]: Info on Kernel releases (Last accessed 2011-11-15).</ref> This package has also been lightly modified from the Linux kernel found in Slackware. One of which includes a major vulnerability fix in terms of Multiple Memory Access that was created in a previous modification found in the Slackware distribution. <ref> http://forum.vectorlinux.com/index.php?topic=10367.0]: VectorLinux forum which discusses major kernel vulnerability (Last accessed 2011-11-15).</ref> Optimization fixes when extracting the kernel from Slackware were added and often needed due to the amount of programs installed on the system. Additional compatibility updates such as fixes that involve VectorLinux specific programs were also later implemented but these were often created by the community and must be downloaded separate from the standard install. <ref> http://forum.vectorlinux.com/index.php?board=5.0]: VectorLinux forum which contains optimized programs for VectorLinux (Last accessed 2011-11-15).</ref> VectorLinux's main reason for inclusion is most likely because the kernel had previously been incorporated into Slackware which VectorLinux was based on and it had been the most stable Linux kernel at the time. Also note that VectorLinux version 7, (newly released) includes Linux Kernel: 3.0.8.


	'''Glibc - 2.7:'''		'''Glibc - 2.7:'''

	Glibc 2.7 is included in the standard install of VectorLinux version 6 and released on the date of October 19th 2007. The most stable release of Glibc, version 2.14, was released on June 1st 2011.<ref> http://www.gnu.org/s/libc/]: (Last accessed 2011-11-15).</ref>		Glibc 2.7 is included in the standard install of VectorLinux version 6 and released on the date of October 19th 2007. The most stable release of Glibc, version 2.14, was released on June 1st 2011.<ref> http://www.gnu.org/s/libc/]: Glibc version history (Last accessed 2011-11-15).</ref>
	This package has been slightly tampered with as some regression issues have been addressed, from a previous modification of Glibc. <ref> http://forum.vectorlinux.com/index.php?topic=8199.0]: (Last accessed 2011-10-15).</ref> One can theorize that the inclusion of this package me have been based on the reason that it is a basic C library for UNIX or that it runs on the Linux kernel on x86 hardware		This package has been slightly tampered with as some regression issues have been addressed, from a previous modification of Glibc. <ref> http://forum.vectorlinux.com/index.php?topic=8199.0]: Discusses regression issues on Glibc (Last accessed 2011-10-15).</ref> One can theorize that the inclusion of this package me have been based on the reason that it is a basic C library for UNIX or that it runs on the Linux kernel on x86 hardware


Line 272:		Line 272:

	SeaMonkey 1.1.14 was released on the date of September 3rd 2009 and chosen to be part of the VectorLinux standard install. The latest stable release was on September 29th 2011 (version 2.4.1)		SeaMonkey 1.1.14 was released on the date of September 3rd 2009 and chosen to be part of the VectorLinux standard install. The latest stable release was on September 29th 2011 (version 2.4.1)
	<ref> http://www.seamonkey-project.org/releases/]: (Last accessed 2011-11-15).</ref> Modifications only include those that were added by the community as a separate download apart from the standard install. One of these additions include a subset of the shared libraries from Seamonkey		<ref> http://www.seamonkey-project.org/releases/]: Seamonkey main website (Last accessed 2011-11-15).</ref> Modifications only include those that were added by the community as a separate download apart from the standard install. One of these additions include a subset of the shared libraries from Seamonkey
	"seamonkey-solibs" to provide run-time support for programs that require nss, nspr, and		"seamonkey-solibs" to provide run-time support for programs that require nss, nspr, and
	seamonkey-solibs. This was done so the user would not need to install the package if they only needed run-time support. <ref> http://forum.vectorlinux.com/index.php?topic=15025.0]: (Last accessed 2011-11-15).</ref>. A basic reason for inclusion may be solely be for the purpose of a popular all in one Internet application		seamonkey-solibs. This was done so the user would not need to install the package if they only needed run-time support. <ref> http://forum.vectorlinux.com/index.php?topic=15025.0]: SeaMonkey on VectorLinux (Last accessed 2011-11-15).</ref>. A basic reason for inclusion may be solely be for the purpose of a popular all in one Internet application


Line 280:		Line 280:


	Xorg Server 1.4.2 was released on the date of June 11th 2008. The Latest stable version (version 1.11.2) was released on November 6th 2011 <ref> http://www.x.org/wiki/]: (Last accessed 2011-11-15).</ref>		Xorg Server 1.4.2 was released on the date of June 11th 2008. The Latest stable version (version 1.11.2) was released on November 6th 2011 <ref> http://www.x.org/wiki/]: Xorg version history on a wiki (Last accessed 2011-11-15).</ref>
	This package contains no modifications as it was probably not necessary, as stability issues may arise. Reasons for inclusion may only be that Xorg Server is a base for the graphical environment, for the computer and is fairly simple.		This package contains no modifications as it was probably not necessary, as stability issues may arise. Reasons for inclusion may only be that Xorg Server is a base for the graphical environment, for the computer and is fairly simple.

Line 286:		Line 286:
	'''Bash - 3.1:'''		'''Bash - 3.1:'''

	Bash 3.1 was released on the date of April 12th 2006 and included in the standard install of VectorLinux. The latest stable release, version 4.2, was released on May 3rd 2011 and is now incorporated as a separate download for both VectorLinux 6 as well as 7. Minor modifications includes a number of bug fixes and a few minor changes. One of these altercations include "+=" was permitted in places where previously only "=" assignment was recognized. <ref> http://tldp.org/LDP/abs/html/bashver3.html]: (Last accessed 2011-11-15).</ref> Reasons for inclusion can be hypothesized as this package being a basic command processor that allows the user to type commands that cause action.		Bash 3.1 was released on the date of April 12th 2006 and included in the standard install of VectorLinux. The latest stable release, version 4.2, was released on May 3rd 2011 and is now incorporated as a separate download for both VectorLinux 6 as well as 7. Minor modifications includes a number of bug fixes and a few minor changes. One of these altercations include "+=" was permitted in places where previously only "=" assignment was recognized. <ref> http://tldp.org/LDP/abs/html/bashver3.html]: alterations to Bash (Last accessed 2011-11-15).</ref> Reasons for inclusion can be hypothesized as this package being a basic command processor that allows the user to type commands that cause action.


Line 294:		Line 294:
	Gtk+ 2.12.9 was released on the date of September 14th 2007 and can be found bundled with version 6 of the standard VectorLinux install. The latest stable release (version 3.2.2) came out on September 25 2011. No alterations or fixes have been made on this package.		Gtk+ 2.12.9 was released on the date of September 14th 2007 and can be found bundled with version 6 of the standard VectorLinux install. The latest stable release (version 3.2.2) came out on September 25 2011. No alterations or fixes have been made on this package.
	The main reason for inclusion is that this package creates a graphical user interface and thus a key component to VectorLinux's graphic infrastructure. Additionally Gtk+ is an essential dependency for the xfdesktop and therefore must be included in order to make use of the xfdesktop. <ref> http://www.xfce.org/about/releasemodel		The main reason for inclusion is that this package creates a graphical user interface and thus a key component to VectorLinux's graphic infrastructure. Additionally Gtk+ is an essential dependency for the xfdesktop and therefore must be included in order to make use of the xfdesktop. <ref> http://www.xfce.org/about/releasemodel
	]: (Last accessed 2011-11-15).</ref>		]: Basic information on xfdesktop found in there main website(Last accessed 2011-11-15).</ref>

Judethedude: /* Installation/Startup */

2011-12-19T23:31:39Z

Installation/Startup

← Older revision		Revision as of 23:31, 19 December 2011
Line 95:		Line 95:


	* Note that during the VectorLinux installation, if the user encounters an error during the installation, the whole thing will crash, so it is advisable not to do too much manual modifications if one does not know what he/she is doing <ref>[http://forum.vectorlinux.com/index.php?topic=8309.15=bugs vectorlinux.com: Bugs]: (Last accessed 2011-10-17).</ref>		* Note that during the VectorLinux installation, if the user encounters an error during the installation, the whole thing will crash, so it is advisable not to do too much manual modifications if one does not know what he/she is doing <ref>[http://forum.vectorlinux.com/index.php?topic=8309.15=bugs vectorlinux.com: Bugs]: Various bugs of VectorLinux discussed on its forum (Last accessed 2011-10-17).</ref>

	===Basic Operation===		===Basic Operation===

Judethedude: /* Background */

2011-12-19T23:29:56Z

Background

← Older revision		Revision as of 23:29, 19 December 2011
Line 16:		Line 16:

	VectorLinux is a Linux distribution designed for the x86 platform. It strives to diverge from other OS distributions by focusing its resources to speed, performance, and stability rather than visual display and graphics. It keeps everything as small as possible while letting the user decide what their operating system is going to be. Vector Linux can be used and enjoyed by a variety of users; however it is geared towards casual users with its ease and simplicity.<ref>[http://vectorlinux.com/table.php?distribution=vec vectorlinux.com: Goals]: Outlines the goals of VectorLinux from developers persepctive (Last accessed 2011-10-17).</ref> This OS distribution can be obtained by visiting the VectorLinux main website in the [http://vectorlinux.com/downloads Download page]. From the download menu the user has a choice between 4 different versions of the OS for specific uses. These include; SOHO edition (contains productivity applications – 1346.01MB in size), standard edition gold (most famous and most used – 699.57MB in size), Kde-classic edition (contains the basics of VectorLinux – 685.03MB in size), light edition (low memory requirements– 617.22MB in size). VectorLinux is derived from the [http://en.wikipedia.org/wiki/Slackware Slackware] Linux distribution, which is one of the earliest operating systems to be created on top of the Linux kernel.		VectorLinux is a Linux distribution designed for the x86 platform. It strives to diverge from other OS distributions by focusing its resources to speed, performance, and stability rather than visual display and graphics. It keeps everything as small as possible while letting the user decide what their operating system is going to be. Vector Linux can be used and enjoyed by a variety of users; however it is geared towards casual users with its ease and simplicity.<ref>[http://vectorlinux.com/table.php?distribution=vec vectorlinux.com: Goals]: Outlines the goals of VectorLinux from developers persepctive (Last accessed 2011-10-17).</ref> This OS distribution can be obtained by visiting the VectorLinux main website in the [http://vectorlinux.com/downloads Download page]. From the download menu the user has a choice between 4 different versions of the OS for specific uses. These include; SOHO edition (contains productivity applications – 1346.01MB in size), standard edition gold (most famous and most used – 699.57MB in size), Kde-classic edition (contains the basics of VectorLinux – 685.03MB in size), light edition (low memory requirements– 617.22MB in size). VectorLinux is derived from the [http://en.wikipedia.org/wiki/Slackware Slackware] Linux distribution, which is one of the earliest operating systems to be created on top of the Linux kernel.
	<ref>[http://www.tuxmachines.org/node/24148/table.php?distribution=about tuxmachines.org: About]: (Last accessed 2011-10-18).</ref>		<ref>[http://www.tuxmachines.org/node/24148/table.php?distribution=about tuxmachines.org: About]: Various details about Slackware OS (Last accessed 2011-10-18).</ref>

	===Installation/Startup===		===Installation/Startup===

Judethedude: /* Background */

2011-12-19T23:28:25Z

Background

← Older revision		Revision as of 23:28, 19 December 2011
Line 15:		Line 15:


	VectorLinux is a Linux distribution designed for the x86 platform. It strives to diverge from other OS distributions by focusing its resources to speed, performance, and stability rather than visual display and graphics. It keeps everything as small as possible while letting the user decide what their operating system is going to be. Vector Linux can be used and enjoyed by a variety of users; however it is geared towards casual users with its ease and simplicity.<ref>[http://vectorlinux.com/table.php?distribution=vec vectorlinux.com: Goals]: (Last accessed 2011-10-17).</ref> This OS distribution can be obtained by visiting the VectorLinux main website in the [http://vectorlinux.com/downloads Download page]. From the download menu the user has a choice between 4 different versions of the OS for specific uses. These include; SOHO edition (contains productivity applications – 1346.01MB in size), standard edition gold (most famous and most used – 699.57MB in size), Kde-classic edition (contains the basics of VectorLinux – 685.03MB in size), light edition (low memory requirements– 617.22MB in size). VectorLinux is derived from the [http://en.wikipedia.org/wiki/Slackware Slackware] Linux distribution, which is one of the earliest operating systems to be created on top of the Linux kernel.		VectorLinux is a Linux distribution designed for the x86 platform. It strives to diverge from other OS distributions by focusing its resources to speed, performance, and stability rather than visual display and graphics. It keeps everything as small as possible while letting the user decide what their operating system is going to be. Vector Linux can be used and enjoyed by a variety of users; however it is geared towards casual users with its ease and simplicity.<ref>[http://vectorlinux.com/table.php?distribution=vec vectorlinux.com: Goals]: Outlines the goals of VectorLinux from developers persepctive (Last accessed 2011-10-17).</ref> This OS distribution can be obtained by visiting the VectorLinux main website in the [http://vectorlinux.com/downloads Download page]. From the download menu the user has a choice between 4 different versions of the OS for specific uses. These include; SOHO edition (contains productivity applications – 1346.01MB in size), standard edition gold (most famous and most used – 699.57MB in size), Kde-classic edition (contains the basics of VectorLinux – 685.03MB in size), light edition (low memory requirements– 617.22MB in size). VectorLinux is derived from the [http://en.wikipedia.org/wiki/Slackware Slackware] Linux distribution, which is one of the earliest operating systems to be created on top of the Linux kernel.
	<ref>[http://www.tuxmachines.org/node/24148/table.php?distribution=about tuxmachines.org: About]: (Last accessed 2011-10-18).</ref>		<ref>[http://www.tuxmachines.org/node/24148/table.php?distribution=about tuxmachines.org: About]: (Last accessed 2011-10-18).</ref>

Judethedude: /* Initialization */

2011-12-19T22:15:12Z

Initialization

← Older revision		Revision as of 22:15, 19 December 2011
Line 352:		Line 352:
	During VectorLinux boot-up, there are many processes that run during the login process in order to set up the system for start-up. First of all the kernel starts up and runs init or more specifically the script ''/sbin/init''. Init is in charge of starting all the background processes necessary for the system to run. These first scripts that run on init are the kill-scripts, these are the processes whose name start with a "K' when the command ps -A is entered, such as ksuspend_usbd. These scripts automatically kill (stop) processes that have unexpected behavior and are also used for system cleanup. For example '''ksuspend_usbd''' monitors the usb and suspends the usb subsystem when it's not being used. The next course of action carried out by init is to run the start scripts, these processes mostly start with the letter "S". This is done by init for every run level. Init runs the initialization script /etc/rc.d/rc.S which performs a variety of tasks such as mount file systems (/proc and sysfs, local system files), loads kernel modules, removes unnecessary files and sets the system time. The next script ''/etc/rc.d/rc.vlinit'' sets up and starts services with the particular run level that the system is being run on(some of these services are VectorLinux specific). <ref>[http://vlcore.vectorlinux.com/svn/vlcore/vlinit/etc/rc.d/rc.vlinit: code]: (Last accessed 2011-12-17).</ref> This script is responsible for the bulk of processes found during start-up, such as '''ata_aux'''(a hard drive controller), <ref>[-> http://ircanswers.com/ubuntu/525616/anyone-ata_aux-process-bandwidth-production: ata]_aux: (Last accessed 2011-12-17).</ref>'''cupsd'''( a common Unix printing system daemon). The process '''pdflush''' may also be used here a few times in order to write data out from dirty page caches(temporary storage used instead of writing the data) to disk when needed.<ref>[http://www.linuxask.com/questions/what-are-the-pdflush-processes: pdflush]: (Last accessed 2011-12-17).</ref> Note that you can switch run levels with the "init <run_level>" command. Afterwards the script ''/etc/rc.d/rc.local'' runs which performs tasks such as setting up the log in message, and setting up the Linux logo text found in /etc/issue. Init then forks a getty processes for each of the 6 virtual machines offered by VectorLinux. The Getty processes open tty lines for each console and sets their modes. Getty then prompts for the username and initiates the login process for that user by calling '''klogd''' ( the secured log in daemon) and '''syslogd''' (the log in application). '''Open SSH''' then runs which is a Secure Shell daemon that starts up a secure logging in process. SSH, which stands for Secure Shell, is a program for logging into a remote machine and for executing commands on a remote machine. It replaces '''rsh''' and '''rlogin''', and it provides secure encrypted communications between two un-trusted hosts over a network that is not secure. After the password is checked, the user's shell is started and most of the GUI processes are started such as xfce-4-panel (a bar which can hold many applications),'''xfce-4-session'''(allows the user to save sessions and restore them in terms of user accounts), and '''xfdesktop''' (provides the main functionality of the desktop)<ref>[http://www.xfce.org/projects/xfdesktop : xfdesktop]: (Last accessed 2011-12-17).</ref> .During the running of the user shell the script ''/etc/rc.d/rc.X'' runs which lunches the display manager, as long as the system is running in a GUI mode (user level 4 or 5).		During VectorLinux boot-up, there are many processes that run during the login process in order to set up the system for start-up. First of all the kernel starts up and runs init or more specifically the script ''/sbin/init''. Init is in charge of starting all the background processes necessary for the system to run. These first scripts that run on init are the kill-scripts, these are the processes whose name start with a "K' when the command ps -A is entered, such as ksuspend_usbd. These scripts automatically kill (stop) processes that have unexpected behavior and are also used for system cleanup. For example '''ksuspend_usbd''' monitors the usb and suspends the usb subsystem when it's not being used. The next course of action carried out by init is to run the start scripts, these processes mostly start with the letter "S". This is done by init for every run level. Init runs the initialization script /etc/rc.d/rc.S which performs a variety of tasks such as mount file systems (/proc and sysfs, local system files), loads kernel modules, removes unnecessary files and sets the system time. The next script ''/etc/rc.d/rc.vlinit'' sets up and starts services with the particular run level that the system is being run on(some of these services are VectorLinux specific). <ref>[http://vlcore.vectorlinux.com/svn/vlcore/vlinit/etc/rc.d/rc.vlinit: code]: (Last accessed 2011-12-17).</ref> This script is responsible for the bulk of processes found during start-up, such as '''ata_aux'''(a hard drive controller), <ref>[-> http://ircanswers.com/ubuntu/525616/anyone-ata_aux-process-bandwidth-production: ata]_aux: (Last accessed 2011-12-17).</ref>'''cupsd'''( a common Unix printing system daemon). The process '''pdflush''' may also be used here a few times in order to write data out from dirty page caches(temporary storage used instead of writing the data) to disk when needed.<ref>[http://www.linuxask.com/questions/what-are-the-pdflush-processes: pdflush]: (Last accessed 2011-12-17).</ref> Note that you can switch run levels with the "init <run_level>" command. Afterwards the script ''/etc/rc.d/rc.local'' runs which performs tasks such as setting up the log in message, and setting up the Linux logo text found in /etc/issue. Init then forks a getty processes for each of the 6 virtual machines offered by VectorLinux. The Getty processes open tty lines for each console and sets their modes. Getty then prompts for the username and initiates the login process for that user by calling '''klogd''' ( the secured log in daemon) and '''syslogd''' (the log in application). '''Open SSH''' then runs which is a Secure Shell daemon that starts up a secure logging in process. SSH, which stands for Secure Shell, is a program for logging into a remote machine and for executing commands on a remote machine. It replaces '''rsh''' and '''rlogin''', and it provides secure encrypted communications between two un-trusted hosts over a network that is not secure. After the password is checked, the user's shell is started and most of the GUI processes are started such as xfce-4-panel (a bar which can hold many applications),'''xfce-4-session'''(allows the user to save sessions and restore them in terms of user accounts), and '''xfdesktop''' (provides the main functionality of the desktop)<ref>[http://www.xfce.org/projects/xfdesktop : xfdesktop]: (Last accessed 2011-12-17).</ref> .During the running of the user shell the script ''/etc/rc.d/rc.X'' runs which lunches the display manager, as long as the system is running in a GUI mode (user level 4 or 5).

	~~[[File:processes.jpg\|450px\|thumb\|center\|''''' VectorLinux's processes.]]~~

			Here is the lists of processes running in the start-up of VectorLinux. One can find these processes by accessing the terminal and typing in the command "ps -A". Note that to view the kernel threads one must use the command "ps -ef", which lists the processes as well as the kernel threads.

	~~[[File:kernel threads.jpg\|450px\|thumb\|center\|''''' VectorLinux's processes.]]~~

			[[File:processes.jpg\|450px\|thumb\|center\|''''' VectorLinux's processes.]]

	~~Here is the lists of processes running in the start-up of VectorLinux. One can find these processes by accessing the terminal and typing in the command "ps -A". Note that to view the~~ kernel threads ~~one must use the command "ps -ef", which lists the processes as well as the~~ kernel threads.
			[[File:kernel threads.jpg\|450px\|thumb\|center\|''''' VectorLinux's kernel threads.]]

	===References ===		===References ===
	----		----
	<references />		<references />

Judethedude: /* Initialization */

2011-12-19T22:14:12Z

Initialization

← Older revision		Revision as of 22:14, 19 December 2011
Line 352:		Line 352:
	During VectorLinux boot-up, there are many processes that run during the login process in order to set up the system for start-up. First of all the kernel starts up and runs init or more specifically the script ''/sbin/init''. Init is in charge of starting all the background processes necessary for the system to run. These first scripts that run on init are the kill-scripts, these are the processes whose name start with a "K' when the command ps -A is entered, such as ksuspend_usbd. These scripts automatically kill (stop) processes that have unexpected behavior and are also used for system cleanup. For example '''ksuspend_usbd''' monitors the usb and suspends the usb subsystem when it's not being used. The next course of action carried out by init is to run the start scripts, these processes mostly start with the letter "S". This is done by init for every run level. Init runs the initialization script /etc/rc.d/rc.S which performs a variety of tasks such as mount file systems (/proc and sysfs, local system files), loads kernel modules, removes unnecessary files and sets the system time. The next script ''/etc/rc.d/rc.vlinit'' sets up and starts services with the particular run level that the system is being run on(some of these services are VectorLinux specific). <ref>[http://vlcore.vectorlinux.com/svn/vlcore/vlinit/etc/rc.d/rc.vlinit: code]: (Last accessed 2011-12-17).</ref> This script is responsible for the bulk of processes found during start-up, such as '''ata_aux'''(a hard drive controller), <ref>[-> http://ircanswers.com/ubuntu/525616/anyone-ata_aux-process-bandwidth-production: ata]_aux: (Last accessed 2011-12-17).</ref>'''cupsd'''( a common Unix printing system daemon). The process '''pdflush''' may also be used here a few times in order to write data out from dirty page caches(temporary storage used instead of writing the data) to disk when needed.<ref>[http://www.linuxask.com/questions/what-are-the-pdflush-processes: pdflush]: (Last accessed 2011-12-17).</ref> Note that you can switch run levels with the "init <run_level>" command. Afterwards the script ''/etc/rc.d/rc.local'' runs which performs tasks such as setting up the log in message, and setting up the Linux logo text found in /etc/issue. Init then forks a getty processes for each of the 6 virtual machines offered by VectorLinux. The Getty processes open tty lines for each console and sets their modes. Getty then prompts for the username and initiates the login process for that user by calling '''klogd''' ( the secured log in daemon) and '''syslogd''' (the log in application). '''Open SSH''' then runs which is a Secure Shell daemon that starts up a secure logging in process. SSH, which stands for Secure Shell, is a program for logging into a remote machine and for executing commands on a remote machine. It replaces '''rsh''' and '''rlogin''', and it provides secure encrypted communications between two un-trusted hosts over a network that is not secure. After the password is checked, the user's shell is started and most of the GUI processes are started such as xfce-4-panel (a bar which can hold many applications),'''xfce-4-session'''(allows the user to save sessions and restore them in terms of user accounts), and '''xfdesktop''' (provides the main functionality of the desktop)<ref>[http://www.xfce.org/projects/xfdesktop : xfdesktop]: (Last accessed 2011-12-17).</ref> .During the running of the user shell the script ''/etc/rc.d/rc.X'' runs which lunches the display manager, as long as the system is running in a GUI mode (user level 4 or 5).		During VectorLinux boot-up, there are many processes that run during the login process in order to set up the system for start-up. First of all the kernel starts up and runs init or more specifically the script ''/sbin/init''. Init is in charge of starting all the background processes necessary for the system to run. These first scripts that run on init are the kill-scripts, these are the processes whose name start with a "K' when the command ps -A is entered, such as ksuspend_usbd. These scripts automatically kill (stop) processes that have unexpected behavior and are also used for system cleanup. For example '''ksuspend_usbd''' monitors the usb and suspends the usb subsystem when it's not being used. The next course of action carried out by init is to run the start scripts, these processes mostly start with the letter "S". This is done by init for every run level. Init runs the initialization script /etc/rc.d/rc.S which performs a variety of tasks such as mount file systems (/proc and sysfs, local system files), loads kernel modules, removes unnecessary files and sets the system time. The next script ''/etc/rc.d/rc.vlinit'' sets up and starts services with the particular run level that the system is being run on(some of these services are VectorLinux specific). <ref>[http://vlcore.vectorlinux.com/svn/vlcore/vlinit/etc/rc.d/rc.vlinit: code]: (Last accessed 2011-12-17).</ref> This script is responsible for the bulk of processes found during start-up, such as '''ata_aux'''(a hard drive controller), <ref>[-> http://ircanswers.com/ubuntu/525616/anyone-ata_aux-process-bandwidth-production: ata]_aux: (Last accessed 2011-12-17).</ref>'''cupsd'''( a common Unix printing system daemon). The process '''pdflush''' may also be used here a few times in order to write data out from dirty page caches(temporary storage used instead of writing the data) to disk when needed.<ref>[http://www.linuxask.com/questions/what-are-the-pdflush-processes: pdflush]: (Last accessed 2011-12-17).</ref> Note that you can switch run levels with the "init <run_level>" command. Afterwards the script ''/etc/rc.d/rc.local'' runs which performs tasks such as setting up the log in message, and setting up the Linux logo text found in /etc/issue. Init then forks a getty processes for each of the 6 virtual machines offered by VectorLinux. The Getty processes open tty lines for each console and sets their modes. Getty then prompts for the username and initiates the login process for that user by calling '''klogd''' ( the secured log in daemon) and '''syslogd''' (the log in application). '''Open SSH''' then runs which is a Secure Shell daemon that starts up a secure logging in process. SSH, which stands for Secure Shell, is a program for logging into a remote machine and for executing commands on a remote machine. It replaces '''rsh''' and '''rlogin''', and it provides secure encrypted communications between two un-trusted hosts over a network that is not secure. After the password is checked, the user's shell is started and most of the GUI processes are started such as xfce-4-panel (a bar which can hold many applications),'''xfce-4-session'''(allows the user to save sessions and restore them in terms of user accounts), and '''xfdesktop''' (provides the main functionality of the desktop)<ref>[http://www.xfce.org/projects/xfdesktop : xfdesktop]: (Last accessed 2011-12-17).</ref> .During the running of the user shell the script ''/etc/rc.d/rc.X'' runs which lunches the display manager, as long as the system is running in a GUI mode (user level 4 or 5).

	~~Here is the lists of~~ processes ~~running in the start-up of~~ VectorLinux~~. One can find these processes by accessing the terminal and typing in the command "ps -A". Note that to view the kernel threads one must use the command "ps -ef", which lists the~~ processes ~~as well as the kernel threads~~.		[[File:processes.jpg\|450px\|thumb\|center\|''''' VectorLinux's processes.]]


	[[File:~~processes~~.jpg\|450px\|thumb\|~~right~~\|''''' VectorLinux's processes.]]		[[File:kernel threads.jpg\|450px\|thumb\|center\|''''' VectorLinux's processes.]]


	~~[[File:~~kernel threads~~.jpg\|450px\|thumb\|right\|''''' VectorLinux's~~ processes.]]		Here is the lists of processes running in the start-up of VectorLinux. One can find these processes by accessing the terminal and typing in the command "ps -A". Note that to view the kernel threads one must use the command "ps -ef", which lists the processes as well as the kernel threads.

	===References ===		===References ===
	----		----
	<references />		<references />

Judethedude: /* Initialization */

2011-12-19T22:12:40Z

Initialization

← Older revision		Revision as of 22:12, 19 December 2011
Line 353:		Line 353:

	Here is the lists of processes running in the start-up of VectorLinux. One can find these processes by accessing the terminal and typing in the command "ps -A". Note that to view the kernel threads one must use the command "ps -ef", which lists the processes as well as the kernel threads.		Here is the lists of processes running in the start-up of VectorLinux. One can find these processes by accessing the terminal and typing in the command "ps -A". Note that to view the kernel threads one must use the command "ps -ef", which lists the processes as well as the kernel threads.


			[[File:processes.jpg\|450px\|thumb\|right\|''''' VectorLinux's processes.]]


			[[File:kernel threads.jpg\|450px\|thumb\|right\|''''' VectorLinux's processes.]]

	===References ===		===References ===
	----		----
	<references />		<references />

Judethedude: /* Initialization */

2011-12-19T22:09:46Z

Initialization

← Older revision		Revision as of 22:09, 19 December 2011
Line 351:		Line 351:

	During VectorLinux boot-up, there are many processes that run during the login process in order to set up the system for start-up. First of all the kernel starts up and runs init or more specifically the script ''/sbin/init''. Init is in charge of starting all the background processes necessary for the system to run. These first scripts that run on init are the kill-scripts, these are the processes whose name start with a "K' when the command ps -A is entered, such as ksuspend_usbd. These scripts automatically kill (stop) processes that have unexpected behavior and are also used for system cleanup. For example '''ksuspend_usbd''' monitors the usb and suspends the usb subsystem when it's not being used. The next course of action carried out by init is to run the start scripts, these processes mostly start with the letter "S". This is done by init for every run level. Init runs the initialization script /etc/rc.d/rc.S which performs a variety of tasks such as mount file systems (/proc and sysfs, local system files), loads kernel modules, removes unnecessary files and sets the system time. The next script ''/etc/rc.d/rc.vlinit'' sets up and starts services with the particular run level that the system is being run on(some of these services are VectorLinux specific). <ref>[http://vlcore.vectorlinux.com/svn/vlcore/vlinit/etc/rc.d/rc.vlinit: code]: (Last accessed 2011-12-17).</ref> This script is responsible for the bulk of processes found during start-up, such as '''ata_aux'''(a hard drive controller), <ref>[-> http://ircanswers.com/ubuntu/525616/anyone-ata_aux-process-bandwidth-production: ata]_aux: (Last accessed 2011-12-17).</ref>'''cupsd'''( a common Unix printing system daemon). The process '''pdflush''' may also be used here a few times in order to write data out from dirty page caches(temporary storage used instead of writing the data) to disk when needed.<ref>[http://www.linuxask.com/questions/what-are-the-pdflush-processes: pdflush]: (Last accessed 2011-12-17).</ref> Note that you can switch run levels with the "init <run_level>" command. Afterwards the script ''/etc/rc.d/rc.local'' runs which performs tasks such as setting up the log in message, and setting up the Linux logo text found in /etc/issue. Init then forks a getty processes for each of the 6 virtual machines offered by VectorLinux. The Getty processes open tty lines for each console and sets their modes. Getty then prompts for the username and initiates the login process for that user by calling '''klogd''' ( the secured log in daemon) and '''syslogd''' (the log in application). '''Open SSH''' then runs which is a Secure Shell daemon that starts up a secure logging in process. SSH, which stands for Secure Shell, is a program for logging into a remote machine and for executing commands on a remote machine. It replaces '''rsh''' and '''rlogin''', and it provides secure encrypted communications between two un-trusted hosts over a network that is not secure. After the password is checked, the user's shell is started and most of the GUI processes are started such as xfce-4-panel (a bar which can hold many applications),'''xfce-4-session'''(allows the user to save sessions and restore them in terms of user accounts), and '''xfdesktop''' (provides the main functionality of the desktop)<ref>[http://www.xfce.org/projects/xfdesktop : xfdesktop]: (Last accessed 2011-12-17).</ref> .During the running of the user shell the script ''/etc/rc.d/rc.X'' runs which lunches the display manager, as long as the system is running in a GUI mode (user level 4 or 5).		During VectorLinux boot-up, there are many processes that run during the login process in order to set up the system for start-up. First of all the kernel starts up and runs init or more specifically the script ''/sbin/init''. Init is in charge of starting all the background processes necessary for the system to run. These first scripts that run on init are the kill-scripts, these are the processes whose name start with a "K' when the command ps -A is entered, such as ksuspend_usbd. These scripts automatically kill (stop) processes that have unexpected behavior and are also used for system cleanup. For example '''ksuspend_usbd''' monitors the usb and suspends the usb subsystem when it's not being used. The next course of action carried out by init is to run the start scripts, these processes mostly start with the letter "S". This is done by init for every run level. Init runs the initialization script /etc/rc.d/rc.S which performs a variety of tasks such as mount file systems (/proc and sysfs, local system files), loads kernel modules, removes unnecessary files and sets the system time. The next script ''/etc/rc.d/rc.vlinit'' sets up and starts services with the particular run level that the system is being run on(some of these services are VectorLinux specific). <ref>[http://vlcore.vectorlinux.com/svn/vlcore/vlinit/etc/rc.d/rc.vlinit: code]: (Last accessed 2011-12-17).</ref> This script is responsible for the bulk of processes found during start-up, such as '''ata_aux'''(a hard drive controller), <ref>[-> http://ircanswers.com/ubuntu/525616/anyone-ata_aux-process-bandwidth-production: ata]_aux: (Last accessed 2011-12-17).</ref>'''cupsd'''( a common Unix printing system daemon). The process '''pdflush''' may also be used here a few times in order to write data out from dirty page caches(temporary storage used instead of writing the data) to disk when needed.<ref>[http://www.linuxask.com/questions/what-are-the-pdflush-processes: pdflush]: (Last accessed 2011-12-17).</ref> Note that you can switch run levels with the "init <run_level>" command. Afterwards the script ''/etc/rc.d/rc.local'' runs which performs tasks such as setting up the log in message, and setting up the Linux logo text found in /etc/issue. Init then forks a getty processes for each of the 6 virtual machines offered by VectorLinux. The Getty processes open tty lines for each console and sets their modes. Getty then prompts for the username and initiates the login process for that user by calling '''klogd''' ( the secured log in daemon) and '''syslogd''' (the log in application). '''Open SSH''' then runs which is a Secure Shell daemon that starts up a secure logging in process. SSH, which stands for Secure Shell, is a program for logging into a remote machine and for executing commands on a remote machine. It replaces '''rsh''' and '''rlogin''', and it provides secure encrypted communications between two un-trusted hosts over a network that is not secure. After the password is checked, the user's shell is started and most of the GUI processes are started such as xfce-4-panel (a bar which can hold many applications),'''xfce-4-session'''(allows the user to save sessions and restore them in terms of user accounts), and '''xfdesktop''' (provides the main functionality of the desktop)<ref>[http://www.xfce.org/projects/xfdesktop : xfdesktop]: (Last accessed 2011-12-17).</ref> .During the running of the user shell the script ''/etc/rc.d/rc.X'' runs which lunches the display manager, as long as the system is running in a GUI mode (user level 4 or 5).

			Here is the lists of processes running in the start-up of VectorLinux. One can find these processes by accessing the terminal and typing in the command "ps -A". Note that to view the kernel threads one must use the command "ps -ef", which lists the processes as well as the kernel threads.

	===References ===		===References ===
	----		----
	<references />		<references />