DistOS 2014W Lecture 1 - Revision history

Eapache: cleanup

2014-04-20T17:59:53Z

cleanup

Alp: Typo.

2014-03-25T14:40:36Z

Typo.

← Older revision		Revision as of 14:40, 25 March 2014
Line 11:		Line 11:
	* Manages synchronization and concurrency issues		* Manages synchronization and concurrency issues

	An OS can be defined by the role it plays in the programming of systems. It takes care of resource management and creates abstraction. An OS turns hardware into the computer/API/interface ~~"""~~want~~"""~~ to program.		An OS can be defined by the role it plays in the programming of systems. It takes care of resource management and creates abstraction. An OS turns hardware into the computer/API/interface '''want''' to program.

	This is similar to how the browser is becoming the OS of the web. The browser is		This is similar to how the browser is becoming the OS of the web. The browser is

Alp: Trivial English semantic fixes.

2014-03-25T14:39:47Z

Trivial English semantic fixes.

← Older revision		Revision as of 14:39, 25 March 2014
Line 28:		Line 28:
	the way of truth. These concepts to do not fit into well defined classes.		the way of truth. These concepts to do not fit into well defined classes.

	~~'''Anil's~~ definition~~''' (following up on the similar note on what~~ a ~~traditional~~ OS ~~is, as seen above): "taking~~ the distributed pieces of a system ~~you have~~ and		To draw parallels to our previous definition of operating systems, a distributed OS takes the distributed pieces of a system, and turn it into the system you want.
	~~turning~~ it into the system you ~~WANT~~."

	It is good to think about about DOSes within the context of who/what is in		It is good to think about about DOSes within the context of who/what is in
	control, in terms of who makes and enforces decisions in DOSes. In essence, who is in charge? The traditional kernel-process model is a dictatorship~~. Authoritarian~~		control, in terms of who makes and enforces decisions in DOSes. In essence, who is in charge? The traditional kernel-process model is a dictatorship, an authoritarian
	model of control. The kernel controls what lives or dies. The internet, by		model of control. The kernel controls what lives or dies. The internet, incontrast, is decentralised (eg. DNS&emdash;to some extent, ignoring centralized roots). Distributed systems may have distributed
	~~contrast~~, is decentralised (eg. DNS). Distributed systems may have distributed		policies where there is not one source of power. Even in DOS we see instances of authoritarian/centralized approaches one example being the walled garden model employed by Apple's iOS. Anil's observation is that centralized systems has an inherent fragility built into and these kind of systems come into existence and disappear after a while. Examples being AOL, Myspace. Even the Facebook also looks to be a possible candidate for a similar fate. Also, concentrations on policy will tend to fall apart in the future.
	policies where there is not one source of power. Even in DOS ~~paradigm~~ we ~~can~~ see instances of authoritarian/centralized approaches one example being the walled garden model employed by Apple's iOS. Anil's observation is that centralized systems has an inherent fragility built into and these kind of systems come into existence and disappear after a while. Examples being AOL, Myspace. Even the Facebook also looks to be a possible candidate for a similar fate. Also, concentrations on policy will tend to fall apart in the future.

Alp: Trivial English syntactic fixes.

2014-03-25T14:33:29Z

Trivial English syntactic fixes.

Alp: Semantic markup fixup.

2014-03-25T14:14:14Z

Semantic markup fixup.

← Older revision		Revision as of 14:14, 25 March 2014
Line 1:		Line 1:
	~~'''~~What is an OS?~~'''~~ An OS allows you to run on (slightly) different hardware. Here are some ideas of what and OS could mean and some functionalities and responsibilities that OSes include::		== What is an OS? ==

			An OS allows you to run on (slightly) different hardware. Here are some ideas of what and OS could mean and some functionalities and responsibilities that OSes include::
	* A hardware abstraction such that hardware resources can be accessed by software		* A hardware abstraction such that hardware resources can be accessed by software
	* Provides consistent execution environment, which hardware doesn't provide (ie. code written to interface -- think portable code)		* Provides consistent execution environment, which hardware doesn't provide (ie. code written to interface -- think portable code)
Line 16:		Line 18:
	etc.), the browser abstracts the device's hardware and OS away.		etc.), the browser abstracts the device's hardware and OS away.

	~~'''So, what's~~ a distributed OS?~~'''~~		== What is a distributed OS? ==

	Anil prefers to think of this 'logically' than functionally/physically. This is		Anil prefers to think of this 'logically' than functionally/physically. This is

Gbooth at 19:49, 14 January 2014

2014-01-14T19:49:16Z

