From: navid <navid>
Date: Mon, 15 Sep 2008 21:51:20 +0000 (+0000)
Subject: *** empty log message ***
X-Git-Tag: buildscript^6~10
X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=f6848865ba0f28d397d9502e1afe66c7e6cffadc;p=IRC.git

*** empty log message ***
---

diff --git a/Robust/Transactions/Notes/sysgurantees.dvi b/Robust/Transactions/Notes/sysgurantees.dvi
index 5132f879..fb98f11c 100644
Binary files a/Robust/Transactions/Notes/sysgurantees.dvi and b/Robust/Transactions/Notes/sysgurantees.dvi differ
diff --git a/Robust/Transactions/Notes/sysgurantees.tex b/Robust/Transactions/Notes/sysgurantees.tex
index 63a1c75f..b7279752 100644
--- a/Robust/Transactions/Notes/sysgurantees.tex
+++ b/Robust/Transactions/Notes/sysgurantees.tex
@@ -196,7 +196,7 @@ Def: We define a function $g(offsetstat_1, offsettat_2, ..., offsetstat_{n-1}, o
 \section{Implementation Overview}
 
 %proof: A write operation writes to the most recently commited offset (unless imposed otherwise by a seek or a prior read or a following read as shown above) of the file descriptor.  According to Def 2, it does not "use" any data. Since the write does not happen till commit instant, the offset chosen during the execution of transaction can be speculative, and the actual offset to be written to, is determined at the sommit instant, when the most recently commited offset is known. 
-Now we will describe the components of our system and demosntrate how the algorithm 
+Now we will describe the components of our system and demosntrate how the algorithm conforms to the function just described, and how all the rules principles are gurantedd.