COMP 3000 Essay 1 2010 Question 4 - Revision history

Soma: Unprotected "COMP 3000 Essay 1 2010 Question 4"

2010-11-08T15:33:18Z

Unprotected "COMP 3000 Essay 1 2010 Question 4"

← Older revision	Revision as of 15:33, 8 November 2010
(No difference)

Soma: /* Motivation */

2010-10-17T17:28:37Z

Motivation

← Older revision		Revision as of 17:28, 17 October 2010
Line 61:		Line 61:
	matched interface prevents it from working at all.		matched interface prevents it from working at all.

	This is the sole purpose for creating SPIN. The team had to meet three important features to make this work, a Flexible kernel with safe extensions and a good overall performance. Operating systems based on C/C++ are too general that handle many applications. Therefore, some programs may fall through the cracks and suffer the lack of safety and performance. The goal for SPIN however, was to create a specialized operating system that can run a range of applications without sacrificing safety or performance. This system would allow the user programs and applications to manipulate and change the system’s interface to load and access the data or memory needed safely and with a good overall performance. This was possible through the type safe extensions of Modula-3. Unlike C/C++, Modula-3 is considered a safe language; it guarantees the protection of the kernel from dangerous extension by forcing them to interact with the kernel through specific interfaces. ~~Furthermore, the~~ extensions are executed in the ~~virtual~~ address space not ~~the~~ user space.		This is the sole purpose for creating SPIN. The team had to meet three important features to make this work, a Flexible kernel with safe extensions and a good overall performance. Operating systems based on C/C++ are too general that handle many applications. Therefore, some programs may fall through the cracks and suffer the lack of safety and performance. The goal for SPIN however, was to create a specialized operating system that can run a range of applications without sacrificing safety or performance. This system would allow the user programs and applications to manipulate and change the system’s interface to load and access the data or memory needed safely and with a good overall performance. This was possible through the type safe extensions of Modula-3. Unlike C/C++, Modula-3 is considered a safe language; it guarantees the protection of the kernel from dangerous extension by forcing them to interact with the kernel through specific interfaces. Such safety is essential because extensions are executed in the kernel's address space in supervisor mode, not in user space.

	===Achievements===		===Achievements===

Soma: Protected "COMP 3000 Essay 1 2010 Question 4" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

2010-10-15T13:35:04Z

Protected "COMP 3000 Essay 1 2010 Question 4" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

← Older revision	Revision as of 13:35, 15 October 2010
(No difference)

Mkugler: /* Problems */

2010-10-15T09:56:44Z

Problems

← Older revision		Revision as of 09:56, 15 October 2010
Line 100:		Line 100:

	It is difficult to accurately discern what if any problems arose within Oberon. It was successfully completed and implemented for use with the Ceres system. Due to the safe nature of the Oberon language which the operating system was built off of, run-time errors within Oberon were minimized. The language itself however did and still does suffer from some flaws in the form of certain safety features commonly implemented in other safe languages being omitted, which can potentially cause problems for developers who are unaware of the absence and are expecting them to be present.		It is difficult to accurately discern what if any problems arose within Oberon. It was successfully completed and implemented for use with the Ceres system. Due to the safe nature of the Oberon language which the operating system was built off of, run-time errors within Oberon were minimized. The language itself however did and still does suffer from some flaws in the form of certain safety features commonly implemented in other safe languages being omitted, which can potentially cause problems for developers who are unaware of the absence and are expecting them to be present.


	====Current Status====		====Current Status====

Mkugler: /* Oberon */

2010-10-15T09:56:36Z

Oberon

← Older revision		Revision as of 09:56, 15 October 2010
Line 98:		Line 98:

	====Problems====		====Problems====

			It is difficult to accurately discern what if any problems arose within Oberon. It was successfully completed and implemented for use with the Ceres system. Due to the safe nature of the Oberon language which the operating system was built off of, run-time errors within Oberon were minimized. The language itself however did and still does suffer from some flaws in the form of certain safety features commonly implemented in other safe languages being omitted, which can potentially cause problems for developers who are unaware of the absence and are expecting them to be present.


	====Current Status====		====Current Status====

Mkugler: /* Current Status */

2010-10-15T09:44:00Z

Current Status

← Older revision		Revision as of 09:44, 15 October 2010
Line 103:		Line 103:
	The original Oberon has ceased further development for a number of years now, but this is not the case for operating systems based around the Oberon language. ETH Zurich has since developed a number of additional systems with the knowledge gained from the first Oberon operating system.		The original Oberon has ceased further development for a number of years now, but this is not the case for operating systems based around the Oberon language. ETH Zurich has since developed a number of additional systems with the knowledge gained from the first Oberon operating system.

	The latest of these is the Bluebottle OS, also known as A2. It is an efficient environment, with multiprocessor support, while retaining the compact size and text-based interface of its predecessor.		The latest of these is the Bluebottle OS, also known as A2. It is an efficient environment, with multiprocessor support, while retaining the compact size and text-based interface of its predecessor. While the original Oberon was targeted for simply in-house hardware, both the operating system and the language has since been ported to a variety of platforms.

	==Smalltalk Based==		==Smalltalk Based==

