Comp 3000 ArtistX Report - Revision history

Adangel2: /* Initialization */

2011-12-20T03:20:56Z

Initialization

← Older revision		Revision as of 03:20, 20 December 2011
Line 941:		Line 941:
	</p>		</p>
	<p>		<p>
	Once described, it should be apparent why each of those programs have been selected to run. How they get run is that they have init scripts in the /etc/init folder that the System V init system runs after it is started. As for the source of the descriptions and most of the quotations for the five programs elaborated upon below, they come from the BUM to which one can refer for more in-depth details (with the ''advanced'' box checked, select the appropriate entry from the list in the ''startup and shutdown scripts'' tab).		Once described, it should be apparent why each of those programs have been selected to run. How they get run is that they have init scripts in the /etc/init.d folder that the System V init system runs after it is started. As for the source of the descriptions and most of the quotations for the five programs elaborated upon below, they come from the BUM to which one can refer for more in-depth details (with the ''advanced'' box checked, select the appropriate entry from the list in the ''startup and shutdown scripts'' tab).
	</p>		</p>
	<p>		<p>

Adangel2: /* Major Package Versions */

2011-12-20T03:15:11Z

Major Package Versions

← Older revision		Revision as of 03:15, 20 December 2011
Line 906:		Line 906:
	<td>'''gif2png'''</td>		<td>'''gif2png'''</td>
	<td>		<td>
	According to the package's [http://www.catb.org/~esr/gif2png/NEWS release history], version 2.5.2 was released '''November 11, 2009''' and the most recent version is 2.5.4 which was released '''November 24, 2010'''. We see on the Ubuntu [https://launchpad.net/ubuntu/+source/gif2png/2.5.2-2 Launchpad changelog] that the included version is not stable and was released '''Monday, January 18, 2010'''. They have since created an updated unstable version ([https://launchpad.net/ubuntu/+source/gif2png/2.5.4-2 2.5.4-2]) which was released '''Saturday, April 30, 2011'''. It is pretty clear that Ubuntu modified the original package as they have a development branch for it. It looks as though when Ubuntu was developing the 'natty narwhal' release, 2.5.2 was the last released version and ArtistX inherited it. This is a useful conversion tool for image files and since things seem to be moving away from the gif format and towards the png format (the [http://en.wikipedia.org/wiki/Portable_Network_Graphics#Web_browser_support_for_PNG Wikipedia png article] reports that even the World Wide Web Consortium is pushing the move to png) it makes sense to have this tool. With an ever-increasing amount of multimedia content finding its way onto websites, the following aspect of the package description (as reported on the aforementioned [https://launchpad.net/ubuntu/+source/gif2png/2.5.2-2 Launchpad changelog]) seems like an attractive feature as web developers maintain their websites: ~~The~~ package ' ''also contains the script "web2png" which converts entire websites from GIF to PNG and updates the HTML accordingly.'' '		According to the package's [http://www.catb.org/~esr/gif2png/NEWS release history], version 2.5.2 was released '''November 11, 2009''' and the most recent version is 2.5.4 which was released '''November 24, 2010'''. We see on the Ubuntu [https://launchpad.net/ubuntu/+source/gif2png/2.5.2-2 Launchpad changelog] that the included version is not stable and was released '''Monday, January 18, 2010'''. They have since created an updated unstable version ([https://launchpad.net/ubuntu/+source/gif2png/2.5.4-2 2.5.4-2]) which was released '''Saturday, April 30, 2011'''. It is pretty clear that Ubuntu modified the original package as they have a development branch for it. It looks as though when Ubuntu was developing the 'natty narwhal' release, 2.5.2 was the last released version and ArtistX inherited it. This is a useful conversion tool for image files and since things seem to be moving away from the gif format and towards the png format (the [http://en.wikipedia.org/wiki/Portable_Network_Graphics#Web_browser_support_for_PNG Wikipedia png article] reports that even the World Wide Web Consortium is pushing the move to png) it makes sense to have this tool. With an ever-increasing amount of multimedia content finding its way onto websites, the following aspect of the package description (as reported on the aforementioned [https://launchpad.net/ubuntu/+source/gif2png/2.5.2-2 Launchpad changelog]) seems like an attractive feature as web developers maintain their websites: the package ' ''also contains the script "web2png" which converts entire websites from GIF to PNG and updates the HTML accordingly.'' '
	</td>		</td>
	</tr>		</tr>

Adangel2: /* Initialization */

2011-12-20T02:30:27Z

Initialization

← Older revision		Revision as of 02:30, 20 December 2011
Line 950:		Line 950:
	</p>		</p>
	<p>		<p>
	[http://www.lm-sensors.org '''S47lm-sensors'''] "is a hardware health monitoring package for Linux" with "utilities to read temperature/voltage/fan sensors". There also exists a 'sensors' man page that ~~give~~ some instruction as to how to use the 'sensors' command.		[http://www.lm-sensors.org '''S47lm-sensors'''] "is a hardware health monitoring package for Linux" with "utilities to read temperature/voltage/fan sensors". There also exists a 'sensors' man page that gives some instruction as to how to use the 'sensors' command.
	</p>		</p>
	<p>		<p>

Adangel2: /* Initialization */

2011-12-20T02:27:43Z

Initialization

← Older revision		Revision as of 02:27, 20 December 2011
Line 941:		Line 941:
	</p>		</p>
	<p>		<p>
	Once described, it should be apparent why each ~~process has~~ been selected to run. How they get run is that they have init scripts in the /etc/init folder that the System V init system runs after it is started. As for the source of the descriptions and most of the quotations for the five programs elaborated upon below, they come from the BUM to which one can refer for more in-depth details (with the ''advanced'' box checked, select the appropriate entry from the list in the ''startup and shutdown scripts'' tab).		Once described, it should be apparent why each of those programs have been selected to run. How they get run is that they have init scripts in the /etc/init folder that the System V init system runs after it is started. As for the source of the descriptions and most of the quotations for the five programs elaborated upon below, they come from the BUM to which one can refer for more in-depth details (with the ''advanced'' box checked, select the appropriate entry from the list in the ''startup and shutdown scripts'' tab).
	</p>		</p>
	<p>		<p>

Adangel2: /* Initialization */

2011-12-20T02:23:50Z

Initialization

← Older revision		Revision as of 02:23, 20 December 2011
Line 930:		Line 930:
	<p>and verified it's state by using</p>		<p>and verified it's state by using</p>
	initctl list		initctl list
	<p>once again; we then checked BUM and confirmed that it was disabled; we ~~then~~ told BUM to activate ''xxx'' which it reported as successful and updated it's list of running services; we finally checked</p>		<p>once again; we then checked BUM and confirmed that it was disabled; next we told BUM to activate ''xxx'' which it reported as successful and updated it's list of running services; we finally checked</p>
	initctl list		initctl list
	<p>one last time and found that ''xxx'' was in fact running again.		<p>one last time and found that ''xxx'' was in fact running again.

Adangel2: /* Initialization */

2011-12-20T02:23:08Z

Initialization

← Older revision		Revision as of 02:23, 20 December 2011
Line 930:		Line 930:
	<p>and verified it's state by using</p>		<p>and verified it's state by using</p>
	initctl list		initctl list
	<p>once again; we then checked BUM and confirmed it was disabled; we then told BUM to activate ''xxx'' which it reported as successful and updated it's list of running services; we finally checked</p>		<p>once again; we then checked BUM and confirmed that it was disabled; we then told BUM to activate ''xxx'' which it reported as successful and updated it's list of running services; we finally checked</p>
	initctl list		initctl list
	<p>one last time and found that ''xxx'' was in fact running again.		<p>one last time and found that ''xxx'' was in fact running again.

Adangel2: /* Major Package Versions */

2011-12-20T02:13:50Z

Major Package Versions

← Older revision		Revision as of 02:13, 20 December 2011
Line 852:		Line 852:
	<td>'''alsa-utils'''</td>		<td>'''alsa-utils'''</td>
	<td>		<td>
	According to [http://git.alsa-project.org/?p=alsa-utils.git;a=tag;h=1d2fa39204435601bec341c88955b3b6cf99d640 git release tag], the unmodified version of the included package of alsa-utils was committed (and I suppose released) '''Mon, 31 Jan 2011 at 14:19:55''' and it seems to be the latest stable release according to the [http://git.alsa-project.org/?p=alsa-utils.git;a=summary git summary]. I do not see any evidence leading me to conclude that the ArtistX team changed this package, but the Ubuntu team may have seeing how the version identifier contains the word 'ubuntu' in it. According to Wikipedia, the alternative to using ALSA would be Open Sound System (OSS) but the Linux people have decided to deprecate OSS and use ALSA as the default sound API<ref name="WikipediaALSA" >[http://en.wikipedia.org/wiki/Advanced_Linux_Sound_Architecture Wikipedia ALSA article]</ref><ref name="WikipediaOSS" >[http://en.wikipedia.org/wiki/Open_Sound_System Wikipedia OSS article]</ref>. ArtistX probably just accepted this default as it shows every sign of being the way of the future.		According to the [http://git.alsa-project.org/?p=alsa-utils.git;a=tag;h=1d2fa39204435601bec341c88955b3b6cf99d640 git release tag], the unmodified version of the included package of alsa-utils was committed (and I suppose released) '''Mon, 31 Jan 2011 at 14:19:55''' and it seems to be the latest stable release according to the [http://git.alsa-project.org/?p=alsa-utils.git;a=summary git summary]. I do not see any evidence leading me to conclude that the ArtistX team changed this package, but the Ubuntu team may have seeing how the version identifier contains the word 'ubuntu' in it. According to Wikipedia, the alternative to using ALSA would be Open Sound System (OSS) but the Linux people have decided to deprecate OSS and use ALSA as the default sound API<ref name="WikipediaALSA" >[http://en.wikipedia.org/wiki/Advanced_Linux_Sound_Architecture Wikipedia ALSA article]</ref><ref name="WikipediaOSS" >[http://en.wikipedia.org/wiki/Open_Sound_System Wikipedia OSS article]</ref>. ArtistX probably just accepted this default as it shows every sign of being the way of the future.
	</td>		</td>
	</tr>		</tr>

Adangel2: /* Software Packaging */

2011-12-20T02:09:09Z

Software Packaging

← Older revision		Revision as of 02:09, 20 December 2011
Line 140:		Line 140:
	</gallery>		</gallery>
	<p>		<p>
	Using Synaptic to install and remove packages is quite easy; if you click the rectangle to the left of the package name you will be given a list of appropriate options such as marking for installation or removal of which you would select what you want to do; you then click the 'Apply' button at the top of the window (the button with the green checkmark), then confirm what you want to add/remove. Note 'mark for removal' and 'mark for complete removal' both remove the package, but the complete removal will remove ''all'' files related to the package like configuration files and user-created data. Using Aptitude to install and remove packages is pretty straightforward but you have to select the 'Become root' option from the 'Actions' menu to do it; to add a package, you navigate to it from the menu/listings and select it for installation (most easily done by using the '+' button); to remove packages you navigate to them and deselect them (most easily done using '-' button); when you have finished selecting/deselecting other packages, you press 'g' to actually add or remove the packages. Note that these things can also be done through the menu at the top, but it is easier to do it with the keyboard.		Using Synaptic to install and remove packages is quite easy; if you click the rectangle to the left of the package name you will be given a list of appropriate options such as marking for installation or removal of which you would select what you want to do; you then click the 'Apply' button at the top of the window (the button with the green checkmark), then confirm what you want to add/remove. Note 'mark for removal' and 'mark for complete removal' both remove the package, but the complete removal will remove ''all'' files related to the package like configuration files and user-created data. Using Aptitude to install and remove packages is pretty straightforward but you have to select the 'Become root' option from the 'Actions' menu to do it; to add a package, you navigate to it from the menu/listings and select it for installation (most easily done by using the '+' button); to remove packages you navigate to them and deselect them (most easily done using '-' button); when you have finished selecting/deselecting other packages, you press 'g' to actually add or remove the packages. Note that these things can also be done through the menu at the top, but it is easier to do them with the keyboard.
	</p>		</p>
	<p>		<p>

Adangel2: /* Initialization */

2011-12-20T02:02:28Z

Initialization

← Older revision		Revision as of 02:02, 20 December 2011
Line 941:		Line 941:
	</p>		</p>
	<p>		<p>
	Once described, it should be apparent why each process has been selected to run. How they get run is that they have init scripts in the /etc/init folder that the System V init system runs after it is started. As for the source of the descriptions and most of the quotations below, they come from the BUM to which one can refer for more in-depth ~~descriptions~~ (with the ''advanced'' box checked, select the appropriate entry from the list in the ''startup and shutdown scripts'' tab).		Once described, it should be apparent why each process has been selected to run. How they get run is that they have init scripts in the /etc/init folder that the System V init system runs after it is started. As for the source of the descriptions and most of the quotations for the five programs elaborated upon below, they come from the BUM to which one can refer for more in-depth details (with the ''advanced'' box checked, select the appropriate entry from the list in the ''startup and shutdown scripts'' tab).
	</p>		</p>
	<p>		<p>

Adangel2: /* Initialization */

2011-12-20T01:59:03Z

Initialization

← Older revision		Revision as of 01:59, 20 December 2011
Line 941:		Line 941:
	</p>		</p>
	<p>		<p>
	Once described, it should be apparent why each process has been selected to run. ~~''Why''~~ they ~~are~~ run is ~~because~~ they have init scripts in the /etc/init folder that the System V init system runs after it is started. As for the source of the descriptions and most of the quotations below, they come from the BUM to which one can refer for more in-depth descriptions (with the ''advanced'' box checked, select the appropriate entry from the list in the ''startup and shutdown scripts'' tab).		Once described, it should be apparent why each process has been selected to run. How they get run is that they have init scripts in the /etc/init folder that the System V init system runs after it is started. As for the source of the descriptions and most of the quotations below, they come from the BUM to which one can refer for more in-depth descriptions (with the ''advanced'' box checked, select the appropriate entry from the list in the ''startup and shutdown scripts'' tab).
	</p>		</p>
	<p>		<p>