@@ Line 1: / Line 1: @@
-'''What is an OS?''' Here are some ideas of what it could mean:
+'''What is an OS?''' An OS allows you to run on (slightly) different hardware. Here are some ideas of what and OS could mean and some functionalities and responsibilities that OSes include::
-* a hardware abstraction
+* A hardware abstraction such that hardware resources can be accessed by software
-* Consistent execution environment. (ie. code written to interface -- think portable code)
+* Provides consistent execution environment, which hardware doesn't provide (ie. code written to interface -- think portable code)
-* manages I/O
+* Manages I/O (such as user I/O, machine I/O i.e. network I/O, sensors, videos, etc.)
-* Resource management/Multiplexing
+* Resource management through multiplexing and policy use
 * Communication infrastructure (example Inter Process Communication mechanisms) between the users (process, applications) of the Operating System.
 An OS can be defined by the role it plays in the programming of systems. It takes care of resource management and creates abstraction. An OS turns hardware into the computer/api/interface you WANT to program.
@@ Line 23: / Line 26: @@
 the way of truth. These concepts to do not fit into well defined classes.
-'''Anil's definition''': "taking the distributed pieces of a system you have and
+'''Anil's definition''' (following up on the similar note on what a traditional OS is, as seen above): "taking the distributed pieces of a system you have and
 turning it into the system you WANT."
 It is good to think about about DOS's within the context of who/what is in
-control, in terms of who makes and enforces decisions in DOS. The traditional kernel-process model is a dictatorship. Authoritarian
+control, in terms of who makes and enforces decisions in DOS. In essence, who is in charge? The traditional kernel-process model is a dictatorship. Authoritarian
 model of control. The kernel controls what lives or dies.  The internet, by
 contrast, is decentralised (eg. DNS). Distributed systems may have distributed
-policies where there is not one source of power.Even in DOS paradigm we can see instances of authoritarian/centralized approaches one example being the walled garden model employed by Apple iOS. Anil's observation is that centralized systems has an inherent fragility built into and these kind of systems comes to existence and disappear after a while. Examples being AOL, Myspace. Even the Facebook also looks to be a possible candidate for a similar fate.
+policies where there is not one source of power. Even in DOS paradigm we can see instances of authoritarian/centralized approaches one example being the walled garden model employed by Apple iOS. Anil's observation is that centralized systems has an inherent fragility built into and these kind of systems come into existence and disappear after a while. Examples being AOL, Myspace. Even the Facebook also looks to be a possible candidate for a similar fate. Also, concentrations on policy will tend to fall apart in the future.

Aschoenr at 15:10, 14 January 2014

2014-01-14T15:10:35Z

← Older revision		Revision as of 15:10, 14 January 2014
Line 36:		Line 36:


	'''''*This section below needs to be integrated into the notes above. Anyone can feel free to do this'''''		'''''This section below needs to be integrated into the notes above. Anyone can feel free to do this'''''

Aschoenr at 05:39, 14 January 2014

2014-01-14T05:39:48Z

← Older revision		Revision as of 05:39, 14 January 2014
Line 36:		Line 36:


	Yuan Liu's Notes		'''''*This section below needs to be integrated into the notes above. Anyone can feel free to do this'''''


			Yuan Liu's Notes

	'''(Normal) Operating Systems'''		'''(Normal) Operating Systems'''

Sjoy: add/edit information supplementing notes from Lecture 1

2014-01-13T04:45:32Z

add/edit information supplementing notes from Lecture 1

Cdelahou at 18:18, 8 January 2014

2014-01-08T18:18:33Z

← Older revision		Revision as of 18:18, 8 January 2014
Line 23:		Line 23:

	'''Anil's definition''': "taking the distributed pieces of a system you have and		'''Anil's definition''': "taking the distributed pieces of a system you have and
	turning it into the system you WANT. ~~(sic)~~"		turning it into the system you WANT."

	It is good to think about about DOS's within the context of who/what is in		It is good to think about about DOS's within the context of who/what is in

