<?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=DistOS_2023W_2023-01-16</id>
	<title>DistOS 2023W 2023-01-16 - 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=DistOS_2023W_2023-01-16"/>
	<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=DistOS_2023W_2023-01-16&amp;action=history"/>
	<updated>2026-04-08T04:55:22Z</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=DistOS_2023W_2023-01-16&amp;diff=24287&amp;oldid=prev</id>
		<title>Soma: Created page with &quot;Video from the second half of class is available in Brightspace in the Zoom portal.  ==Notes==  &lt;pre&gt; Lecture 3 ---------  Group reports  - can be bullet points, but paragraphs are better  - should be self-contained, should be readable by someone who hasn&#039;t done the readings     - but you don&#039;t have to summarize the entire paper, just make the points you discussed clear      Monday group reports are due Friday Wednesday group reports are due Monday (and responses are due...&quot;</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=DistOS_2023W_2023-01-16&amp;diff=24287&amp;oldid=prev"/>
		<updated>2023-01-16T18:00:33Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;Video from the second half of class is available in Brightspace in the Zoom portal.  ==Notes==  &amp;lt;pre&amp;gt; Lecture 3 ---------  Group reports  - can be bullet points, but paragraphs are better  - should be self-contained, should be readable by someone who hasn&amp;#039;t done the readings     - but you don&amp;#039;t have to summarize the entire paper, just make the points you discussed clear      Monday group reports are due Friday Wednesday group reports are due Monday (and responses are due...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Video from the second half of class is available in Brightspace in the Zoom portal.&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Lecture 3&lt;br /&gt;
---------&lt;br /&gt;
&lt;br /&gt;
Group reports&lt;br /&gt;
 - can be bullet points, but paragraphs are better&lt;br /&gt;
 - should be self-contained, should be readable by someone who hasn&amp;#039;t done the readings&lt;br /&gt;
    - but you don&amp;#039;t have to summarize the entire paper, just make the points you discussed clear&lt;br /&gt;
    &lt;br /&gt;
Monday group reports are due Friday&lt;br /&gt;
Wednesday group reports are due Monday&lt;br /&gt;
(and responses are due Sunday night)&lt;br /&gt;
&lt;br /&gt;
Multics&lt;br /&gt;
 - idea of &amp;quot;utility computing&amp;quot;&lt;br /&gt;
    - that&amp;#039;s why they cared about security&lt;br /&gt;
 - Multics was supposed to be distrubuted, in a sense&lt;br /&gt;
    - terminals everywhere connected by data links (phone lines)&lt;br /&gt;
&lt;br /&gt;
Multics is before computer networking was a thing&lt;br /&gt;
 - distributed system was one mainframe with lots of terminals in remote places&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Resource-Sharing Computer Communications Networks&lt;br /&gt;
 - so, why this paper?&lt;br /&gt;
 - because their discussion is &amp;quot;distributed operating systems&amp;quot;&lt;br /&gt;
&lt;br /&gt;
What is this paper arguing for?  What is the technical innovation?&lt;br /&gt;
 - what is the innovation relative to?&lt;br /&gt;
&lt;br /&gt;
Circuit-switched networks - old&lt;br /&gt;
Packet-switched networks - new&lt;br /&gt;
&lt;br /&gt;
What were circuit-switched networks designed for?&lt;br /&gt;
What are their key advantages?&lt;br /&gt;
&lt;br /&gt;
with circuit switched, as long as someone was on a phone call,&lt;br /&gt;
there was a &amp;quot;wire&amp;quot; dedicated to to that call&lt;br /&gt;
  - and for long distance, that was a significant amount of resources,&lt;br /&gt;
    hence the cost&lt;br /&gt;
&lt;br /&gt;
Originally this was all analog, but then it became digital&lt;br /&gt;
 - but idea was still to have a dedicated connection between callers&lt;br /&gt;
 - how do you make a &amp;quot;virtual&amp;quot; wire?&lt;br /&gt;
    - can use packets to send data&lt;br /&gt;
    - but have explicit bandwidth reservations and latency requirements&lt;br /&gt;
      - resources are still reserved for each call to ensure quality&lt;br /&gt;
 - this is circuit-switched networks&lt;br /&gt;
&lt;br /&gt;
Packet-switched networks are different&lt;br /&gt;
 - each packet is considered independently&lt;br /&gt;
 - normally, delivery is &amp;quot;best effort&amp;quot; - no resource reservation&lt;br /&gt;
   - so packets can get dropped at any time&lt;br /&gt;
   - endpoints have to handle retransmission, network won&amp;#039;t do it for you&lt;br /&gt;
&lt;br /&gt;
Packet-switched networks are fundamentally more efficient&lt;br /&gt;
 - no wasted resources on reservations&lt;br /&gt;
 - and is okay because we&amp;#039;re transmitting data, delays are fine&lt;br /&gt;
   (voice data is much more latency sensitive)&lt;br /&gt;
&lt;br /&gt;
What did they want this network for?&lt;br /&gt;
 - file transfers&lt;br /&gt;
 - email (which is a kind of file transfer)&lt;br /&gt;
 - remote access to computers (remote terminals)&lt;br /&gt;
&lt;br /&gt;
What was an IMP equivalent to?&lt;br /&gt;
 - mostly like an ethernet interface&lt;br /&gt;
 - but also aspects of a router&lt;br /&gt;
&lt;br /&gt;
Why was it called the ARPANet?&lt;br /&gt;
 - (D)ARPA - one of the research arms of the US military&lt;br /&gt;
&lt;br /&gt;
They are talking about the Internet and IP packets, that&amp;#039;s what they built&lt;br /&gt;
&lt;br /&gt;
How to read a research paper?&lt;br /&gt;
 - read the intro and discussion/conclusion first&lt;br /&gt;
    - see what the authors were trying to say&lt;br /&gt;
 - look at the figures, see what they say&lt;br /&gt;
 - look at background/related work, what other systems is this connected to&lt;br /&gt;
 - look at results - why do they think their system is any good?&lt;br /&gt;
 - then read the paper from the beginning&lt;br /&gt;
 - a pure linear read is almost never the best idea&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Soma</name></author>
	</entry>
</feed>