COMP 3000 2011 Report: LinHES - Revision history

Jmarcha1: /* Basic Operation */

2011-12-13T21:53:39Z

Basic Operation

← Older revision		Revision as of 21:53, 13 December 2011
Line 103:		Line 103:
	**Upgrade LinHES		**Upgrade LinHES

	As I do not have a TV tuner, a capture card or cable I was not able to fully enjoy all the features of LinHES. However, since using these features would mainly consist of me watching TV this did not reduce my ability to assess LinHES' operation. I was still able to watch DVDs, listen to music, watch online streams, play games and enjoy many other features. One feature I found particularly fun was the "Play Online Stream" option. This option contains a sub-option of "Apple Trailers", which lists all the trailers from the Apple Trailers website in a handy alphabetical list (which can be traversed very quickly). When selected the trailers are fully loaded (to save the user from buffering during playback) and then played automatically when ready. Upon completion LinHES returns to the trailer list again. Most of the other features act fairly predictably, which is a very good thing in this case, as entertainment systems should make all their options clear and intuitive for easy use.		As I do not have a TV tuner, a capture card or cable I was not able to fully enjoy all the features of LinHES. However, since using these features would mainly consist of me watching TV this did not reduce my ability to assess LinHES' operation. I was still able to watch DVDs, listen to music, watch online streams, play games and enjoy many other features. One feature I found particularly fun was the "Play Online Stream" option. This option contains a sub-option of "Apple Trailers", which lists all the trailers from the Apple Trailers website in a handy alphabetical list (which can be traversed very quickly). When selected the trailers are fully loaded (to save the user from buffering during playback) and then played automatically when ready. Upon completion LinHES returns to the trailer list again. The play games menu option was also very interesting. Unlike most home theaters, LinHES still maintains the gaming power of any PC and includes the options the play standard PC games as well as emulate games from older console systems (assuming you own the original, otherwise this would be illegal). Included are emulators for MAME,NES and SNES. All games are played the same as you would on any PC with the keyboard and mouse. LinHES also includes a variety of other menu settings if you are not happy with the default (including some that are optimized for widescreen televisions). Most of the other features act fairly predictably, which is a very good thing in this case, as entertainment systems should make all their options clear and intuitive for easy use.

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

Jmarcha1: /* Initialization */

2011-12-13T21:43:46Z

Initialization

← Older revision		Revision as of 21:43, 13 December 2011
Line 201:		Line 201:
	In order to start up these processes LinHES also mounts the local filesystem, activates swap and various other system tasks. Only the first 4 process mentioned are started from /etc/runit/1. This file starts the first 4 process and does some required system setup. LinHES then leaves /etc/runit/1 and uses /etc/runit/2 to start up the rest of the system. A Photoshopped image of the full verbose start up screen's commands can be viewed to the right.		In order to start up these processes LinHES also mounts the local filesystem, activates swap and various other system tasks. Only the first 4 process mentioned are started from /etc/runit/1. This file starts the first 4 process and does some required system setup. LinHES then leaves /etc/runit/1 and uses /etc/runit/2 to start up the rest of the system. A Photoshopped image of the full verbose start up screen's commands can be viewed to the right.

	~~<br/>~~
	~~<br/>~~
	~~<br/>~~
	~~<br/>~~
	~~<br/>~~
	<br/>		<br/>
	<br/>		<br/>

Jmarcha1: /* Initialization */

2011-12-13T21:43:29Z

Initialization

