DistOS 2015W Session 4 - Revision history

Mohamedahmed: /* Capablities: */

2015-04-28T05:38:23Z

Capablities:

← Older revision		Revision as of 05:38, 28 April 2015
Line 17:		Line 17:

	= Amoeba Operating System =		= Amoeba Operating System =

			The Ameoba research project with the goal at understanding how to connect multiple computers in a seamless way. The main goal of this was to build a distributed system that is transparent to the users. This was different from a network operating system where a user would be aware of the separate nodes it was accessing.

	=== Capablities: ===		=== Capablities: ===
Line 30:		Line 32:
	* The third field is the right field which contains a bit map telling which operation the holder of the capability may performed		* The third field is the right field which contains a bit map telling which operation the holder of the capability may performed
	* X11 Window management		* X11 Window management


	=== Thread Management: ===		=== Thread Management: ===

Jasons: /* Andrew File System */

2015-04-20T09:51:01Z

Andrew File System

← Older revision		Revision as of 09:51, 20 April 2015
Line 10:		Line 10:

	Given all this, AFS was suitable for working with small files, not large ones, limiting its usefulness. It is also notoriously annoying to set up as it is geared towards university-sized networks, further limiting its success.		Given all this, AFS was suitable for working with small files, not large ones, limiting its usefulness. It is also notoriously annoying to set up as it is geared towards university-sized networks, further limiting its success.

			*Kerberos protocol
			**authentication protocol using time based ticket
			**single sign on system to authenticate and use other services
			**AFS uses Kerberos for authentication, and implements access control lists on directories for users and groups.

	= Amoeba Operating System =		= Amoeba Operating System =

Abeinges: /* Andrew File System */

2015-04-06T04:45:54Z

Andrew File System

← Older revision		Revision as of 04:45, 6 April 2015
Line 2:		Line 2:
	AFS (Andrew File System) was set up as a direct response to NFS. Essentially universities found issues when they tried to scale NFS in a way that would allow them to share files amongst their staff effectively. AFS was more scalable than NFS because read-write operations happened locally before they were committed to the server (data store).		AFS (Andrew File System) was set up as a direct response to NFS. Essentially universities found issues when they tried to scale NFS in a way that would allow them to share files amongst their staff effectively. AFS was more scalable than NFS because read-write operations happened locally before they were committed to the server (data store).

	Since AFS ~~copied~~ files locally when they were opened and only ~~sent~~ the data back when they ~~were~~ closed, all operations ~~during that time~~ are very fast and do need the network. NFS works with files remotely, so there is no data to transfer when opening/closing the file, making those operations instant.		Since AFS copies files locally when they were opened and only sends the data back when they are closed, all operations between opening and closing the file are very fast and do not need to access the network. NFS works with files remotely, so there is no data to transfer when opening/closing the file, making those operations instant.

	There are several problems with this design, however.		There are several problems with this design, however:
	* The local system must have enough space to temporarily store the file.		* The local system must have enough space to temporarily store the file.
	* Opening and closing the files requires a lot of bandwidth for large files. To read even a single byte, the entire file must be retrieved (later versions remedied this).		* Opening and closing the files requires a lot of bandwidth for large files. To read even a single byte, the entire file must be retrieved (later versions remedied this).
	* If the close operation fails, the system will not have the updated version of the file. Many programs don't even check the return value of the close operation, giving users the false impression that everything went well.		* If the close operation fails, the system will not have the updated version of the file. Many programs are designed around local filesystems, and therefore don't even check the return value of the close operation (as this is unlikely to fail on a local FS), giving users the false impression that everything went well.

	Given all this, AFS was suitable for working with small files, not large ones, limiting its usefulness. It is also notoriously annoying to set up as it is geared towards university-sized networks, further limiting its success.		Given all this, AFS was suitable for working with small files, not large ones, limiting its usefulness. It is also notoriously annoying to set up as it is geared towards university-sized networks, further limiting its success.


	= Amoeba Operating System =		= Amoeba Operating System =

Aimbot: /* Supported architectures */ Changed HTML to wiki markup

2015-02-28T17:01:23Z

