COMP 3000 2011 Report: PuppyLinux - Revision history

Mwooff: /* Initialization */

2011-12-06T03:54:05Z

Initialization

← Older revision		Revision as of 03:54, 6 December 2011
Line 355:		Line 355:

	'''This next process is the first one to run during bootup and is very important.'''		'''This next process is the first one to run during bootup and is very important.'''


	;udev		;udev

Mwooff: /* Processes */

2011-12-06T03:53:41Z

Processes

← Older revision		Revision as of 03:53, 6 December 2011
Line 397:		Line 397:
	root 474 2 0 03:13 ? 00:00:00 [loop0]		root 474 2 0 03:13 ? 00:00:00 [loop0]

	These processes are started during kernel threads. These next ones are started during the initialization shown above:		These processes are started during kernel threads. These next ones are started during the initialization shown above (especially "udev"):

	root 5914 1 0 03:14 ? 00:00:00 /bin/sh /sbin/pup_event_backend_		root 5914 1 0 03:14 ? 00:00:00 /bin/sh /sbin/pup_event_backend_

Mwooff: /* Software Initialization */

2011-12-06T03:53:00Z

Software Initialization

← Older revision		Revision as of 03:53, 6 December 2011
Line 355:		Line 355:

	'''This next process is the first one to run during bootup and is very important.'''		'''This next process is the first one to run during bootup and is very important.'''


	;udev		;udev

Mwooff: /* This next process is the first one to run during bootup and is very important. */

2011-12-06T03:52:35Z

This next process is the first one to run during bootup and is very important.

← Older revision		Revision as of 03:52, 6 December 2011
Line 354:		Line 354:


	== This next process is the first one to run during bootup and is very important. ==		'''This next process is the first one to run during bootup and is very important.'''

	;udev		;udev

Mwooff: /* Software Initialization */

2011-12-06T03:50:20Z

Software Initialization

← Older revision		Revision as of 03:50, 6 December 2011
Line 353:		Line 353:
	:This runs the daemons 'syslogd' and 'klogd', which log kernel and application events (espcially error messages) to various log files, mostly to /var/log/messages. This can be disabled and Puppy will still work.		:This runs the daemons 'syslogd' and 'klogd', which log kernel and application events (espcially error messages) to various log files, mostly to /var/log/messages. This can be disabled and Puppy will still work.

	~~'''~~This next process is the first one to run during bootup and is very important.~~'''~~
			== This next process is the first one to run during bootup and is very important. ==

	;udev		;udev

Mwooff: /* Software Initialization */

2011-12-06T03:49:32Z

Software Initialization

← Older revision		Revision as of 03:49, 6 December 2011
Line 353:		Line 353:
	:This runs the daemons 'syslogd' and 'klogd', which log kernel and application events (espcially error messages) to various log files, mostly to /var/log/messages. This can be disabled and Puppy will still work.		:This runs the daemons 'syslogd' and 'klogd', which log kernel and application events (espcially error messages) to various log files, mostly to /var/log/messages. This can be disabled and Puppy will still work.

	''This next process is the first one to run during bootup and is very important.''		'''This next process is the first one to run during bootup and is very important.'''

	;udev		;udev

Mwooff: /* Software Initialization */

2011-12-06T03:49:08Z

Software Initialization

← Older revision		Revision as of 03:49, 6 December 2011
Line 352:		Line 352:
	;sys_logger		;sys_logger
	:This runs the daemons 'syslogd' and 'klogd', which log kernel and application events (espcially error messages) to various log files, mostly to /var/log/messages. This can be disabled and Puppy will still work.		:This runs the daemons 'syslogd' and 'klogd', which log kernel and application events (espcially error messages) to various log files, mostly to /var/log/messages. This can be disabled and Puppy will still work.

			''This next process is the first one to run during bootup and is very important.''

	;udev		;udev

Mwooff: /* Basic Operation */

2011-12-06T03:46:51Z

Basic Operation