← Older revision		Revision as of 21:43, 13 December 2011
Line 191:		Line 191:
	===Initialization===		===Initialization===
	[[File:LinHESVerbose.png\|400px\|thumb\|right\|		[[File:LinHESVerbose.png\|400px\|thumb\|right\|
	<p>''~~First Install Menu Options~~''</p>		<p>''Verbose Start Up''</p>
	]]		]]
	According to the LinHES page on ArchWiki, "LinHES uses /etc/runit/1.local for startup scripts"<ref name "ArchWiki">[https://wiki.archlinux.org/index.php/LinHES] Wikipedia Contributors. (September 21 2011). LinHES. Retrieved November 13, 2011, from ArchWiki:https://wiki.archlinux.org/index.php/LinHES</ref>. From this and the verbose boot up screen I can conlude that the first 5 process run are:		According to the LinHES page on ArchWiki, "LinHES uses /etc/runit/1.local for startup scripts"<ref name "ArchWiki">[https://wiki.archlinux.org/index.php/LinHES] Wikipedia Contributors. (September 21 2011). LinHES. Retrieved November 13, 2011, from ArchWiki:https://wiki.archlinux.org/index.php/LinHES</ref>. From this and the verbose boot up screen I can conlude that the first 5 process run are:
Line 201:		Line 201:
	In order to start up these processes LinHES also mounts the local filesystem, activates swap and various other system tasks. Only the first 4 process mentioned are started from /etc/runit/1. This file starts the first 4 process and does some required system setup. LinHES then leaves /etc/runit/1 and uses /etc/runit/2 to start up the rest of the system. A Photoshopped image of the full verbose start up screen's commands can be viewed to the right.		In order to start up these processes LinHES also mounts the local filesystem, activates swap and various other system tasks. Only the first 4 process mentioned are started from /etc/runit/1. This file starts the first 4 process and does some required system setup. LinHES then leaves /etc/runit/1 and uses /etc/runit/2 to start up the rest of the system. A Photoshopped image of the full verbose start up screen's commands can be viewed to the right.

			<br/>
			<br/>
			<br/>
			<br/>
			<br/>
			<br/>
	<br/>		<br/>

Jmarcha1: /* Initialization */

2011-12-13T21:42:53Z

Initialization

← Older revision		Revision as of 21:42, 13 December 2011
Line 201:		Line 201:
	In order to start up these processes LinHES also mounts the local filesystem, activates swap and various other system tasks. Only the first 4 process mentioned are started from /etc/runit/1. This file starts the first 4 process and does some required system setup. LinHES then leaves /etc/runit/1 and uses /etc/runit/2 to start up the rest of the system. A Photoshopped image of the full verbose start up screen's commands can be viewed to the right.		In order to start up these processes LinHES also mounts the local filesystem, activates swap and various other system tasks. Only the first 4 process mentioned are started from /etc/runit/1. This file starts the first 4 process and does some required system setup. LinHES then leaves /etc/runit/1 and uses /etc/runit/2 to start up the rest of the system. A Photoshopped image of the full verbose start up screen's commands can be viewed to the right.

	</br>		<br/>

	===References===		===References===

Jmarcha1: /* Initialization */

2011-12-13T21:42:40Z

Initialization

← Older revision		Revision as of 21:42, 13 December 2011
Line 190:		Line 190:

	===Initialization===		===Initialization===
	[[File:LinHESVerbose.png\|400px\|thumb\|~~left~~\|		[[File:LinHESVerbose.png\|400px\|thumb\|right\|
	<p>''First Install Menu Options''</p>		<p>''First Install Menu Options''</p>
	]]		]]
Line 200:		Line 200:
	#Mysql		#Mysql
	In order to start up these processes LinHES also mounts the local filesystem, activates swap and various other system tasks. Only the first 4 process mentioned are started from /etc/runit/1. This file starts the first 4 process and does some required system setup. LinHES then leaves /etc/runit/1 and uses /etc/runit/2 to start up the rest of the system. A Photoshopped image of the full verbose start up screen's commands can be viewed to the right.		In order to start up these processes LinHES also mounts the local filesystem, activates swap and various other system tasks. Only the first 4 process mentioned are started from /etc/runit/1. This file starts the first 4 process and does some required system setup. LinHES then leaves /etc/runit/1 and uses /etc/runit/2 to start up the rest of the system. A Photoshopped image of the full verbose start up screen's commands can be viewed to the right.

			</br>

	===References===		===References===

Jmarcha1: /* Initialization */

2011-12-13T21:41:58Z

Initialization

← Older revision		Revision as of 21:41, 13 December 2011
Line 190:		Line 190:

	===Initialization===		===Initialization===
			[[File:LinHESVerbose.png\|400px\|thumb\|left\|
			<p>''First Install Menu Options''</p>
			]]
	According to the LinHES page on ArchWiki, "LinHES uses /etc/runit/1.local for startup scripts"<ref name "ArchWiki">[https://wiki.archlinux.org/index.php/LinHES] Wikipedia Contributors. (September 21 2011). LinHES. Retrieved November 13, 2011, from ArchWiki:https://wiki.archlinux.org/index.php/LinHES</ref>. From this and the verbose boot up screen I can conlude that the first 5 process run are:		According to the LinHES page on ArchWiki, "LinHES uses /etc/runit/1.local for startup scripts"<ref name "ArchWiki">[https://wiki.archlinux.org/index.php/LinHES] Wikipedia Contributors. (September 21 2011). LinHES. Retrieved November 13, 2011, from ArchWiki:https://wiki.archlinux.org/index.php/LinHES</ref>. From this and the verbose boot up screen I can conlude that the first 5 process run are:
	#UDev Daemon		#UDev Daemon
Line 196:		Line 199:
	#UDev uevents		#UDev uevents
	#Mysql		#Mysql
	~~[[File:LinHESVerbose.png\|500px\|thumb\|left\|~~
	~~<p>''First Install Menu Options''</p>~~
	]]
	In order to start up these processes LinHES also mounts the local filesystem, activates swap and various other system tasks. Only the first 4 process mentioned are started from /etc/runit/1. This file starts the first 4 process and does some required system setup. LinHES then leaves /etc/runit/1 and uses /etc/runit/2 to start up the rest of the system. A Photoshopped image of the full verbose start up screen's commands can be viewed to the right.		In order to start up these processes LinHES also mounts the local filesystem, activates swap and various other system tasks. Only the first 4 process mentioned are started from /etc/runit/1. This file starts the first 4 process and does some required system setup. LinHES then leaves /etc/runit/1 and uses /etc/runit/2 to start up the rest of the system. A Photoshopped image of the full verbose start up screen's commands can be viewed to the right.

Jmarcha1: /* Initialization */

2011-12-13T21:41:36Z

Initialization

← Older revision		Revision as of 21:41, 13 December 2011
Line 196:		Line 196:
	#UDev uevents		#UDev uevents
	#Mysql		#Mysql
	In order to start up these processes LinHES also mounts the local filesystem, activates swap and various other system tasks. Only the first 4 process mentioned are started from /etc/runit/1. This file starts the first 4 process and does some required system setup. LinHES then leaves /etc/runit/1 and uses /etc/runit/2 to start up the rest of the system. A Photoshopped image of the full verbose start up screen's commands can be viewed to the right.		[[File:LinHESVerbose.png\|500px\|thumb\|left\|
	[[File:~~LinHESverbose~~.png\|~~250px~~\|thumb\|left\|
	<p>''First Install Menu Options''</p>		<p>''First Install Menu Options''</p>
	]]		]]
			In order to start up these processes LinHES also mounts the local filesystem, activates swap and various other system tasks. Only the first 4 process mentioned are started from /etc/runit/1. This file starts the first 4 process and does some required system setup. LinHES then leaves /etc/runit/1 and uses /etc/runit/2 to start up the rest of the system. A Photoshopped image of the full verbose start up screen's commands can be viewed to the right.

	===References===		===References===

