COMP 3000 2011 Report: APODIO - Revision history

Mbrowna: /* System Initialization */

2011-12-19T22:30:33Z

System Initialization

← Older revision		Revision as of 22:30, 19 December 2011
Line 261:		Line 261:

	/etc/rcS.d/S*		/etc/rcS.d/S*
	S13pcmciautils		S13pcmciautils // Service that provides support for PCMCIA hardware for systems with Linux 2.6.13-rc1 or later.
	S25brltty		S25brltty // Provides access to braille terminals (braille terminal driver).
	S37apparmor		S37apparmor // Script in charge of loading all AppArmor profiles.
	S46-lm-sensors		S46-lm-sensors // Everything to do with monitoring hardware health.
	S55urandom		S55urandom // In charge of saving the random seed (when booting, halting, and restarting).
	S70x11-common		S70x11-common // Sets up the X Server, as well as the ICE socket directories.

	At this point, the appropriate run level scripts are run (<code>/etc/rc[run-level].d/</code>). All of the scripts that start with <code>SXX</code> (where <code>XX</code> is a number for distinguishing order) within <code>/etc/rc2.d/</code> will have been executed (as this is the basic, multi-user mode, run level 2):		At this point, the appropriate run level scripts are run (<code>/etc/rc[run-level].d/</code>). All of the scripts that start with <code>SXX</code> (where <code>XX</code> is a number for distinguishing order) within <code>/etc/rc2.d/</code> will have been executed (as this is the basic, multi-user mode, run level 2):

Mbrowna at 22:13, 19 December 2011

2011-12-19T22:13:49Z

Mbrowna: /* System Initialization */

2011-12-19T06:23:40Z

System Initialization

← Older revision		Revision as of 06:23, 19 December 2011
Line 285:		Line 285:

	[[File:Apodio_pstree.png\|thumb\|right\|'''(Figure 10)''' Process tree (by running <code>pstree</code>)]]		[[File:Apodio_pstree.png\|thumb\|right\|'''(Figure 10)''' Process tree (by running <code>pstree</code>)]]
	The process tree depicts information about all currently active processes, and the parent-child relationship between them ('''Figure 10'''). The process tree can be loaded via the terminal by typing in the following command:		Upon logging in, all of the needed processes are running. The process tree depicts information about all currently active processes, and the parent-child relationship between them ('''Figure 10'''). The process tree can be loaded via the terminal by typing in the following command:

	$ pstree		$ pstree
Line 368:		Line 368:
	└─wpa_supplicant		└─wpa_supplicant

	Details on a few of the major processes are listed below.		The process tree above shows all of the active processes when the system is booted-up and logged in ('''fully initialized'''). Details on a few of the major processes (and how they are initialized) are listed below:

	<table style="width: 100%;" border="1" cellpadding="4" cellspacing="0">		<table style="width: 100%;" border="1" cellpadding="4" cellspacing="0">
Line 413:		Line 413:
	</tr>		</tr>
	</table>		</table>


	Some outlying scripts remain (that don't necessarily have a process running when logged in):		Some outlying scripts remain (that don't necessarily have a process running when logged in):
Line 424:		Line 425:

	This information was found by researching how a standard Debian-based system boots up and initializes. The APODIO file system was browsed to discover what scripts reside in which folders, to discover how and when each one is run.		This information was found by researching how a standard Debian-based system boots up and initializes. The APODIO file system was browsed to discover what scripts reside in which folders, to discover how and when each one is run.

	~~After all of this, the system is initialized.~~

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

Mbrowna: /* System Initialization */

2011-12-19T06:18:23Z

System Initialization

← Older revision		Revision as of 06:18, 19 December 2011
Line 415:		Line 415:

	Some outlying scripts remain (that don't necessarily have a process running when logged in):		Some outlying scripts remain (that don't necessarily have a process running when logged in):
	* '''S21aumix''': Saves and restores audio-mixer settings when booting up and shutting down.		* '''S21aumix''': Saves and restores audio-mixer settings when booting up and shutting down.
	* '''S91apache2''': In charge of starting/stopping the apache web server (not running by default on APODIO).		* '''S91apache2''': In charge of starting/stopping the apache web server (not running by default on APODIO).
	* '''S20fancontrol''': Associated with '''S46-lm-sensors''', automated software to regulate fan-speed based on temperature.		* '''S20fancontrol''': Associated with '''S46-lm-sensors''', automated software to regulate fan-speed based on temperature.
	* '''S20icecast2''': Starts the icecast audio streaming server daemon.		* '''S20icecast2''': Starts the icecast audio streaming server daemon.
	* '''S25bluetooth''': Starts the bluetoothd process (not running by default on APODIO).		* '''S25bluetooth''': Starts the bluetoothd process (not running by default on APODIO).
	* '''S20speech-dispatcher''': Common interface to speech synthesizers.		* '''S20speech-dispatcher''': Common interface to speech synthesizers.
	* '''S50rsync''': Program that allows the copying of files to/from remote machines (similar to rcp).		* '''S50rsync''': Program that allows the copying of files to/from remote machines (similar to rcp).

	This information was found by researching how a standard Debian-based system boots up and initializes. The APODIO file system was browsed to discover what scripts reside in which folders, to discover how and when each one is run.		This information was found by researching how a standard Debian-based system boots up and initializes. The APODIO file system was browsed to discover what scripts reside in which folders, to discover how and when each one is run.