← Older revision		Revision as of 03:46, 6 December 2011
Line 57:		Line 57:
	The first thing I would do if I was using this easy-to-use distribution would be to fire up an internet browser, mainly Firefox. One purpose for reviving old machines would be to make it usable to the average user and these user's would definitely want access to the web. Puppy Linux doesn’t come pre-installed with any internet browsers but when you click the “browse” icon it gives you the option to install one of five browsers (Firefox, Seamonkey, Chromium, Opera, and Iron). Of course, you have to be connected to the internet to download one of these browsers. Once one is clicked, it is downloaded and automatically installed by the OS. After clicking on the Firefox icon, Puppy Linux prompted me to select which version of Firefox I wanted:		The first thing I would do if I was using this easy-to-use distribution would be to fire up an internet browser, mainly Firefox. One purpose for reviving old machines would be to make it usable to the average user and these user's would definitely want access to the web. Puppy Linux doesn’t come pre-installed with any internet browsers but when you click the “browse” icon it gives you the option to install one of five browsers (Firefox, Seamonkey, Chromium, Opera, and Iron). Of course, you have to be connected to the internet to download one of these browsers. Once one is clicked, it is downloaded and automatically installed by the OS. After clicking on the Firefox icon, Puppy Linux prompted me to select which version of Firefox I wanted:

	[[File:Puppy4.jpg\|~~500px~~\|center\|frame\|Launching an internet browser in PuppyLinux.]]		[[File:Puppy4.jpg\|400px\|center\|frame\|Launching an internet browser in PuppyLinux.]]

	Once it was installed, it launched the default Lucid Puppy page and I was able to use Firefox and surf the internet easily. The main page even comes with links for the user to explore the latest news, updates or documentation about Puppy Linux to get more acquainted with the OS.		Once it was installed, it launched the default Lucid Puppy page and I was able to use Firefox and surf the internet easily. The main page even comes with links for the user to explore the latest news, updates or documentation about Puppy Linux to get more acquainted with the OS.

	[[File:Puppy5.jpg\|~~500px~~\|center\|frame\|Firefox running in PuppyLinux.]]		[[File:Puppy5.jpg\|400px\|center\|frame\|Firefox running in PuppyLinux.]]

	We also tested the pre-installed image editor [http://mtpaint.sourceforge.net/ mtPaint] and easily managed to create a drawing dedicated to our new favourite Linux distribution:		We also tested the pre-installed image editor [http://mtpaint.sourceforge.net/ mtPaint] and easily managed to create a drawing dedicated to our new favourite Linux distribution:

	[[File:Puppy6.jpg\|~~500px~~\|center\|frame\|Creativity at its finest.]]		[[File:Puppy6.jpg\|400px\|center\|frame\|Creativity at its finest.]]

	Of course, another essential application to test is one of the pre-installed games called XInvaders 3D which is basically a 3D version of the old arcade game invaders. After much testing and intricate study, we were able to attain a high score of 10,000:		Of course, another essential application to test is one of the pre-installed games called XInvaders 3D which is basically a 3D version of the old arcade game invaders. After much testing and intricate study, we were able to attain a high score of 10,000:

	[[File:Puppy7.jpg\|~~500px~~\|center\|frame\|A great game for such a small OS.]]		[[File:Puppy7.jpg\|400px\|center\|frame\|A great game for such a small OS.]]

	After all the testing and exploring we did with Puppy Linux, we realized that there was one large bug that came with it. The cursor gets out of sync between the Virtual OS and Windows when you move the cursor outside of the Virtual environment. It seems like this is only evident when the OS is loaded inside a virtual environment, but we could not find any other instances of this problem occurring to other users when searching online. It’s not clear if it would be fixed if the OS was installed directly onto the machine but further testing would need to be done:		After all the testing and exploring we did with Puppy Linux, we realized that there was one large bug that came with it. The cursor gets out of sync between the Virtual OS and Windows when you move the cursor outside of the Virtual environment. It seems like this is only evident when the OS is loaded inside a virtual environment, but we could not find any other instances of this problem occurring to other users when searching online. It’s not clear if it would be fixed if the OS was installed directly onto the machine but further testing would need to be done:

	[[File:Puppy8.jpg\|~~500px~~\|center\|frame\|Cursor problems in VirtualBox.]]		[[File:Puppy8.jpg\|400px\|center\|frame\|Cursor problems in VirtualBox.]]

	Screenshots do not capture the Windows cursor but as you can see the tab “Devices” is being hovered over in Windows while the cursor is all the way on the right in the Virtual Machine. This problem got annoying when trying to reach icons that are close to edge of the window inside the virtual environment, but is fixable if you play around with the mouse to get the locations of both cursors to be close enough together.		Screenshots do not capture the Windows cursor but as you can see the tab “Devices” is being hovered over in Windows while the cursor is all the way on the right in the Virtual Machine. This problem got annoying when trying to reach icons that are close to edge of the window inside the virtual environment, but is fixable if you play around with the mouse to get the locations of both cursors to be close enough together.

Mwooff: /* Basic Operation */

2011-12-06T03:46:23Z

Basic Operation

← Older revision		Revision as of 03:46, 6 December 2011
Line 57:		Line 57:
	The first thing I would do if I was using this easy-to-use distribution would be to fire up an internet browser, mainly Firefox. One purpose for reviving old machines would be to make it usable to the average user and these user's would definitely want access to the web. Puppy Linux doesn’t come pre-installed with any internet browsers but when you click the “browse” icon it gives you the option to install one of five browsers (Firefox, Seamonkey, Chromium, Opera, and Iron). Of course, you have to be connected to the internet to download one of these browsers. Once one is clicked, it is downloaded and automatically installed by the OS. After clicking on the Firefox icon, Puppy Linux prompted me to select which version of Firefox I wanted:		The first thing I would do if I was using this easy-to-use distribution would be to fire up an internet browser, mainly Firefox. One purpose for reviving old machines would be to make it usable to the average user and these user's would definitely want access to the web. Puppy Linux doesn’t come pre-installed with any internet browsers but when you click the “browse” icon it gives you the option to install one of five browsers (Firefox, Seamonkey, Chromium, Opera, and Iron). Of course, you have to be connected to the internet to download one of these browsers. Once one is clicked, it is downloaded and automatically installed by the OS. After clicking on the Firefox icon, Puppy Linux prompted me to select which version of Firefox I wanted:

	[[File:Puppy4.jpg\|~~550px~~\|center\|frame\|Launching an internet browser in PuppyLinux.]]		[[File:Puppy4.jpg\|500px\|center\|frame\|Launching an internet browser in PuppyLinux.]]

	Once it was installed, it launched the default Lucid Puppy page and I was able to use Firefox and surf the internet easily. The main page even comes with links for the user to explore the latest news, updates or documentation about Puppy Linux to get more acquainted with the OS.		Once it was installed, it launched the default Lucid Puppy page and I was able to use Firefox and surf the internet easily. The main page even comes with links for the user to explore the latest news, updates or documentation about Puppy Linux to get more acquainted with the OS.

	[[File:Puppy5.jpg\|~~550px~~\|center\|frame\|Firefox running in PuppyLinux.]]		[[File:Puppy5.jpg\|500px\|center\|frame\|Firefox running in PuppyLinux.]]

	We also tested the pre-installed image editor [http://mtpaint.sourceforge.net/ mtPaint] and easily managed to create a drawing dedicated to our new favourite Linux distribution:		We also tested the pre-installed image editor [http://mtpaint.sourceforge.net/ mtPaint] and easily managed to create a drawing dedicated to our new favourite Linux distribution:

	[[File:Puppy6.jpg\|~~550px~~\|center\|frame\|Creativity at its finest.]]		[[File:Puppy6.jpg\|500px\|center\|frame\|Creativity at its finest.]]

	Of course, another essential application to test is one of the pre-installed games called XInvaders 3D which is basically a 3D version of the old arcade game invaders. After much testing and intricate study, we were able to attain a high score of 10,000:		Of course, another essential application to test is one of the pre-installed games called XInvaders 3D which is basically a 3D version of the old arcade game invaders. After much testing and intricate study, we were able to attain a high score of 10,000:

	[[File:Puppy7.jpg\|~~550px~~\|center\|frame\|A great game for such a small OS.]]		[[File:Puppy7.jpg\|500px\|center\|frame\|A great game for such a small OS.]]

	After all the testing and exploring we did with Puppy Linux, we realized that there was one large bug that came with it. The cursor gets out of sync between the Virtual OS and Windows when you move the cursor outside of the Virtual environment. It seems like this is only evident when the OS is loaded inside a virtual environment, but we could not find any other instances of this problem occurring to other users when searching online. It’s not clear if it would be fixed if the OS was installed directly onto the machine but further testing would need to be done:		After all the testing and exploring we did with Puppy Linux, we realized that there was one large bug that came with it. The cursor gets out of sync between the Virtual OS and Windows when you move the cursor outside of the Virtual environment. It seems like this is only evident when the OS is loaded inside a virtual environment, but we could not find any other instances of this problem occurring to other users when searching online. It’s not clear if it would be fixed if the OS was installed directly onto the machine but further testing would need to be done:

	[[File:Puppy8.jpg\|~~550px~~\|center\|frame\|Cursor problems in VirtualBox.]]		[[File:Puppy8.jpg\|500px\|center\|frame\|Cursor problems in VirtualBox.]]

	Screenshots do not capture the Windows cursor but as you can see the tab “Devices” is being hovered over in Windows while the cursor is all the way on the right in the Virtual Machine. This problem got annoying when trying to reach icons that are close to edge of the window inside the virtual environment, but is fixable if you play around with the mouse to get the locations of both cursors to be close enough together.		Screenshots do not capture the Windows cursor but as you can see the tab “Devices” is being hovered over in Windows while the cursor is all the way on the right in the Virtual Machine. This problem got annoying when trying to reach icons that are close to edge of the window inside the virtual environment, but is fixable if you play around with the mouse to get the locations of both cursors to be close enough together.

Mwooff: /* Processes */

2011-12-06T03:45:49Z

Processes

← Older revision		Revision as of 03:45, 6 December 2011
Line 392:		Line 392:
	root 136 2 0 03:13 ? 00:00:00 [aufsd/0]		root 136 2 0 03:13 ? 00:00:00 [aufsd/0]
	root 474 2 0 03:13 ? 00:00:00 [loop0]		root 474 2 0 03:13 ? 00:00:00 [loop0]

			These processes are started during kernel threads. These next ones are started during the initialization shown above:

	root 5914 1 0 03:14 ? 00:00:00 /bin/sh /sbin/pup_event_backend_		root 5914 1 0 03:14 ? 00:00:00 /bin/sh /sbin/pup_event_backend_
	root 5921 1 0 03:14 ? 00:00:00 /sbin/udevd --daemon --resolve-n		root 5921 1 0 03:14 ? 00:00:00 /sbin/udevd --daemon --resolve-n