Jmarcha1: /* Initialization */

2011-12-13T21:40:32Z

Initialization

← Older revision		Revision as of 21:40, 13 December 2011
Line 197:		Line 197:
	#Mysql		#Mysql
	In order to start up these processes LinHES also mounts the local filesystem, activates swap and various other system tasks. Only the first 4 process mentioned are started from /etc/runit/1. This file starts the first 4 process and does some required system setup. LinHES then leaves /etc/runit/1 and uses /etc/runit/2 to start up the rest of the system. A Photoshopped image of the full verbose start up screen's commands can be viewed to the right.		In order to start up these processes LinHES also mounts the local filesystem, activates swap and various other system tasks. Only the first 4 process mentioned are started from /etc/runit/1. This file starts the first 4 process and does some required system setup. LinHES then leaves /etc/runit/1 and uses /etc/runit/2 to start up the rest of the system. A Photoshopped image of the full verbose start up screen's commands can be viewed to the right.
			[[File:LinHESverbose.png\|250px\|thumb\|left\|
			<p>''First Install Menu Options''</p>
			]]

	===References===		===References===

Jmarcha1: /* Initialization */

2011-12-13T21:36:55Z

Initialization

← Older revision		Revision as of 21:36, 13 December 2011
Line 190:		Line 190:

	===Initialization===		===Initialization===
	According to the LinHES page on ArchWiki, "LinHES uses /etc/runit/1.local for startup scripts"<ref name "ArchWiki">[https://wiki.archlinux.org/index.php/LinHES] Wikipedia Contributors. (September 21 2011). LinHES. Retrieved November 13, 2011, from ArchWiki:https://wiki.archlinux.org/index.php/LinHES</ref>. From this ~~file~~ I ~~have been able to conclude~~ that the first 5 ~~commands~~ run are~~<ref name = "runit scripts">[http://linhes.org/cgit/cgit.cgi/linhes_pkgbuild/tree/abs/core/runit-scripts/runitscripts/1] Runitscripts/1 from LinHES packages files. Retrieved on November 15 2011.</ref>~~:		According to the LinHES page on ArchWiki, "LinHES uses /etc/runit/1.local for startup scripts"<ref name "ArchWiki">[https://wiki.archlinux.org/index.php/LinHES] Wikipedia Contributors. (September 21 2011). LinHES. Retrieved November 13, 2011, from ArchWiki:https://wiki.archlinux.org/index.php/LinHES</ref>. From this and the verbose boot up screen I can conlude that the first 5 process run are:
	#~~/etc/rc.sysinit~~		#UDev Daemon
	#~~/etc/rc.conf~~		#MythVantage-modules
	#~~/etc/rc.functions~~		#standard ACPI modules
	#~~hostname 'cat /etc/hostname'~~		#UDev uevents
	#~~/sbin/sysctl -p 2>/dev/null >/dev/null~~		#Mysql
	~~Once~~ the ~~scripts in~~ /etc/runit/1 ~~are finished I assume that~~ the ~~init scripts in~~ /etc/runit/2 and /etc/runit/~~3 are run to complete the necessary actions~~ to ~~load~~ the rest of the system. ~~From there~~ the ~~scripts in the /etc/runit/services directory are probably run~~ to ~~complete~~ the ~~system initialization~~.		In order to start up these processes LinHES also mounts the local filesystem, activates swap and various other system tasks. Only the first 4 process mentioned are started from /etc/runit/1. This file starts the first 4 process and does some required system setup. LinHES then leaves /etc/runit/1 and uses /etc/runit/2 to start up the rest of the system. A Photoshopped image of the full verbose start up screen's commands can be viewed to the right.

	===References===		===References===

Jmarcha1: /* Other packages */

2011-12-13T21:14:26Z

Other packages

← Older revision		Revision as of 21:14, 13 December 2011
Line 187:		Line 187:

	====Other packages====		====Other packages====
	~~#MythWeb (Web Interface for~~ MythTV's ~~Backend)~~		For all of MythTV's included packages the most recent version was used. Although the reason for this is clearly because it was the most recent version, it is especially important that the most recent versions were used in this case. The core functionality of LinHES centers around MythTV and to include anything less than the most recent version would defeat the purpose of the distribution. The package itself does not appear to have been modified from its original as the purpose of LinHES was simply to streamline the installation and use by providing some abstraction and not modifying its functionality. The lack of modification can be seen in the PKGBUILD files for the MythTV packages. The Qt framework included only has one minor version difference between the most recent version. This was, once again, likely to have been used simply for ease of incorporation on the developers' part (not to create more work for themselves that would not noticeably affect operation of the distribution. Qt also does not appear to have any major changes when you examine the PKGBUILD file for that package.
	~~#*Version Difference: none~~
	~~#*Modifications: PKGBUILD file~~ is ~~46 lines~~ of ~~code (1kb)~~. ~~Likely small modifications (if any)~~ have been ~~made~~. ~~<ref name = "mythweb build"/>~~
	#Qt ~~Framework~~
	~~#*Version Difference: There is~~ only 1 minor version difference between the ~~included version and the current~~ version. ~~A minor version change is not~~ likely to ~~affect the operation~~ of ~~LinHES in any substantial way and thus~~ the ~~difference is probably simply~~ to ~~save~~ work ~~changing things~~ that would not ~~make a noticeable difference on~~ the ~~system~~.
	~~#*Modifications:~~ PKGBUILD file ~~is 143 lines of code (5kb). Likely low to moderate modifications~~.~~<ref name = "Qt build"/>~~

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