← Older revision		Revision as of 17:59, 20 April 2014
Line 1:		Line 1:
	== What is an OS? ==		== What is an Operating System? ==

	An OS allows you to run on (slightly) different hardware. Here are ~~some ideas~~ of what ~~and~~ OS ~~could mean and some functionalities and responsibilities that OSes include~~:		In general, an OS allows you to run the same applications on (slightly) different hardware. Here are a few thoughts on what the responsibilities and functionality are of modern operating systems, and what we expect from something calling itself an OS:
	* A hardware abstraction such that hardware resources can be accessed by software		* A hardware abstraction layer such that diverse hardware resources can be accessed uniformly by software
	* ~~Provides~~ consistent execution environment, which hardware doesn't provide (ie. code written to interface &emdash; think portable code)		* A consistent execution environment, which hardware doesn't provide (ie. code written to interface &emdash; think portable code)
	* ~~Manages~~ I/O (such as user I/O, machine I/O i.e. network I/O, sensors, videos, etc.)		* Management of I/O (such as user I/O, machine I/O i.e. network I/O, sensors, videos, etc.)
	* Resource management through multiplexing and policy use		* Resource management through multiplexing and policy use
	** Multiplexing (sharing): one resource wanted by multiple users		** Multiplexing (sharing): one resource wanted by multiple users
	* Communication infrastructure (example inter process communication ~~mechanisms~~) between the users (process, applications) of the operating system.		* Communication infrastructure (for example inter-process communication) between the users (process, applications) of the operating system.
	* ~~OS turns a computer you want to a computer you want to program~~		* Management of synchronization and concurrency issues
	* Manages synchronization and concurrency issues

	An OS can be defined by the role it plays in the programming of systems. It takes care of resource management and creates abstraction. An OS turns hardware into the computer/API/interface '''want''' to program.		We could also say that an OS turns the computer you have into the computer you want. An OS can be defined by the role it plays in the programming of systems. It takes care of resource management and creates abstraction. An OS turns hardware into the computer/API/interface we '''want''' to program.

	This is similar to how the browser is becoming the OS of the web. The browser is		This is similar to how the browser is becoming the OS of the web. The browser is
Line 20:		Line 19:
	== What is a distributed OS? ==		== What is a distributed OS? ==

	Anil prefers to think of this 'logically' than functionally/physically. This is		Anil prefers to think of this 'logically' rather than functionally/physically. This is
	because the old distributed operating system (DOS) model applies to today'~~s systems~~		because the old distributed operating system (DOS) model applies to systems today which we
	(ie. managing multiple cores, etc). The traditional definition is systems that		don't consider distributed (ie. managing multiple cores, etc). The traditional definition is systems that
	manage their resources over a Network.		manage their resources over a Network.

Line 32:		Line 31:
	It is good to think about about DOSes within the context of who/what is in		It is good to think about about DOSes within the context of who/what is in
	control, in terms of who makes and enforces decisions in DOSes. In essence, who is in charge? The traditional kernel-process model is a dictatorship, an authoritarian		control, in terms of who makes and enforces decisions in DOSes. In essence, who is in charge? The traditional kernel-process model is a dictatorship, an authoritarian
	model of control. The kernel controls what lives or dies. The internet, ~~incontrast~~, is decentralised (eg. DNS&emdash;to some extent, ignoring centralized roots). Distributed systems may have distributed		model of control. The kernel controls what lives or dies. The internet, in contrast, is decentralised (eg. DNS&emdash;to some extent, ignoring centralized roots). Distributed systems may have distributed
	policies where there is not one source of power. Even in DOS we see instances of authoritarian/centralized approaches one example being the walled garden model employed by Apple's iOS. Anil's observation is that centralized systems has an inherent fragility built into and these kind of systems come into existence and disappear after a while. Examples being AOL, Myspace. Even ~~the~~ Facebook also looks to be a possible candidate for a similar fate. Also, concentrations on policy will tend to fall apart in the future.		policies where there is not one source of power. Even in DOS we see instances of authoritarian/centralized approaches one example being the walled garden model employed by Apple's iOS. Anil's observation is that centralized systems has an inherent fragility built into and these kind of systems come into existence and disappear after a while. Examples being AOL, Myspace. Even Facebook also looks to be a possible candidate for a similar fate. Also, concentrations on policy will tend to fall apart in the future.

← Older revision		Revision as of 14:33, 25 March 2014
Line 1:		Line 1:
	== What is an OS? ==		== What is an OS? ==

	An OS allows you to run on (slightly) different hardware. Here are some ideas of what and OS could mean and some functionalities and responsibilities that OSes include::		An OS allows you to run on (slightly) different hardware. Here are some ideas of what and OS could mean and some functionalities and responsibilities that OSes include:
	* A hardware abstraction such that hardware resources can be accessed by software		* A hardware abstraction such that hardware resources can be accessed by software
	* Provides consistent execution environment, which hardware doesn't provide (ie. code written to interface -- think portable code)		* Provides consistent execution environment, which hardware doesn't provide (ie. code written to interface &emdash; think portable code)
	* Manages I/O (such as user I/O, machine I/O i.e. network I/O, sensors, videos, etc.)		* Manages I/O (such as user I/O, machine I/O i.e. network I/O, sensors, videos, etc.)
	* Resource management through multiplexing and policy use		* Resource management through multiplexing and policy use
	** Multiplexing (sharing): one resource wanted by multiple users		** Multiplexing (sharing): one resource wanted by multiple users
	* Communication infrastructure (example ~~Inter Process Communication~~ mechanisms) between the users (process, applications) of the ~~Operating System~~.		* Communication infrastructure (example inter process communication mechanisms) between the users (process, applications) of the operating system.
	* OS turns a computer you want to a computer you want to program		* OS turns a computer you want to a computer you want to program
	* Manages synchronization and concurrency issues		* Manages synchronization and concurrency issues

	An OS can be defined by the role it plays in the programming of systems. It takes care of resource management and creates abstraction. An OS turns hardware into the computer/~~api~~/interface ~~you WANT~~ to program.		An OS can be defined by the role it plays in the programming of systems. It takes care of resource management and creates abstraction. An OS turns hardware into the computer/API/interface """want""" to program.

	This is similar to how the browser is becoming the OS of the web. The browser is		This is similar to how the browser is becoming the OS of the web. The browser is