Mbrowna: /* System Initialization */

2011-12-19T06:17:20Z

System Initialization

@@ Line 258: / Line 258: @@
 The system startup process of APODIO will be similar to that of the boot up process of Ubuntu (and therefore, Debian). Like any standard machine, it begins with the BIOS which loads the boot sector from any standard medium (Floppy Disk, CD-ROM, Hard Drive, USB, etc.).<ref>[http://www.debianhelp.co.uk/boot.htm "Linux Boot Sequence"]: debianhelp.co.uk. 2010-10-13. (Last accessed 2011-11-15).</ref> The BIOS will load and execute the first 512 bytes of disk, and the boot record will attempt to find a primary partition, via the boot loader (generally GRUB for Linux machines). From here, the kernel of the machine is loaded (initializing devices, mounting filesystems, etc.). After this, the kernel will execute <code>/sbin/init</code>.
-From <code>/sbin/init</code>, the <code>/etc/inittab</code> is read so that the system knows what programs to run (based on the run level the system is currently operating in). The default run level when booting up us run level 2 (Full Multi-User Mode). Different scripts are run within different folders beforehand, however: <code>/etc/init.d/rcS/</code>, which runs scripts in <code>/etc/rcS.d/</code>, as well as deprecated scripts within <code>/etc/rc.boot/</code>.
+From <code>/sbin/init</code>, the <code>/etc/inittab</code> is read so that the system knows what programs to run (based on the run level the system is currently operating in). The default run level when booting up us run level 2 (Full Multi-User Mode). Different scripts are run within different folders beforehand, however: <code>/etc/init.d/rcS/</code>, which runs scripts in <code>/etc/rcS.d/</code>, as well as deprecated scripts within <code>/etc/rc.boot/</code>. A few of the scripts in <code>/etc/rcS.d/</code> are:
 At this point, the appropriate run level scripts are run (<code>/etc/rc[run-level].d/</code>), all of the scripts within <code>/etc/rc2.d/</code> (that start with <code>SXX</code>, where <code>XX</code> is a numerical for order) will have been executed (as the basic, multi-user mode is ''run level'' 2):
@@ Line 359: / Line 367: @@
        ├─wnck-applet
        └─wpa_supplicant
 This information was found by researching how a standard Debian-based system boots up and initializes. The APODIO file system was browsed to discover what scripts reside in which folders, to discover how and when each one is run.

Mbrowna: /* System Initialization */

2011-12-19T03:33:12Z

System Initialization

@@ Line 258: / Line 258: @@
 The system startup process of APODIO will be similar to that of the boot up process of Ubuntu (and therefore, Debian). Like any standard machine, it begins with the BIOS which loads the boot sector from any standard medium (Floppy Disk, CD-ROM, Hard Drive, USB, etc.).<ref>[http://www.debianhelp.co.uk/boot.htm "Linux Boot Sequence"]: debianhelp.co.uk. 2010-10-13. (Last accessed 2011-11-15).</ref> The BIOS will load and execute the first 512 bytes of disk, and the boot record will attempt to find a primary partition, via the boot loader (generally GRUB for Linux machines). From here, the kernel of the machine is loaded (initializing devices, mounting filesystems, etc.). After this, the kernel will execute <code>/sbin/init</code>.
-From <code>/sbin/init</code>, the <code>/etc/inittab</code> is read so that the system knows what programs to run (based on the run level the system is currently operating in). The default run level when booting up us run level 2 (Full Multi-User Mode). Different scripts are run within different folders beforehand, however: <code>/etc/init.d/rcS/<code>, which runs scripts in <code>/etc/rcS.d/</code>, as well as deprecated scripts within <code>/etc/rc.boot/</code>.
+From <code>/sbin/init</code>, the <code>/etc/inittab</code> is read so that the system knows what programs to run (based on the run level the system is currently operating in). The default run level when booting up us run level 2 (Full Multi-User Mode). Different scripts are run within different folders beforehand, however: <code>/etc/init.d/rcS/</code>, which runs scripts in <code>/etc/rcS.d/</code>, as well as deprecated scripts within <code>/etc/rc.boot/</code>.
-At this point, the appropriate run level scripts are run (<code>/etc/rc[run-level].d/</code>) When the system is '''fully initialized''', all of the scripts within <code>/etc/rc2.d/</code> will have been executed (as the basic, multi-user mode is ''run level 2''):
+At this point, the appropriate run level scripts are run (<code>/etc/rc[run-level].d/</code>), all of the scripts within <code>/etc/rc2.d/</code> (that start with <code>SXX</code>, where <code>XX</code> is a numerical for order) will have been executed (as the basic, multi-user mode is ''run level'' 2):
   /etc/rc2.d/S*
@@ Line 275: / Line 275: @@
 These scripts are run in alphabetical order (mainly sorted by S[number]),<ref>[http://tldp.org/LDP/intro-linux/html/sect_04_02.html "Boot process, Init and shutdown"]: tldp.org. 2008-06-06. (Last accessed 2011-11-15).</ref> although are technically just the symbolic links to the real scripts located within <code>/etc/init.d/</code>.
 This information was found by researching how a standard Debian-based system boots up and initializes. The APODIO file system was browsed to discover what scripts reside in which folders, to discover how and when each one is run.

Mbrowna: /* System Initialization */

2011-12-18T23:32:15Z

System Initialization

@@ Line 258: / Line 258: @@
 The system startup process of APODIO will be similar to that of the boot up process of Ubuntu (and therefore, Debian). Like any standard machine, it begins with the BIOS which loads the boot sector from any standard medium (Floppy Disk, CD-ROM, Hard Drive, USB, etc.).<ref>[http://www.debianhelp.co.uk/boot.htm "Linux Boot Sequence"]: debianhelp.co.uk. 2010-10-13. (Last accessed 2011-11-15).</ref> The BIOS will load and execute the first 512 bytes of disk, and the boot record will attempt to find a primary partition, via the boot loader (generally GRUB for Linux machines). From here, the kernel of the machine is loaded (initializing devices, mounting filesystems, etc.). After this, the kernel will execute <code>/sbin/init</code>.
-From <code>/sbin/init</code>, the <code>/etc/inittab</code> is read so that the system knows what programs to run (based on the run level the system is currently operating in). The default run level when booting up us run level 2 (Full Multi-User Mode). Different scripts are run within different folders beforehand, however:
+From <code>/sbin/init</code>, the <code>/etc/inittab</code> is read so that the system knows what programs to run (based on the run level the system is currently operating in). The default run level when booting up us run level 2 (Full Multi-User Mode). Different scripts are run within different folders beforehand, however: <code>/etc/init.d/rcS/<code>, which runs scripts in <code>/etc/rcS.d/</code>, as well as deprecated scripts within <code>/etc/rc.boot/</code>.
 At this point, the appropriate run level scripts are run (<code>/etc/rc[run-level].d/</code>) When the system is '''fully initialized''', all of the scripts within <code>/etc/rc2.d/</code> will have been executed (as the basic, multi-user mode is ''run level 2''):

Mbrowna: /* System Initialization */

2011-12-18T23:26:36Z

System Initialization

← Older revision		Revision as of 23:26, 18 December 2011
Line 274:		Line 274:
	as well as deprecated scripts within <code>/etc/rc.boot/</code>.		as well as deprecated scripts within <code>/etc/rc.boot/</code>.

	At this point, the appropriate run level scripts are run (<code>/etc/rc[run-level].d/</code>):		At this point, the appropriate run level scripts are run (<code>/etc/rc[run-level].d/</code>) When the system is '''fully initialized''', all of the scripts within <code>/etc/rc2.d/</code> will have been executed (as the basic, multi-user mode is ''run level 2''):

	/etc/rc2.d/S*		/etc/rc2.d/S*
	~~S20fancontrol~~		S20akiradrelease S21aumix S70pppd-dns
	~~S20speech~~-~~dispatcher~~		S20cinecutiestart S25bluetooth S90binfmt-support
	~~S25bluetooth~~		S20cinestart S30vboxadd S91apache2
	S30vboxadd		S20darkice S30vboxadd-x11 S99acpi-support
	S50rsync		S20fancontrol S35vboxadd-service S99grub-common
	~~S70dns~~-~~clean~~		S20icecast2 S50cups S99jackd
	~~S99grub~~-~~common~~		S20kerneloops S50pulseaudio S99ondemand
			S20lighttpd S50rsync S99rc.local
			S20speech-dispatcher S50saned S99rtirq
			S20winbind S70dns-clean S99timidity

	~~The~~ scripts are run in alphabetical order (mainly sorted by S[number]).<ref>[http://tldp.org/LDP/intro-linux/html/sect_04_02.html "Boot process, Init and shutdown"]: tldp.org. 2008-06-06. (Last accessed 2011-11-15).</ref> This information was found by researching how a standard Debian-based system boots up and initializes. The APODIO file system was browsed to discover what scripts reside in which folders, to discover how and when each one is run.		These scripts are run in alphabetical order (mainly sorted by S[number]),<ref>[http://tldp.org/LDP/intro-linux/html/sect_04_02.html "Boot process, Init and shutdown"]: tldp.org. 2008-06-06. (Last accessed 2011-11-15).</ref> although are technically just the symbolic links to the real scripts located within <code>/etc/init.d/</code>.

			This information was found by researching how a standard Debian-based system boots up and initializes. The APODIO file system was browsed to discover what scripts reside in which folders, to discover how and when each one is run.

	After all of this, the system is initialized.		After all of this, the system is initialized.

Mbrowna at 18:28, 5 December 2011

2011-12-05T18:28:40Z

← Older revision		Revision as of 18:28, 5 December 2011
Line 288:		Line 288:

	After all of this, the system is initialized.		After all of this, the system is initialized.

	~~=Part III=~~
	~~Due: December 5th, 2011.~~

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

Mbrowna at 18:27, 5 December 2011

2011-12-05T18:27:27Z

← Older revision		Revision as of 18:27, 5 December 2011
Line 70:		Line 70:
	To sample a simple image program, [http://mypaint.intilinux.com/ MyPaint] and GIMP were used. MyPaint is an open-source graphics program for artists who appreciate digital mediums for creating, and don't want an annoying interface,<ref>[http://mypaint.intilinux.com/ "MyPaint"]: mypaint.intilinux.com. 2011. (Last accessed 2011-10-16).</ref> and GIMP is the '''G'''NU '''I'''mage '''M'''anipulation '''P'''rogram, a package that allows users to modify and manipulate photos, providing features such as photo enhancement and digital retouching.<ref>[http://www.gimp.org/features/ "GIMP - Feature Overview"]: gimp.org. 2011. (Last accessed 2011-10-16).</ref> It is a raster editor (meaning that it performs operations directly on the pixels that make up the image), as opposed to a vector image (where the image is made up of directional lines that explain how the image looks). A picture of a sun was drawn in MyPaint using its various brush tools; the variety of tools supplied is quite profound, and really shows the potential of this simple application. That image was then saved and opened in GIMP, where the colour levels were modified (among other settings) to show how simple adjustments propagate larger effects '''(Figure 7)'''.		To sample a simple image program, [http://mypaint.intilinux.com/ MyPaint] and GIMP were used. MyPaint is an open-source graphics program for artists who appreciate digital mediums for creating, and don't want an annoying interface,<ref>[http://mypaint.intilinux.com/ "MyPaint"]: mypaint.intilinux.com. 2011. (Last accessed 2011-10-16).</ref> and GIMP is the '''G'''NU '''I'''mage '''M'''anipulation '''P'''rogram, a package that allows users to modify and manipulate photos, providing features such as photo enhancement and digital retouching.<ref>[http://www.gimp.org/features/ "GIMP - Feature Overview"]: gimp.org. 2011. (Last accessed 2011-10-16).</ref> It is a raster editor (meaning that it performs operations directly on the pixels that make up the image), as opposed to a vector image (where the image is made up of directional lines that explain how the image looks). A picture of a sun was drawn in MyPaint using its various brush tools; the variety of tools supplied is quite profound, and really shows the potential of this simple application. That image was then saved and opened in GIMP, where the colour levels were modified (among other settings) to show how simple adjustments propagate larger effects '''(Figure 7)'''.

	As well as the plethora or programs installed, it's important to remember that this is still a typical GNU/Linux distribution under the hood. The common, necessary components remain intact, such as [http://projects.gnome.org/gedit/ gedit] and the terminal '''(Figure 8)'''.		As well as the plethora of programs installed, it's important to remember that this is still a typical GNU/Linux distribution under the hood. The common, necessary components remain intact, such as [http://projects.gnome.org/gedit/ gedit] and the terminal '''(Figure 8)'''.

	This is the most basic of operations of APODIO. Simply speaking, it provides the environment in which the provided applications run, and all operations would be unique to each application, and not APODIO. At this stage, however, not even Guest Additions were installed, and APODIO still ran these programs quite well.		This is the most basic of operations of APODIO. Simply speaking, it provides the environment in which the provided applications run, and all operations would be unique to each application, and not APODIO. At this stage, however, not even Guest Additions were installed, and APODIO still ran these programs quite well.
Line 76:		Line 76:
	==Usage Evaluation==		==Usage Evaluation==

	With the number of applications included, the organizational tactic implemented, and the simplicity offered by APODIO, this distribution certainly offers what it promises~~: an~~ operating system ~~that~~ provides a large collection of A/V applications, without the need for modifying unnecessary, finicky settings. Even running in a virtual environment, the system performed relative efficiently. Even though the applications have no real flow mechanism to creating large projects encompassing multiple media-types, the organization of the programs, and the pre-defined structure of folders makes utilizing all the programs simple and easy, however, there are a few minor things that can be improved upon.		With the number of applications included, the organizational tactic implemented, and the simplicity offered by APODIO, this distribution certainly offers what it promises. The operating system provides a large collection of A/V applications, without the need for modifying unnecessary, finicky settings. Even running in a virtual environment, the system performed relative efficiently. Even though the applications have no real flow mechanism to creating large projects encompassing multiple media-types, the organization of the programs, and the pre-defined structure of folders makes utilizing all the programs simple and easy, however, there are a few minor things that can be improved upon.

	When running the APODIO installer, it gives you the illusion that you can change settings that, in reality, have no effect. For one, creating a user has no effect, as the system comes with one default user already, and yet you can still add users once the system is installed, which seems rather contradictory to the design goals. For two, changing the keyboard language settings upon installation yielded no effect when the system was actually running; the system keyboard layout defaulted to 'France,' and thus, pressing certain keys resulted in undesirable outcomes ('m's become commas, 'a's become 'q's, etc.). This setting could be forcefully changed after installation, however.		When running the APODIO installer, it gives you the illusion that you can change settings that, in reality, have no effect. For one, creating a user has no effect, as the system comes with one default user already, and yet you can still add users once the system is installed, which seems rather contradictory to the design goals. For two, changing the keyboard language settings upon installation yielded no effect when the system was actually running; the system keyboard layout defaulted to 'France,' and thus, pressing certain keys resulted in undesirable outcomes ('m's become commas, 'a's become 'q's, etc.). This setting could be forcefully changed after installation, however.
Line 89:		Line 89:
	==Software Packaging==		==Software Packaging==
	[[File:Apodio_dpkg_l.png\|thumb\|right\|'''(Figure 9)''' Package list (by running <code>dpkg -l</code>)]]		[[File:Apodio_dpkg_l.png\|thumb\|right\|'''(Figure 9)''' Package list (by running <code>dpkg -l</code>)]]
	Software packaged for APODIO arrives in the format '''.deb''', and uses '''dpkg''' as the package management software, provided for all Debian GNU/Linux distributions (Ubuntu included, and therefore APODIO) ~~to handle~~ the installation, removal, and modification of software installed on the system. dpkg is a relatively low-level package manager, so the '''Advanced Packaging Tool''' ('''APT''') front-end interface is utilized to provide a higher level of abstraction of software management. This is particularly useful when dealing with more complex package management and relationships and package retrieval from additional sources.		Software packaged for APODIO arrives in the format '''.deb''', and uses '''dpkg''' as the package management software (provided for all Debian GNU/Linux distributions, Ubuntu included, and therefore APODIO). dpkg handles the installation, removal, and modification of software installed on the system. dpkg is a relatively low-level package manager, so the '''Advanced Packaging Tool''' ('''APT''') front-end interface is utilized to provide a higher level of abstraction of software management. This is particularly useful when dealing with more complex package management and relationships and package retrieval from additional sources.

	To get a list of all currently installed packages, simply type the following at the command line ('''Figure 9'''):		To get a list of all currently installed packages, simply type the following at the command line ('''Figure 9'''):
Line 99:		Line 99:
	$ apt-get install <pkg>		$ apt-get install <pkg>

	To ~~removes~~ a package, simply type the following at the command line:		To remove a package, simply type the following at the command line:
	$ dpkg -r <pkg>		$ dpkg -r <pkg>
	OR		OR

← Older revision		Revision as of 22:13, 19 December 2011
Line 66:		Line 66:
	APODIO organizes the packaged programs within it by media-type and by purpose, in that order '''(Figure 5)'''. This makes it much easier for finding desired applications, as well as discovering new ones that can be used for the same tasks.		APODIO organizes the packaged programs within it by media-type and by purpose, in that order '''(Figure 5)'''. This makes it much easier for finding desired applications, as well as discovering new ones that can be used for the same tasks.

	To sample a simple audio program, Audacity was used. Audacity is an open-source, cross-platform program that allows users to record and edit sounds.<ref>[http://audacity.sourceforge.net/about/ "Audacity: Free Audio Editor and Recorder"]: audacity.sourceforge.net. 2011-04-11. (Last accessed 2011-10-15).</ref> Tasks include amplifying, splicing and mixing sounds, editing .mp3 and .wav files, changing the speed and pitch of a track, to name a few. A generic .midi file was imported to explore the various features. Opening a .midi file yields rather fantastic abilities: since a .midi is just instructions on how to play music (as opposed to actual recorded music), you can see what musical notes actually comprise the file in Audacity (like virtual sheet music). Even running in a virtual environment, the program worked very well, and was able to perform various tasks efficiently '''(Figure 6)'''.		To sample a simple audio program, Audacity was used. Audacity is an open-source, cross-platform program that allows users to record and edit sounds.<ref>[http://audacity.sourceforge.net/about/ "Audacity: Free Audio Editor and Recorder"]: audacity.sourceforge.net. 2011-04-11. (Last accessed 2011-10-15).</ref> Tasks include amplifying, splicing and mixing sounds, editing .mp3 and .wav files, and changing the speed and pitch of a track, to name a few. A generic .midi file was imported to explore the various features. Opening a .midi file yields rather fantastic abilities: since a .midi is just instructions on how to play music (as opposed to actual recorded music), you can see what musical notes actually comprise the file in Audacity (like virtual sheet music). Even running in a virtual environment, the program worked very well, and was able to perform various tasks efficiently '''(Figure 6)'''.

	To sample a simple image program, [http://mypaint.intilinux.com/ MyPaint] and GIMP were used. MyPaint is an open-source graphics program for artists who appreciate digital mediums for creating, and don't want an annoying interface,<ref>[http://mypaint.intilinux.com/ "MyPaint"]: mypaint.intilinux.com. 2011. (Last accessed 2011-10-16).</ref> and GIMP is the '''G'''NU '''I'''mage '''M'''anipulation '''P'''rogram, a package that allows users to modify and manipulate photos, providing features such as photo enhancement and digital retouching.<ref>[http://www.gimp.org/features/ "GIMP - Feature Overview"]: gimp.org. 2011. (Last accessed 2011-10-16).</ref> It is a raster editor (meaning that it performs operations directly on the pixels that make up the image), as opposed to a vector ~~image~~ (where the image is made up of directional lines that explain how the image looks). A picture of a sun was drawn in MyPaint using its various brush tools; the variety of tools supplied is quite profound, and really shows the potential of this simple application. That image was then saved and opened in GIMP, where the colour levels were modified (among other settings) to show how simple adjustments propagate larger effects '''(Figure 7)'''.		To sample a simple image program, [http://mypaint.intilinux.com/ MyPaint] and GIMP were used. MyPaint is an open-source graphics program for artists who appreciate digital mediums for creating, and don't want an annoying interface,<ref>[http://mypaint.intilinux.com/ "MyPaint"]: mypaint.intilinux.com. 2011. (Last accessed 2011-10-16).</ref> and GIMP is the '''G'''NU '''I'''mage '''M'''anipulation '''P'''rogram, a package that allows users to modify and manipulate photos, providing features such as photo enhancement and digital retouching.<ref>[http://www.gimp.org/features/ "GIMP - Feature Overview"]: gimp.org. 2011. (Last accessed 2011-10-16).</ref> It is a raster editor (meaning that it performs operations directly on the pixels that make up the image), as opposed to a vector editor (where the image is made up of directional lines that explain how the image looks). A picture of a sun was drawn in MyPaint using its various brush tools; the variety of tools supplied is quite profound, and really shows the potential of this simple application. That image was then saved and opened in GIMP, where the colour levels were modified (among other settings) to show how simple adjustments propagate larger effects '''(Figure 7)'''.

	As well as the plethora of programs installed, it's important to remember that this is still a typical GNU/Linux distribution under the hood. The common, necessary components remain intact, such as [http://projects.gnome.org/gedit/ gedit] and the terminal '''(Figure 8)'''.		As well as the plethora of programs installed, it's important to remember that this is still a typical GNU/Linux distribution under the hood. The common, necessary components remain intact, such as [http://projects.gnome.org/gedit/ gedit] and the terminal '''(Figure 8)'''.

	This is the most basic of operations of APODIO. Simply speaking, it provides the environment in which the provided applications run, and all operations ~~would be~~ unique to each application, and not APODIO. At this stage, however, not even Guest Additions were installed, and APODIO still ran these programs quite well.		This is the most basic of operations of APODIO. Simply speaking, it provides the environment in which the provided applications run, and all operations are unique to each application, and not APODIO. At this stage, however, not even Guest Additions were installed, and APODIO still ran these programs quite well.

	==Usage Evaluation==		==Usage Evaluation==

	With the number of applications included, the organizational tactic implemented, and the simplicity offered by APODIO, this distribution certainly offers what it promises. The operating system provides a large collection of A/V applications, without the need for modifying unnecessary, finicky settings. Even running in a virtual environment, the system performed relative efficiently. Even though ~~the applications have~~ no real flow mechanism to creating large projects encompassing multiple media-types, the organization of the programs, and the pre-defined structure of folders makes utilizing all the programs simple and easy~~, however~~, there are a few minor things that can be improved upon.		With the number of applications included, the organizational tactic implemented, and the simplicity offered by APODIO, this distribution certainly offers what it promises. The operating system provides a large collection of A/V applications, without the need for modifying unnecessary, finicky settings. Even running in a virtual environment, the system performed relative efficiently. Even though no real flow mechanism is provided for creating large projects encompassing multiple media-types and applications, the organization of the programs and the pre-defined structure of folders makes utilizing all the programs simple and easy. However, there are a few minor things that can be improved upon.

	~~When running the~~ APODIO installer~~, it~~ gives ~~you~~ the illusion that you can change settings that, in reality, have no effect. For one, creating a user ~~has~~ no effect, as the system comes with one default user already, ~~and~~ yet you can still add users once the system is installed, which seems rather contradictory to the design goals. ~~For two~~, changing the keyboard language settings upon installation yielded no effect when the system was actually running; the system keyboard layout defaulted to 'France,' and thus, pressing certain keys resulted in undesirable outcomes ('m's become commas, 'a's become 'q's, etc.). This setting could be forcefully changed after installation, however.		The APODIO installer gives the illusion that you can change installation settings that, in reality, have no effect. For one, creating a user during installation seems to yield no effect (as the system comes with one default user already), yet you can still add users once the system is installed, which seems rather contradictory to the design goals. Secondly, changing the keyboard language settings upon installation yielded no effect when the system was actually running; the system keyboard layout defaulted to 'France,' and thus, pressing certain keys resulted in undesirable outcomes ('m's become commas, 'a's become 'q's, etc.). This setting could be forcefully changed after installation, however.

	Overall, however, I think this is an extremely convenient operating system for an A/V fanatics, but it might be lost on some users who prefer a crisper and cleaner look to their environments; APODIO doesn't do the best job of making these programs aesthetically pleasing, but it is arguable that this bare-bones interface gets right down to the point to allow its users simplicity when performing tasks.		Overall, however, I think this is an extremely convenient operating system for an A/V fanatics, but it might be lost on some users who prefer a crisper and cleaner look to their environments; APODIO doesn't do the best job of making these programs aesthetically pleasing, but it is arguable that this bare-bones interface gets right down to the point to allow its users simplicity when performing tasks.
Line 89:		Line 89:
	==Software Packaging==		==Software Packaging==
	[[File:Apodio_dpkg_l.png\|thumb\|right\|'''(Figure 9)''' Package list (by running <code>dpkg -l</code>)]]		[[File:Apodio_dpkg_l.png\|thumb\|right\|'''(Figure 9)''' Package list (by running <code>dpkg -l</code>)]]
	Software packaged for APODIO arrives in the format '''.deb''', and uses '''dpkg''' as the package management software (provided for all Debian GNU/Linux distributions, Ubuntu ~~included,~~ and ~~therefore~~ APODIO). dpkg handles the installation, removal, and modification of software installed on the system. dpkg is a relatively low-level package manager, so the '''Advanced Packaging Tool''' ('''APT''') front-end interface is utilized to provide a higher level of abstraction of software management. This is particularly useful when dealing with more complex package management and relationships and package retrieval from additional sources.		Software packaged for APODIO arrives in the format '''.deb''', and uses '''dpkg''' as the package management software (provided for all Debian GNU/Linux distributions, and therefore Ubuntu and APODIO). dpkg handles the installation, removal, and modification of software installed on the system. dpkg is a relatively low-level package manager, so the '''Advanced Packaging Tool''' ('''APT''') front-end interface is utilized to provide a higher level of abstraction of software management. This is particularly useful when dealing with more complex package management and relationships, and package retrieval from additional sources.

	To get a list of all currently installed packages, simply type the following at the command line ('''Figure 9'''):		To get a list of all currently installed packages, simply type the following at the command line ('''Figure 9'''):
Line 258:		Line 258:
	The system startup process of APODIO will be similar to that of the boot up process of Ubuntu (and therefore, Debian). Like any standard machine, it begins with the BIOS which loads the boot sector from any standard medium (Floppy Disk, CD-ROM, Hard Drive, USB, etc.).<ref>[http://www.debianhelp.co.uk/boot.htm "Linux Boot Sequence"]: debianhelp.co.uk. 2010-10-13. (Last accessed 2011-11-15).</ref> The BIOS will load and execute the first 512 bytes of disk, and the boot record will attempt to find a primary partition, via the boot loader (generally GRUB for Linux machines). From here, the kernel of the machine is loaded (initializing devices, mounting filesystems, etc.). After this, the kernel will execute <code>/sbin/init</code>.		The system startup process of APODIO will be similar to that of the boot up process of Ubuntu (and therefore, Debian). Like any standard machine, it begins with the BIOS which loads the boot sector from any standard medium (Floppy Disk, CD-ROM, Hard Drive, USB, etc.).<ref>[http://www.debianhelp.co.uk/boot.htm "Linux Boot Sequence"]: debianhelp.co.uk. 2010-10-13. (Last accessed 2011-11-15).</ref> The BIOS will load and execute the first 512 bytes of disk, and the boot record will attempt to find a primary partition, via the boot loader (generally GRUB for Linux machines). From here, the kernel of the machine is loaded (initializing devices, mounting filesystems, etc.). After this, the kernel will execute <code>/sbin/init</code>.

	From <code>/sbin/init</code>, ~~the~~ <code>/etc/inittab</code> is read so that the system knows what programs to run (based on the run level the system is currently operating in). The default run level when booting up us run level 2 (Full Multi-User Mode). Different scripts are run within different folders beforehand, however: <code>/etc/init.d/rcS/</code>, which runs scripts in <code>/etc/rcS.d/</code>, as well as deprecated scripts within <code>/etc/rc.boot/</code>. A few of the scripts in <code>/etc/rcS.d/</code> are:		From <code>/sbin/init</code>, <code>/etc/inittab</code> is read so that the system knows what programs to run (based on the run level the system is currently operating in). The default run level when booting up us run level 2 (Full Multi-User Mode). Different scripts are run within different folders beforehand, however: <code>/etc/init.d/rcS/</code>, which runs scripts in <code>/etc/rcS.d/</code>, as well as deprecated scripts within <code>/etc/rc.boot/</code>. A few of the scripts in <code>/etc/rcS.d/</code> are:

	/etc/rcS.d/S*		/etc/rcS.d/S*
Line 268:		Line 268:
	S70x11-common		S70x11-common

	At this point, the appropriate run level scripts are run (<code>/etc/rc[run-level].d/</code>)~~, all~~ of the scripts ~~within <code>/etc/rc2.d/</code> (~~that start with <code>SXX</code>, where <code>XX</code> is a ~~numerical~~ for order) will have been executed (as the basic, multi-user mode ~~is ''~~run level'' 2):		At this point, the appropriate run level scripts are run (<code>/etc/rc[run-level].d/</code>). All of the scripts that start with <code>SXX</code> (where <code>XX</code> is a number for distinguishing order) within <code>/etc/rc2.d/</code> will have been executed (as this is the basic, multi-user mode, run level 2):

	/etc/rc2.d/S*		/etc/rc2.d/S*
Line 282:		Line 282:
	S20winbind S70dns-clean S99timidity		S20winbind S70dns-clean S99timidity

	These scripts are run in alphabetical order (mainly sorted by S[number]),<ref>[http://tldp.org/LDP/intro-linux/html/sect_04_02.html "Boot process, Init and shutdown"]: tldp.org. 2008-06-06. (Last accessed 2011-11-15).</ref> although are technically just the symbolic links to the real scripts located within <code>/etc/init.d/</code>.		These scripts are run in alphabetical order (mainly sorted by <code>S[number]</code>),<ref>[http://tldp.org/LDP/intro-linux/html/sect_04_02.html "Boot process, Init and shutdown"]: tldp.org. 2008-06-06. (Last accessed 2011-11-15).</ref> although are technically just the symbolic links to the real scripts located within <code>/etc/init.d/</code>.

	[[File:Apodio_pstree.png\|thumb\|right\|'''(Figure 10)''' Process tree (by running <code>pstree</code>)]]		[[File:Apodio_pstree.png\|thumb\|right\|'''(Figure 10)''' Process tree (by running <code>pstree</code>)]]
	Upon logging in, all of the ~~needed~~ processes are running. The process tree depicts information about all currently active processes, and the parent-child relationship between them ('''Figure 10'''). The process tree can be loaded via the terminal by typing in the following command:		Upon logging in, all of the necessary processes are running. The process tree depicts information about all currently active processes, and the parent-child relationship between them ('''Figure 10'''). The process tree can be loaded via the terminal by typing in the following command:

	$ pstree		$ pstree