Supported architectures: Changed HTML to wiki markup

← Older revision		Revision as of 17:01, 28 February 2015
Line 44:		Line 44:
	== Supported architectures ==		== Supported architectures ==
	Many different processor architectures are supported including:		Many different processor architectures are supported including:
	~~<ul>~~		* i80386 (Pentium)
	~~<li>~~ i80386(Pentium)~~</li>~~		* 68K
	~~<li>~~68K~~</li>~~		* SPARC
	~~<li>~~SPARC~~</li>~~
	~~</ul>~~

	= The V Distributed System =		= The V Distributed System =

Ameti073: /* Supported processor architectures */

2015-02-11T03:37:09Z

Supported processor architectures

← Older revision		Revision as of 03:37, 11 February 2015
Line 42:		Line 42:
	Pool processors are group of CPUs that are dynamically allocated as user needs. When a program is executed, any of the available processor run.		Pool processors are group of CPUs that are dynamically allocated as user needs. When a program is executed, any of the available processor run.

	== Supported ~~processor~~ architectures ==		== Supported architectures ==
	Many different processor architectures are supported including:		Many different processor architectures are supported including:
	<ul>		<ul>

Ameti073: /* Pool processors */

2015-02-11T03:36:41Z

Pool processors

← Older revision		Revision as of 03:36, 11 February 2015
Line 41:		Line 41:
	== Pool processors ==		== Pool processors ==
	Pool processors are group of CPUs that are dynamically allocated as user needs. When a program is executed, any of the available processor run.		Pool processors are group of CPUs that are dynamically allocated as user needs. When a program is executed, any of the available processor run.

			== Supported processor architectures ==
			Many different processor architectures are supported including:
			<ul>
			<li> i80386(Pentium)</li>
			<li>68K</li>
			<li>SPARC</li>
			</ul>

	= The V Distributed System =		= The V Distributed System =

Ameti073: /* Unique features */

2015-02-11T03:33:45Z

Unique features

← Older revision		Revision as of 03:33, 11 February 2015
Line 27:		Line 27:
	* X11 Window management		* X11 Window management


	~~= Unique features =~~

	~~== Pool processors ==~~
	~~Pool processors are group of CPUs that are dynamically allocated as user needs. When a program is executed, any of the available processor run.~~

	=== Thread Management: ===		=== Thread Management: ===

Ameti073: /* Thread Management: */

2015-02-11T03:32:50Z

Thread Management:

← Older revision		Revision as of 03:32, 11 February 2015
Line 41:		Line 41:
	* Buttlet thread the mutex		* Buttlet thread the mutex
	* The careful reader may have noticed that user process can pull 813kbytes/sec		* The careful reader may have noticed that user process can pull 813kbytes/sec

			= Unique features =

			== Pool processors ==
			Pool processors are group of CPUs that are dynamically allocated as user needs. When a program is executed, any of the available processor run.

	= The V Distributed System =		= The V Distributed System =

Ameti073: /* Pool processors */

2015-02-11T03:32:21Z

Pool processors

← Older revision		Revision as of 03:32, 11 February 2015
Line 31:		Line 31:

	== Pool processors ==		== Pool processors ==
			Pool processors are group of CPUs that are dynamically allocated as user needs. When a program is executed, any of the available processor run.

	=== Thread Management: ===		=== Thread Management: ===
Line 40:		Line 41:
	* Buttlet thread the mutex		* Buttlet thread the mutex
	* The careful reader may have noticed that user process can pull 813kbytes/sec		* The careful reader may have noticed that user process can pull 813kbytes/sec


	= The V Distributed System =		= The V Distributed System =

Ameti073: /* Capablities: */

2015-02-11T03:30:17Z

Capablities:

← Older revision		Revision as of 03:30, 11 February 2015
Line 26:		Line 26:
	* The third field is the right field which contains a bit map telling which operation the holder of the capability may performed		* The third field is the right field which contains a bit map telling which operation the holder of the capability may performed
	* X11 Window management		* X11 Window management


			= Unique features =

			== Pool processors ==

	=== Thread Management: ===		=== Thread Management: ===