Line 31:		Line 31:
	turning it into the system you WANT."		turning it into the system you WANT."

	It is good to think about about ~~DOS's~~ within the context of who/what is in		It is good to think about about DOSes within the context of who/what is in
	control, in terms of who makes and enforces decisions in ~~DOS~~. In essence, who is in charge? The traditional kernel-process model is a dictatorship. Authoritarian		control, in terms of who makes and enforces decisions in DOSes. In essence, who is in charge? The traditional kernel-process model is a dictatorship. Authoritarian
	model of control. The kernel controls what lives or dies. The internet, by		model of control. The kernel controls what lives or dies. The internet, by
	contrast, is decentralised (eg. DNS). Distributed systems may have distributed		contrast, is decentralised (eg. DNS). Distributed systems may have distributed
	policies where there is not one source of power. Even in DOS paradigm we can see instances of authoritarian/centralized approaches one example being the walled garden model employed by Apple iOS. Anil's observation is that centralized systems has an inherent fragility built into and these kind of systems come into existence and disappear after a while. Examples being AOL, Myspace. Even the Facebook also looks to be a possible candidate for a similar fate. Also, concentrations on policy will tend to fall apart in the future.		policies where there is not one source of power. Even in DOS paradigm we can see instances of authoritarian/centralized approaches one example being the walled garden model employed by Apple's iOS. Anil's observation is that centralized systems has an inherent fragility built into and these kind of systems come into existence and disappear after a while. Examples being AOL, Myspace. Even the Facebook also looks to be a possible candidate for a similar fate. Also, concentrations on policy will tend to fall apart in the future.

← Older revision		Revision as of 04:45, 13 January 2014
Line 4:		Line 4:
	* manages I/O		* manages I/O
	* Resource management/Multiplexing		* Resource management/Multiplexing
			* Communication infrastructure (example Inter Process Communication mechanisms) between the users (process, applications) of the Operating System.

	An OS can be defined as the role it plays in the programming of systems. It takes care of resource management and creates abstraction. An OS turns hardware into the computer/api/interface you WANT to program.		An OS can be defined by the role it plays in the programming of systems. It takes care of resource management and creates abstraction. An OS turns hardware into the computer/api/interface you WANT to program.

	This is similar to how the browser is becoming the OS of the web. The browser is		This is similar to how the browser is becoming the OS of the web. The browser is
Line 16:		Line 17:
	Anil prefers to think of this 'logically' than functionally/physically. This is		Anil prefers to think of this 'logically' than functionally/physically. This is
	because the old distributed operating system (DOS) model applies to today's systems		because the old distributed operating system (DOS) model applies to today's systems
	(ie. managing multiple cores, etc). The ~~tradition~~ definition is systems that		(ie. managing multiple cores, etc). The traditional definition is systems that
	manage their resources over ~~TCP/IP~~.		manage their resources over a Network.

	A lot of these definitions are hard to peg down because simplicity always gets in		A lot of these definitions are hard to peg down because simplicity always gets in
Line 26:		Line 27:

	It is good to think about about DOS's within the context of who/what is in		It is good to think about about DOS's within the context of who/what is in
	control. The traditional kernel-process model is a dictatorship. Authoritarian		control, in terms of who makes and enforces decisions in DOS. The traditional kernel-process model is a dictatorship. Authoritarian
	model of control. The kernel controls what lives or dies. The internet, by		model of control. The kernel controls what lives or dies. The internet, by
	contrast, is decentralised (eg. DNS). Distributed systems may have distributed		contrast, is decentralised (eg. DNS). Distributed systems may have distributed
	policies where there is not one source of power.		policies where there is not one source of power.Even in DOS paradigm we can see instances of authoritarian/centralized approaches one example being the walled garden model employed by Apple iOS. Anil's observation is that centralized systems has an inherent fragility built into and these kind of systems comes to existence and disappear after a while. Examples being AOL, Myspace. Even the Facebook also looks to be a possible candidate for a similar fate.