Aar}  0  Pp @  0 ``P00 pHH $ @d HHHH̀̀̀ff@  d Footnote TableFootnote**.\t.\t/ - :;,.!?c;dTOCHeading1Heading2BainerHaring LangholtzLinuxPrenticeRochkind ShivaratriSinghal TanenbaumThuTuThUCDiskWoodhullafs eventcountersfromusergshandin homeworkshwnisunpkgpstousertxtusr   WEquationVariablesO;`<<=7=P=i=;B;D;F;HD^D`DaM M:M; ,66040: Title: All About Homework Assignments 81167: Title: All About UCDisk 8F,66040: Title: All About Homework Assignments8F81167: Title: All About UCDisk<$lastpagenum><$monthname> <$daynum>, <$year>"<$monthnum>/<$daynum>/<$shortyear>J<$hour>:<$minute00> <$ampm> on <$dayname>, <$monthname> <$daynum>, <$year>"<$monthnum>/<$daynum>/<$shortyear><$monthname> <$daynum>, <$year>"<$monthnum>/<$daynum>/<$shortyear> <$fullfilename> <$filename> <$paratext[Title]> <$paratext[Heading1]> <$curpagenum> <$marker1> <$marker2> (Continued)+ (Sheet <$tblsheetnum> of <$tblsheetcount>)Heading & Page <$paratext> on page<$pagenum>Pagepage<$pagenum>See Heading & Page%See <$paratext> on page<$pagenum>. Table All7Table<$paranumonly>, <$paratext>, on page<$pagenum>Table Number & Page'Table<$paranumonly> on page<$pagenum>Heading <$paratext>EHTML Headings++A33557WA<<>>@@AL;b;d;f;h;j;l;n;p;r;t;v;x;z;|;~;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;<<<<<< < <<<<<<<<<<< <"<$<&<(<*<,<.<0<2<4<6<8<:<<<>)O-+4.M)O.)O/L\ L])O0)O1-CcO2-O3-Lx O4-O5-O6-L)O7)O8O9)O:-O;1.O<+3.O?+2.O@+4.OA+5.OBOC)OF)O-O~-O-OO-O)O)Cd)Ce)Cg)Cj#Ck)ClCC@Co)Cp)Cq-C@Cs-Ct-Cu)C#C)DC}#KK)>)C~@C#C@AX+2.C)J)IK)Wdq5+d>< d;]d;L HmR;MHmRHRHRFootnote Hr@;NHr@HzHz Single LineH;O Footnote ;P  HD;Q HDHH Double LineH;R Double Line;S ;T H;U  Single Line;V HZ;W  TableFootnoted5p77 EGxR;XEGxREPwEPw TableFootnoted;^dEl d;_d1QRUX[^adgjmpsvy| %).1W/$Bm }d ;ad WaHTML Mapping Table }Hd ;cHd Wa }d ;ed Wa }d ;gd Wa } d ;i d Wa }H;kH! FrameMaker PA Source Item }H ;mH Wa HTML Item }H ;oH Wa }H;qH W aInclude Auto# } H;s H W a Comments }H;uH W a }HH;w HH W aElement }H;y#H W a New Topic? }H;{H Wa } H;} H Wa }H ; $H Wa P:Date Line }HH ;#%HH WaP }H ;$&H WaN }H ;%'H WaN } H ;&( H Wa }EH ;')EH Wa P:Reading }HEH ;(*HEH WaP }EH ;)+EH WaN }EH ;*,EH WaN } EH ;+- EH Wa }QH ;,.QH WaP:Title }HQH ;-/HQH WaH* }QH ;.0QH WaN }QH ;/1QH WaN } QH ;02 QH Wa }]H ;13]H WaP:Body }H]H ;24H]H W aP }]H ;35]H W!aN }]H ;46]H W"aN } ]H ;57 ]H W#a }iH(;68iH( W$a P:Numbered1 }HiH(;79HiH((%aLI &a Parent = OL Q'a Depth = 0 }iH(;8:iH( W(aN }iH(;9;iH( W)aY } iH(;:< iH( W*a }H ;;=H  W+a P:Heading1 }HH ;<>HH  W,aH* }H ;=?H  W-aN }H ;>@H  W.aN } H ;?A H  W/a }H(;@BH(  W0a P:Numbered }HH(;ACHH(( 1aP 2a Parent = OL Q3a Depth = 0 }H(;BDH(  W4aN }H(;CEH(  W5aY } H(;DF H(  W6a }H ;EGH  W7a P:CellBody }HH ;FHHH  W8aP }H ;GIH  W9aN }H ;HJH  W:aN } H ;IK H  W;a }H ;JLH  W<aP:CellHeading }HH ;KMHH  W=aP }H ;LNH  W>aN }H ;MOH  W?aN } H ;NP H  W@a }H ;OQH  WAa P:Footnote }HH ;PRHH  WBaP }H ;QSH  WCaN }H ;RTH  WDaN } H ;SU H  WEa }H(;TVH( WFa P:Bulleted }HH(;UWHH((GaLI Ha Parent = UL QIa Depth = 0 }H(;VXH( WJaN }H(;WYH( WKaN } H(;XZ H( WLa }H ;Y[H WMa P:Heading2 }HH ;Z\HH WNaH* }H ;[]H WOaN }H ;\^H WPaN } H ;]_ H WQa }H;^`HR! P:HeadingRuPAnIn }HH;_aHH WSaP }H<`bH WTaN }H<acH WUaN } H<bd H WVa }7H <ce7H WWa P:Indented }H7H < dfH7H WXaP }7H < eg7H WYaN }7H < fh7H WZaN } 7H <gi 7H W[a }CH<hjCH\! P:TableFootPAnote }HCH<ikHCH W]aP }CH<jlCH W^aN }CH<kmCH W_aN } CH<ln CH W`a }]H(<mo]H( Waa P:TableTitle }H]H(<npH]H((baLI ca Parent = OL Qda Depth = 0 }]H( H "W4a }©H <=?©H #W5a }H©H <>@H©H #W6a }©H <?A©H #W7a }©H <@B©H #W8a } ©H <AC ©H #W9a }»d <BF»d $W:aHTML Options Table }D»d <D»d $W;a }»d <»d $W<a }D <CGD %W=a }DH <FHDH %W>a }H <GIH %W?a }D <HJD &W@a Image Format }DH <IKDH &WAaIMAGGIF }H <JLH &WBa }D <KMD 'WCaBanners }DH <LNDH 'WDaN }H <MOH 'WEa }D<NPD(F! Banner ReferPA ence Frame }DH<OQDH (WGa }H<PH (WHa }D(<DSD((F)I! Copy Files  Imported by PA Rerefernce }DH(<DRTDH( F)WJa }H(<DSUH( F)WKa }DD <DTVDD F*WLa }DDH <DUWDDH F*WMa }DH <DVXDH F*WNa }Vd <DW[Vd F+WOaSystem Macros }?Vd <D?Vd F+WPa }Vd <DVd F+WQa }f? <DX\f? F,WRa Macro Name }?fH <D[]?fH F,WSa Replace With }fH <D\^fH F,WTa Comments }r? =D]_r? F-WUa StartOfDoc }?rH =D^`?rH F-WVa }rH =D_arH F-WWa }~? =D`b~? F.WXa EndOfDoc }?~H = Dac?~H F.WYa }~H = Dbd~H F.WZa }?= Dce?F/[! StartOfSubPADoc }?H=Ddf?H F/W\a }H=DegH F/W]a }?=Dfh?F0^! EndOfSubPADoc }?H=Dgi?H F0W_a }H=DhjH F0W`a }?=Dik?F1a! StartOfFirstPASubDoc }?H=Djl?H F1Wba }H=DkmH F1Wca }?=Dln?F2d! EndOfFirstPASubDoc }?H=!Dmo?H F2Wea }H=#DnpH F2Wfa }?=%Doq?F3g! StartOfLastPASubDoc }?H='Dpr?H F3Wha }H=)DqsH F3Wia } ?=+Drt ?F4j! EndOfLastPASubDoc }? H=-Dsu? H F4Wka } H=/Dtv H F4Wla }&? =1Duw&? F5Wma }?&H =3Dvx?&H F5Wna }&H =5Dwy&H F5Woa }8d =8Dx|8d F6WpaCross-Reference Macros }?8d =:D?8d F6Wqa }8d =<D8d F6Wra }H? =>Dy}H? F7Wsa Macro Name }?HH =@D|~?HH F7Wta Replace With }HH =BD}HH F7Wua Comments }T?=DD~T? F8Wva See Also }?TH=FD?THF8w! See Also: PA <$paratext> }TH=HDTH F8Wxa }n? =JDn? F9Wya }?nH =LD?nH F9Wza }nH =NDnH F9W{a }d =QD d F:WaGeneral Macros }?d =SD?d F:Wa }d =UDd F:Wa }d =WDd F:Wa }? =YD"? F;Wa Macro Name d= d= d l d= do  W$Bm }d = d  <W|aHeadings Table }Hd = Hd  <W}a }d = d  <W~a }H= H =!Paragraph ForPAmat }HH= HH  =WaHeading Level }H= H  =Wa Comments }H= H >W aTitle }HH= HH  >Wa }H= H  >Wa }KH = KH  ?Wa Heading1 }HKH = HKH  ?Wa }KH = KH  ?Wa }WH = WH  @Wa Heading2 }HWH = HWH  @W a }WH = WH  @W a }cH = cH  AW a }HcH = HcH  AW a }cH = cH  AW a HHˆ>=HHˆv @$,zThe handout  All About Homework Assignments   has more information on how to turn in homework and what I oexpect. Please submit your homework electronically as described in that handout; I will not accept handwritten 0tassignments. Also, please think your answers through before writing them down in final form. A request for a discuswsion should be treated as an essay question, with a main theme and arguments for and against the answer. It is fair to present the factors that affect your answer; it is  not  acceptable to begin by giving one answer in the introduction and sa different answer in the conclusion! (Yes, youll lose points.) Always show your work; if you simply write down a @tcorrect answer and do not show how you got that answer, you will not get any credit (even if your answer is right). 6#g`Grading I$y`025%Homework25%Project25%Midterm25%Final K#` Extra Credit E$ uSome of the assignments may include suggestions for extra credit. Extra credit scores are kept separate from regular zscores. If you end up on a borderline between two grades at the end of the course, extra credit will count in your favor. 0tHowever, failure to do extra credit will never count against you, since grades are assigned on the basis of regular xscores. You should do extra credit if you find it interesting and think it might teach you something. But it never pays @@to skimp on the regular assignment in order to do extra credit. b#`Academic Integrity c$`xPlease see the Winter 2000  Class Schedule and Room Directory  for a general discussion of this. In particular: d nAll work submitted for credit must be your own. You may discuss your assignments with classmates or me to get qideas or a critique of your ideas, but the ideas and words you submit must be your own. Unless explicitly stated U;@[otherwise in the assignment, collaboration is cheating and will be dealt with accordingly. e5`iYou must write up your own homework solutions and may neither read nor copy another students solutions. gC qA good analogy between appropriate discussion and inappropriate collaboration is the following: you and a fellow Onstudent work for competing software companies developing products to meet a given specification. You and your pUUtcompetitor might choose to discuss product specifications and general techniques employed in your products, but you wcertainly would not discuss or exchange proprietary information revealing details of your products. Ask the instructor @Ifor clarification  beforehand  if the above rules are not clear. HHˆ>?HHˆ79 ld>C99 }?H =[D #?H F;Wa Replace With }H =]D"$H F;W aHead }H =_D#%H F;W!a Comments }? =aD$&? FCW"a }?H =cD%'?H FCW#a }H =eD&(H FCW$a }H =gD')H FCW%a }d =jD(.d FDW&aCharacter Macros HHˆ;"HHˆ+W$e HHˆ;$3HHˆ**l}?d =lD?d FDW'a }d =nDd FDW(a }? =pD)/? FEW)a Macro Name }?H =rD.0?H FEW*a Replace With }H =tD/1H FEW+a Comments }? =vD0B? FFW,a HUV ;.HUV 3We HUV ;05+HUV 22l H$ ;1H$ 5We H$ ;33H$ 44l HHˆ;4HHˆ…((7 `General Information #,` Instructor $ OMatt Bishop Office hours : MWF 11:15 AM 12:15 PM, or by appointment 2%IMOffice : 3059 Engineering Unit II Email : bishop@cs.ucdavis.edu @TPhone : (530) 752-8060 WWW : http://seclab.cs.ucdavis.edu/~bishop  r&c Note : If you send me email about the class, please make the first words of the subject be  ECS 251  to help us see it $o@ quickly! 3#`!Lectures and Discussion Sections 3$`OSection 1: TuTh 12:10PM1:30PM in 1062 Bainer; there is no discussion section. 5#`Course Outline 7$Ū sA survey of formal models for the study of operating systems. Modeling of parallel processes and their synchroniza0Ѫytion in terms of partial orderings and procedure relations. Deterministic and probabilistic models for the evaluation of @system performance. 7#` Course Goals 8$`Some goals I hope you achieve: 9`Zunderstand how process synchronization works, and some of the mechanisms to achieve this; <`,learn about the various models of deadlock; ;`Alearn about distributed systems and the algorithms they use; and != llearn the very basics of computer security and cryptography (enough to interest you in ECS 222 and ECS 253, @for example...). `#]`Course Prerequisites a$o`YI expect you to be comfortable with the following concepts and able to do the following: l{`;Operating systems, as covered in ECS 150 or ECS 151AB; and ;`?Basic probability theory, as covered in Math 131 or Stat 131A. >#`Text ?$ tMukesh Singhal and Niranjan G. Shivaratri,  Advanced Concepts in Operating Systems , McGraw-Hill, Inc., New @York, NY (1994). B#`)Course Web Page, Handouts, and Newsgroup C$骖 {The web page  http://ecs251-001.ucdavis.edu  contains links to course handouts. Information about this class, home0owork assignments, office hours, and so forth, will be posted to the web page. Announcements, information about zassignments, and other important messages will be posted to the  ucd.class.ecs251  newsgroup. Read this newsgroup vdaily, especially near the time assignments are due. You are responsible for everything posted. This newsgroup is not @gfor discussion about the class, for but information from the instructor or teaching assistants to you. E' ~If you want to post things about the class, please use the discussion newsgroup  ucd.class.ecs251.d.  Discussing some3@'thing in this group is perfectly fair! G#L`Homework Assignments H$^ nThere will be several homework assignments. The due date will be on each assignment. Because we must cover so pjxmuch material, it is imperative you keep up with the class and labs. As this is a graduate class, I expect that each of qyou can keep charge of your own time, and get assignments in on time. So I will not penalize you for late assign@vments,  but I reserve the right to change this policy if the class abuses it!  So please get work in on time. HHˆ;6HHˆ 66 l HHˆ>D!HHˆƒ((9- ` Syllabus 2,`Week #1. January 57, 2000 D% 'Topics : Introduction and overview  G@3Reading :  Singhal and Shivaratri,  1 FZ`Week #2. January 1014, 2000 S%j %Topics : Process synchronization  v9Reading :  Singhal and Shivaratri,  2, 4.7 !u@*project discussion will be this week  P`Week #3. January 1721, 2000 R% Topics : Deadlock  @3Reading :  Singhal and Shivaratri,  3 W`Week #4. January 2428, 2000 Z%Ԫ 0Topics : Foundations of distributed systems  ઢ@=Reading :  Singhal and Shivaratri,  4.14.7, 5 X`%Week #5. January 31February 4, 2000 h% 5Topics : Distributed Mutual Exclusion Algorithms  @3Reading :  Singhal and Shivaratri,  6 o"`&Week #6. February 7February 11, 2000 p%2 ,Topics : Distributed Deadlock Detection  >8Reading :  Singhal and Shivaratri,  7  !1UI@midterm will be this week  u]`'Week #7. February 14February 18, 2000 v%m -Topics : Distributed Agreement Protocols  y@3Reading :  Singhal and Shivaratri,  8 |`'Week #8. February 21February 25, 2000 % 3Topics :  to be determined (presentations)  $Reading :  to be determined !@(project presentations will be this week N`#Week #9. February 28March 3, 2000 %ת -Topics : Protection in Operating Systems  㪖@4Reading :  Singhal and Shivaratri,  14 J`Week #10. March 610, 2000 Q% Topics : Cryptography  @4Reading :  Singhal and Shivaratri,  15 #+` Lectures a$= uBecause I teach to the students, and not to the syllabus, these dates and topics are tentative and subject to change I{without warning. In particular, if I dont discuss something youre interested in, ask about it! I may very well add it or ¶@(modify what Im covering to include it. #n`"Tentative Nature of This Syllabus W0$€ This syllabus is  tentative , and I reserve the right to change it as seems appropriate. So, I really will welcome any feedHHˆ>F!HHˆ H88 ld>JHH d;;<@H$ ;<;>H$ == l H$ ;=;H$ <Wl7January 6, 2000ECS 251 Winter 2000Page 1  HUV ;>;<@HUV ?? l HUV ;?;HUV >Wl@Last modified at  4:14 pm on Tuesday, January 4, 2000  HHˆ;@;>HHˆAA l HHˆ;A;HHˆ@W$` }?H =xD1C?H FFW-a }H =zDBH FFW.a d=~EEd=DdFF l d=DdRCERUX[^adgjmpsvy| %).1 HHˆ>K:HHˆHW0$@Fback, or expressions of interest, in other areas (or in these areas). HHˆ>M:HHˆ9KGG ld>QKK HHˆ>RIHHˆ~++K1 `Project :#,` Introduction O$ uThe goal of this project is to have you study different aspects of operating system design and algorithms, and apply Irwhat you learn to the design of a new operating system. Im also going to try to give you a flavor for real-world W@Pdesign considerations, in a way that I hope you will find novel and intriguing. ^#n` Background _$ kWe work for the Cow Computer Company, which develops educational systems for various universities. We have pbeen approached to bid on a contract by a major but unnamed university in a small town 15 minutes west of Sacra0qmento. To make our bid credible, we have to present a design of the major components of an operating system, and @Thow they will work together. They have given us the goals of the system, which are: f`aThe system must be a distributed system capable of sharing files and other resources seamlessly; m`nThe system must scale easily; that is, it should run correctly and quickly whether there are 3 nodes or 3000; !n pThe system must protect the privacy of directories on a per-user basis (for example, if a team of 6 students is @Zworking on a project, the project directory should allow access to only those six users); !q nThe system must allow test systems or experimental systems to run under it, without endangering the nodes run@ning production systems. s yOur goal is to come up with a design to meet these needs. (If these sound nebulous, they are; the people soliciting bids @Awere not too helpful. We can refine these goals as we go along.) t#`Components of the System w$1 xOur approach will be to divide the class into teams. We will look at different aspects of the operating system first in =@Oisolation, and then combine what we have. Some aspects we need to look at are: xL`Distributed file systems  `.Distributed process execution (including RPC) `Distributed memory z`1Distributed location and management of resources {`8Process scheduling, including locating appropriate CPUs }`Security and protection ~`User interface ` Networking ` Performance `Naming `Structuring of the System `/and so forth. So, here is how we will proceed. # `7Task #1: Split up into teams and tackle the components $ sSoon after the course begins, we will spend some time discussing what components we should split the operating sys'@htem into components, and break up into teams. Each team will be responsible for preparing a paper that: 1V lanalyzes and refines any requirements related to the component (this may simply be stating them and arguing @%why those requirements were chosen); `@surveys different approaches to the component used in the past; `Xanalyzes the way those approaches might be expected to work in the system under design; `Hdiscusses any interfaces that other components need to be aware of; and a  mrecommends a choice of algorithm, design, or some combination as appropriate. It is fair to specify multiple ochoices, one per requirement, if you have a set of requirements that someone can choose from. For example, If HHˆ>TIHHˆHNJJ ld>XNN HHˆ>YLHHˆ  N $@[you want to meet requirement A, use this; if you want to meet requirement B, choose that.   sEach design must be detailed enough so that, if someone were handed the resulting paper and asked to implement it, ~that person could do so. But you need not implement it. You  may  need to simulate several possibilities to see under UR@4what conditions they are effective, of course.   #E`Task #2: Integrate the results  $W uIn the later part of the course, each group will give a presentation of what they have done, and why. The teams will cxthen integrate what they have done into a proposed distributed operating system. Ill make a short presentation for the 0ytoverall goals and design, and each group will prepare a 10-15 minute presentation on what they did and why. We will @3give this to ourselves the last week of the class. #` A Final Note $ wIf parts of this project sound a bit vague, thats because they are. I expect each group to refine the requirements as sthey see fit, and (when possible) to point out what requirements different designs meet, or to suggest a design as PUJ@iappropriate for a particular goal. I want you to be creative here! So have fun and use your imagination HHˆ>[LHHˆKQMM ld>_QQ HHˆ>`OHHˆ{--QY h$ All About Homework Assignments k$ qThis handout describes some general thoughts and techniques for doing homework, as well as what is required, how @Pto submit it, how late homeworks are handled, and other administrative matters. y#O`Turning In Homework $a qAll homework is due at 11:59PM on the due date, unless noted otherwise on the assignment. (This way, you have no mtincentive to skip the class while finishing your homework at the last minute!) These will be graded and returned to @Vyou as quickly as possible; Ill try for three class periods, but cant guarantee it.  uYou must turn in either an ASCII or a PostScript version of your answers (you can use any text processor you like to generate these). If you submit PostScript, please be sure the file will print on our department printers (use  ghostscript  0UOor  gs  to check this; if they display it properly, it should be okay). If your file is a postscript file, choose a name that @Rends in .ps; if it is an ASCII file, please choose a name that ends in .txt. ,zTurn in your written exercises electronically to UCDisk. To do this, get a credential for UCDisk (see  All About !Ū UCDisk ), and put your homework in a subdirectory of your UCDisk home directory called ecs251/hand-in/hw n  2$where  n  is the homework number. Be sure the account bishop can read that directory and the files in it! I will copy the whomework out, and send you a letter saying what we copied and the date of last modification of the file. (This will be rused as the time of submission.) At a later time, I will email your grade and any comments to your UC Davis login @"( not  your CSIF login!). # `Doing Written Exercises  $ {When you are asked to analyze something, or explain something, please be complete, and  show your work  (including *pany commands you give, and their output, to show how you did the problem); otherwise, even if you get the right 0U1answer, you will get  ZERO  points. Think your answer through and do a rough draft. Write clearly and cogently. If the vquestion asks for an opinion, state your opinion clearly, justify it, and dont ramble. Answers which start, My opintion is yes and conclude with on the other hand it could equally well be no wont get much credit. Similarly, tif you are asked to prove something, you must give a mathematical proof (formal or informal). Proof by similarity y(it works in this case, and in another case, so it must be true for all cases!), proof by assertion (it sounds right, @xtherefore it is right!), or proof by citation (our professor said it in class, so its right!) are all unacceptable. !#`Asking For Help $$ tI do not mind being asked for help; indeed, I welcome it because it helps me know what you are finding difficult or qconfusing, and sometimes a few words about the problem in class will clarify the assignment immensely. Your queṡ@utions may also point out ambiguities that I didnt think of, so the more questions you ask, the better for everyone! <ê I  do  mind being asked for help before you have tried to think the problem through; the classic objectionable question Ϫn(this really happened) occurred on a programming assignment in which the class was given a buggy program. The 0}rassignment said the program did not work, and the homework was to debug it and make it work. Within 10 minutes of wthe end of the class during which the assignment was given out, the instructor got this request for help: The program @!doesnt run. What do I do now? %`sSo, before asking for help (except for questions about what the problem is asking), please be sure that you have: &`Lspent a significant amount of time thinking about how to solve the problem; (X oread all relevant handouts, sections of the textbook, and news articles (because your question may be answered +@ there); and ):`:tried everything you could think of to solve the problem. *H rWhen you come to me, or send me a note, asking for help, please describe whatever you have done to solve the probTulem, because the first question I will ask you is What have you tried to solve the problem? This isnt because I ppvthink youre wasting our time; its because understanding how you have tried to solve the problem will help me figure vout exactly what your difficulty is and what I can do to help you. Remember, I will do everything I can to avoid solv@ling the problem for you; when I give you help, my goal is to help  you  solve the problem yourself. HHˆ>bOHHˆNTPP ldDOTT HHˆDPRHHˆBT"#` Dont Delay! '$ rI must emphasize the importance of taking time to think through, outline, and draft your answer, thoroughly. More wpoints are lost through unclear organization, or superficial answers, than anything else. So do think both your answer 0yand your  expression  of the answer through, and as always try to find the simplest way to solve the problem @8(within the limits given in the assignment, of course)! #L wDo not leave assignments for the last minute. The assignments are non-trivial and will require significant time before Xsyou write your answers for submission. When I decide on the due dates, I assume you will spend significant amounts 0Dvof time solving (at least some) of the problems. If you choose not to do this, you will have difficulty finishing the @assignments on time. 2#`Grades ,$ wYour grades will be mailed to your UC Davis account ( not  your CSIF account!) when the homework assignment is vgraded. Please be sure that account will forward mail to wherever you want to see the grade. If the letter bounces, I 0 UFwill  not  try to figure out why. (With 50 people at least! in this class, and 130 in my other class, its simply not @,practical; the gradermewill be too busy.) +#`Late Homework 8$檞 zInitially, Ill assume that if you dont get a homework in on time, that you have a good reason, and that you will get it wto me as quickly as possible. If people abuse this policy (say, homework from a majority of the class starts coming in UV@^a week or two late), I reserve the right to impose penalties. But lets start out this way... 9#`Grade Appeals :$' {If you feel that there is an error in grading, please come see me Ill look over it (and possibly talk with you about it). 3rHowever, dont dally; any such request must be made within one week of when the grades were made available. After P_@!that, I won't change your grade. HHˆDRRHHˆQWSS ldOWW HHˆOUHHˆW 4 hAll About UCDisk T$ }This term, we will be experimenting with the Universitys shared file system, called  UCDisk . All homework is to be @Usubmitted through this shared file system. This is a brief introduction to using it. L#O`What Is UCDisk? V$a wUCDisk is a large shared disk facility built on AFS (a descendent of the Andrew File System). It provides fine-grained mwaccess control, which will play a part in how you will use UCDisk. It also is accessible from a large number of places 0xon campus, including from the  isun  systems and most Windows labs. If you have a home computer running Windows r95 or 98, and you connect over the Internet (either from another ISP or through the campus modem bank using PPP), @6you can mount the file system onto your home machine. [ uUnfortunately, you cannot yet connect from the CSIF. If this experiment works out well, we will try to make it availrable next term. But currently AFS software is available to the University only for SGI systems (although a native @ Linux client is being written). \#`Accessing UCDisk ]$⪠ qTo access UCDisk, you first need a campuswide login (called your UCD login) and a password. The authentication tprotocol Kerberos is used to authenticate you, which in turn controls what you can access. This means your password 0is  never  sent over the network (in the clear or enciphered). If you do not have a UCD login,  telnet  to the host @bmothra.ucdavis.edu, log in as  services  (no password needed) and choose N from the menu. i mYour UCDisk home directory has your UCD login as its name. For example, my UCDisk home directory is called  pbishop. DCAS has created UCDisk home directories for everyone in the class who has a UCD login. If you do not Ѫ@nhave a UCD login, please get one and email me when it is selected, and Ill ask DCAS to make you a directory. j: Once you have a directory, you can access it through Windows (any of 95, 98, or NT will work), the  isun s, or the ECE FoUNIX computer systems. (Sorry, you cant do it through a Mac. The Mac doesnt handle the right versions of Ker0vberos.) The web page http://ucdisk.ucdavis.edu describes how to do this from all systems; go to the Getting Started plink. Briefly, from a UNIX system, if your UCD login is  ucdlogin , your UCDisk home directory is /afs/zdcas.ucdavis.edu/pilot/users/ ucdlogin . From a Windows system, perform the network mounting as described on the rweb page, and your home directory will be represented by a network drive (the exact letter depends on your system @ setup).  A#`UCDisk Web Page U$ rThis is an abbreviated version of the information available from http://ucdisk.ucdavis.edu. I recommend you check P@(that web page out for more information. HHˆOUHHˆTVV ldLeftd;Rightd ReferenceddHTMLdDHTMLd Headingsd d !d :d Id Ld Od RdU@@ XMapping Table Title. @@ XBody. f@T Y#Heading1Body. @@ XFooter. f@T X TableTitleT:Table : . f@ Y $2Body.  f@@Y TitleBody.  f@@YTitleBody. f@T XHeading3Body. f@T XHeading3Body. @@ XHeader Double Line. f@ X CellFooting. f@ X CellHeading. f@ X CellBody. @@ XMapping Table Cell. @@1Mapping Table Cell. @@ 1Mapping Table Cell. @@ XMapping Table Cell. f@E Y $ Numbered1.\tNumbered.  f@T Y#Heading1Body. f@ X BodySpaced.  f@T YHeading1Body. mf@ Xl. DateProject. @@ XHeader Double Line. f@ Y $Body. f@ Y $ Numbered.\t. f@ X NumberedSpaced.\t. f@ Y $ Bulleted\t. f@$X.Line Single Line. f@ XCellBody. f@ X CellHeading.  f@T XHeading2Body. f@T X HeadingRunInBody. f@ X Indented. f@ X TableFootnote. f@T X TableTitleT:Table : . f@ X Footnote. f@ Y $$?hBody. f@ Y $Body. f@ Y Body. f@E Y  Numbered1.\tNumbered. f@ Y  Numbered.\t. f@ Y ...Date. f@ Y .Reading. f@ Y  Bulleted\t. @@ Y $ H l      D h  ManHeading. @@ Y  $ H l      D h  ManBody. @@ Y ManHeading2. $$@@    $ H l      D h  ManCode.  X X 1 X ڝXXEmphasis  XItalicXEquationVariables ڝX 1  BoldItalic XItalic XBold X1 X XItalicY Y  Y Y  Y   Y  BoldItalic YZZThinMediumDoubleThick@ Very Thin HHHHHFormat AH Mapping Table HHHHHFormat BH))) Mapping Tableh*|#HHHHHf$*DHH+5?HH&69?HH :C?HHH DF?HH*6 ? @ h( A B C D E h  F G H I J h  K L M N O h  P Q R S T h( UVWXYh Z[\]^h_`abc7h defghChijklm]h(nopqrh stuvwh xyz{|h(}~h h    h  h h h)h  !"#$5h%&'()Oh  *+,-.[h!/ 0 1 2 3 uh "4!5!6!7!8!h!#9":";"<"="©h ">#?#@#A#B#»d %C$D$E$ $&F%G%H% %'I&J&K& &(L'M'N'')O(P(Q(((*FR)S)T)D )FU*V*W*Vd ,FX+Y+Z+f +-F[,\,],r ,.F^-_-`-~ -/Fa.b.c..0Fd/e/f//1Fg0h0i002Fj1k1l113Fm2n2o224Fp3q3r3 35Fs4t4u4& 4Fv5w5x58d 7Fy6z6{6H 68F|7}7~7T79F888n 8F999d ;F:::: :CF ;";#;$;d =  <<<<> ====? >>>K >@ ???W ?A @@@c @ AAA ;F%C&C'C(Cd EF)D,D-D DFF.E/E0E EF1FBFCFComment ;C ;G D_M9d BlackT!WhiteddARedddGreendd BluedCyandMagentad YellowHeader/Footer $1Header/Footer $1Header/Footer $2Header/Footer $2IndexIndexCommentCommentSubjectSubjectAuthorAuthorGlossaryGlossaryEquationEquation Hypertext Hypertext  Cross-Ref Cross-Ref Conditional TextConditional TextPositionFMPrivatePositionFMPrivateRangeEndFMPrivateRangeEndFMPrivate HTML Macro HTML Macro M.Times.P Times-Roman FrameRomanM.Times New Roman.BTimesNewRomanPS-BoldMT FrameRoman M.Times.B Times-Bold FrameRomanM.Times New Roman.PTimesNewRomanPSMT FrameRoman M.Helvetica.BHelvetica-Bold FrameRoman M.Courier.PCourier FrameRoman M.Times.I Times-Italic FrameRomanM.Helvetica.BIHelvetica-BoldOblique FrameRomanM.Times New Roman.BITimesNewRomanPS-BoldItalicMT FrameRomanM.Times New Roman.ITimesNewRomanPS-ItalicMT FrameRomanfCourier0 HelveticaWTimesXTimes New Roman"Regular$Roman MediumBoldRegular ObliqueItalicjpT:Y tiӊپ5;be{'% ,*5\>flAl Mo-Y N1K $ծ'K#/ق-)OEYZ"+DI::= Q&thKr~^T4uL_9B`)꩜6tcmSA̳* =;?jZC͢(-r]}M9L eؠ]