Mkugler: /* References */

2010-10-15T09:39:22Z

References

← Older revision		Revision as of 09:39, 15 October 2010
Line 193:		Line 193:

	University of Washington, Dept. of Computer Science. The SPIN Operating System. [http://www.cs.washington.edu.html]		University of Washington, Dept. of Computer Science. The SPIN Operating System. [http://www.cs.washington.edu.html]

			For Oberon:

			Bluebottle OS. (n.d.). Retrieved February 3, 2010, from Wikipedia: http://en.wikipedia.org/wiki/Bluebottle_OS

			Ceres (workstation). (2010, August 24). Retrieved from Wikipedia: http://en.wikipedia.org/wiki/Ceres_(workstation)

			Native Oberon. (n.d.). Retrieved March 5, 2010, from Wikipedia: http://en.wikipedia.org/wiki/Native_Oberon

			Niklaus Wirth. (2010, October 13). Retrieved from Wikipedia: http://en.wikipedia.org/wiki/Niklaus_Wirth

			NS320xx. (2010, June 30). Retrieved from Wikipedia: http://en.wikipedia.org/wiki/NS320xx

			Oberon (operating system). (2010, September 1). Retrieved from Wikipedia: http://en.wikipedia.org/wiki/Oberon_(operating_system)

			Oberon (programming language). (2010, October 3). Retrieved from Wikipedia: http://en.wikipedia.org/wiki/Oberon_(programming_language)

			Oberon. (2008, July 10). Retrieved from ETH Zurich: http://www.oberon.ethz.ch/

			Wirth, N., & Gutknecht, J. (2005). ETH Oberon. Retrieved from Project Oberon: The Design of an Operating System and Compiler: http://www.oberon.ethz.ch/archives/systemsarchive/sys_genealogy_new

Mkugler: /* Achievements */

2010-10-15T09:26:37Z

Achievements

← Older revision		Revision as of 09:26, 15 October 2010
Line 94:		Line 94:

	Perhaps one of the most interesting features of the Oberon operating system can be seen in a particular version entitled Native Oberon. While most versions of Oberon were incredibly compact, to the point of the entire OS, along with an Oberon language compiler an assorted utilities, being able to fit on a single 3.5" floppy disk, Native Oberon was unique in that it could be run directly from the floppy on bare PC hardware.		Perhaps one of the most interesting features of the Oberon operating system can be seen in a particular version entitled Native Oberon. While most versions of Oberon were incredibly compact, to the point of the entire OS, along with an Oberon language compiler an assorted utilities, being able to fit on a single 3.5" floppy disk, Native Oberon was unique in that it could be run directly from the floppy on bare PC hardware.


	In addition to this uncommon and convenient feature, Oberon also made use of an unconventional text-based user interface. This system allowed for the point-and-click convenience of a GUI, with the versatility of a command line.		In addition to this uncommon and convenient feature, Oberon also made use of an unconventional text-based user interface. This system allowed for the point-and-click convenience of a GUI, with the versatility of a command line.

Mkugler: /* Current Status */

2010-10-15T09:26:24Z

Current Status

← Older revision		Revision as of 09:26, 15 October 2010
Line 101:		Line 101:

	====Current Status====		====Current Status====

			The original Oberon has ceased further development for a number of years now, but this is not the case for operating systems based around the Oberon language. ETH Zurich has since developed a number of additional systems with the knowledge gained from the first Oberon operating system.

			The latest of these is the Bluebottle OS, also known as A2. It is an efficient environment, with multiprocessor support, while retaining the compact size and text-based interface of its predecessor.

	==Smalltalk Based==		==Smalltalk Based==

Mkugler: /* Current Status */

2010-10-15T09:13:46Z

Current Status

← Older revision		Revision as of 09:13, 15 October 2010
Line 76:		Line 76:

	SPIN, and extendible operating systems in general, is becoming the playground for research. The authors of SPIN at the University of Washington are performing projects and continuing the on-going research of improving extendible operating systems. The solutions they might come up with could greatly influence the operating systems as we see them today.		SPIN, and extendible operating systems in general, is becoming the playground for research. The authors of SPIN at the University of Washington are performing projects and continuing the on-going research of improving extendible operating systems. The solutions they might come up with could greatly influence the operating systems as we see them today.


	----		----