<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://homeostasis.scs.carleton.ca/wiki/index.php?action=history&amp;feed=atom&amp;title=Talk%3ADistOS_2015W_Session_4</id>
	<title>Talk:DistOS 2015W Session 4 - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://homeostasis.scs.carleton.ca/wiki/index.php?action=history&amp;feed=atom&amp;title=Talk%3ADistOS_2015W_Session_4"/>
	<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=Talk:DistOS_2015W_Session_4&amp;action=history"/>
	<updated>2026-06-02T21:53:39Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.42.1</generator>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=Talk:DistOS_2015W_Session_4&amp;diff=19730&amp;oldid=prev</id>
		<title>Deepshree: Created page with &quot;&#039;&#039;&#039;Amebo Operating System: Capablities&#039;&#039;&#039;  	• Pointer to the object 	• Capability assigning right to perform to some operation to the object ticket  	• Communicate wide ...&quot;</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=Talk:DistOS_2015W_Session_4&amp;diff=19730&amp;oldid=prev"/>
		<updated>2015-01-27T18:25:28Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;&amp;#039;&amp;#039;&amp;#039;Amebo Operating System: Capablities&amp;#039;&amp;#039;&amp;#039;  	• Pointer to the object 	• Capability assigning right to perform to some operation to the object ticket  	• Communicate wide ...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&amp;#039;&amp;#039;&amp;#039;Amebo Operating System: Capablities&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
	• Pointer to the object&lt;br /&gt;
	• Capability assigning right to perform to some operation to the object ticket &lt;br /&gt;
	• Communicate wide area network &lt;br /&gt;
	• a kind of ticket or key that allows the holder of the capa- bility to perform some (not neces- sarily all) &lt;br /&gt;
	• Each user process owns some collection of capabilities, which together define the set of objects it may access and the types of operations that my ne performed on each &lt;br /&gt;
	• After the server has performed the operation, it sends back a reply message that unblocks the client &lt;br /&gt;
	• Sending messages, blocking and accepting forms the remote procedure call that can be encapsulate using to make entire remote operation look like local procedure &lt;br /&gt;
	• Second field:  used by the sever to identify which of its objects is being addressed server port and object number identify object which operation to performed  &lt;br /&gt;
	• Generates 48-bit random number     &lt;br /&gt;
	• The third field is the right field which contains a bit map telling which operation the holder of the capability  may performed &lt;br /&gt;
	&lt;br /&gt;
	&lt;br /&gt;
	&lt;br /&gt;
	&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Thread Management:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
	• Same process have multiple thread and each process has its own registered counter and stack &lt;br /&gt;
	• Behave like process&lt;br /&gt;
	• It can synchronized using mutex semaphore &lt;br /&gt;
	• File: Multiple thread, &lt;br /&gt;
	• Blocked when there&amp;#039;s multiple threads &lt;br /&gt;
	• Buttlet thread the mutex&lt;br /&gt;
	• The careful reader may have noticed that user process can pull 813kbytes/sec&lt;/div&gt;</summary>
		<author><name>Deepshree</name></author>
	</entry>
</feed>