Aarc  0 @P      0`@p0HH $ @d HHHH̀̀̀ff@  d Footnote TableFootnote**.\t.\t/ - :;,.!?c;0 dTOCHeading1Heading2Haring LangholtzPrenticeRochkind TanenbaumThuTuThWoodhull eventcountersfromusergshandin homeworkspkgpstousertxtusr   WEquationVariablesR;`<<=7=P=i=;B;D;F;HD^D`DaM_DjDlGgGhGjM M:M; ,66040: Title: All About Homework Assignments .57517: Title: All About Laboratory Assignments 81167: Title: All About UCDisk 8q,66040: Title: All About Homework Assignments8q.57517: Title: All About Laboratory Assignments8q,66040: Title: All About Homework Assignments8q81167: 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<<>>@@An;b;d;f;h;j;l;n;p;r;t;v;x;z;|;~;;;;;;;;;;;;;;;;;;;;;OjOl;;;;;;;;;;OO;;;;;;;;;;;;;;;;;;;;OO;;;;;;;;;;<<<<<< < <<<<<<<<P&P(< <"<$<&<(<*<,<.<0<2<4<6<8<:<<PZP\<@HH  W,eH* }H ;=?H  W-eN }H ;>@H  W.eN } H ;?A H  W/a }H(;@BH(  W0e P:Numbered }HH(;ACHH(( 3eP 1e Parent = OL Q2e Depth = 0 }H(;BDH(  W4eN }H(;CEH(  W5eY } H(;DF H(  W6a }H ;EGH  W7e P:CellBody }HH ;FHHH  W8eP }H ;GIH  W9eN }H ;HJH  W:eN } H ;IK H  W;a }H ;JLH  W<eP:CellHeading }HH ;KMHH  W=eP }H ;LNH  W>eN }H ;MOH  W?eN } H ;NP H  W@a }H ;OQH  WAe P:Footnote }HH ;PRHH  WBeP }H ;QSH  WCeN }H ;RTH  WDeN } H ;SU H  WEa }H(;TVH( WFe P:Bulleted }HH(;UWHH((IeLI Ge Parent = UL QHe Depth = 0 }H(;VXH( WJeN }H(;WYH( WKeN } H(;XZ H( WLa }H ;Y[H WMe P:Heading2 }HH ;Z\HH WNeH* }H ;[]H WOeN }H ;\^H WPeN } H ;]_ H WQa }H;^`HR% P:HeadingRuPEnIn }HH;_aHH WSeP }H<`bH WTeN }H<acH WUeN } H<bd H WVa }7H <ce7H WWe P:Indented }H7H < dfH7H WXeP }7H < eg7H WYeN }7H < fh7H WZeN } 7H <gi 7H W[a }CH<hjCH\% P:TableFootPEnote }HCH<ikHCH W]eP }CH<jlCH W^eN }CH<kmCH W_eN } CH<ln CH W`a }]H(<mo]H( Wae P:TableTitle }H]H(<npH]H((deLI be Parent = OL Qce Depth = 0 }]H( H "W4a }©H <=?©H #W5e P:Heading3 }H©H <>@H©H #W6eH* }©H <?A©H #W7eN }©H <@B©H #W8eN } ©H <A ©H #W9a }»d <DsF»d F$W:aHTML Options Table }D»d <DD»d F$W;a }»d <D»d F$W<a }D <DCGD F%W=eControl }DH <DFHDH F%W>eValue }H <DGIH F%W?e Comments }D6<DHJD6 F&W@e Image Format }DH6<DIKDH66F&A% 0001IMAGGIF p MACP0001GIEF }H6<DJLH6 F&WBa }D <DKMD F'WCeBanners }DH <DLNDH F'WDeN }H <DMOH F'WEa }D<DNPDF(F% Banner ReferPE ence Frame }DH<DOQDH F(WGe }H<DPRH F(WHa }D(<DQSD((F)I$% Copy Files  Imported by PE Rerefernce }DH(<DRTDH( F)WJe }H(<DSUH( F)WKa }DD(<DTVDD((F*L% Copy Files  Imported by PE Reference }DDH(<DUWDDH( F*WMeN }DH(<DVDH( F*WNa }Vd <D[Vd F+WOaSystem Macros }?Vd <D?Vd F+WPa }Vd <DVd F+WQa }f? <DX\f? F,WRe Macro Name }?fH <D[?fH F,WSe Replace With }fH <D^fH F,WTe Comments }r? =D]_r? F-WUe StartOfDoc }?rH =D^?rH F-WVa }rH =DarH F-WWa }~? =D`b~? F.WXe EndOfDoc }?~H = Dak?~H F.WYa }~H = Dkd~H F.WZa }?= Dce?F/[% StartOfSubPEDoc }?H=Ddl?H F/W\a }H=DlgH F/W]a }?=Dfh?F0^% EndOfSubPEDoc }?H=Dgm?H F0W_a }H=DmjH F0W`a }?=Dik?F1a% StartOfFirstPESubDoc }?H=Djn?H F1Wba }H=DnmH F1Wca }?=Dln?F2d% EndOfFirstPESubDoc }?H=!Dmo?H F2Wea }H=#DopH F2Wfa }?=%Doq?F3g% StartOfLastPESubDoc }?H='Dpp?H F3Wha }H=)DpsH F3Wia } ?=+Drt ?F4j% EndOfLastPESubDoc }? H=-Dsq? H F4Wka } H=/Dqy H F4Wla }H Q6DxwH F5Gme C:Emphasis }H Q8DvxH F5GneEM }H Q:DwrH F5GoeN },d =8Du|,d F6WpaCross-Reference Macros }?,d =:D?,d F6Wqa },d =<D,d F6Wra }<? =>Dy}<? F7Wse Macro Name }?<H =@D|~?<H F7Wte Replace With }<H =BD}<H F7Wue Comments }H?=DD~H? F8Wve See Also }?HH=FD?HHF8w% See Also: PE <$paratext> }HH=HDHH F8Wxa }Vd NDVd F+Wye }fH ND\]fH F,WzeHead }rH ND_`rH F-W{e }hd =QD hd F:WaGeneral Macros }?hd =SD?hd F:Wa }hd =UDhd F:Wa }hd =WDhd F:Wa }x? =YD"x? F;We Macro Name d= d= d l d= du  W$Bm }d = d  <W|aHeadings Table }Hd = Hd  <W}a }d = d  <W~a }H= H  =WeHeading Level }HH= HH =%Paragraph ForPEmat }H= H  =We Comments }H= H >W e2 }HH= HH  >We Heading1 }H= H  >Wa }KH = KH  ?We3 }HKH = HKH  ?We Heading2 }KH = KH  ?Wa }WH = WH  @We4 }HWH = HWH  @W e Heading3 }WH = WH  @W a }cH= cH  AW e1 }HcH= HcH AW  eTitle }cH= cH  AW a HHˆ>=HHˆ‚,, B#`)Course Web Page, Handouts, and Newsgroup C$ {The web page  http://ecs150.ucdavis.edu  contains links to course handouts. Information about this class, homework 0qassignments, office hours, and so forth, will be posted to the web page. Announcements, information about assign{ments, and other important messages will be posted to the  ucd.class.ecs150  newsgroup. Read this newsgroup daily, sespecially near the time assignments are due. You are responsible for everything posted. This newsgroup is not for @cdiscussion about the class, for but information from the instructor or teaching assistants to you. EW ~If you want to post things about the class, please use the discussion newsgroup  ucd.class.ecs150.d.  Discussing somec@'thing in this group is perfectly fair! G#|`Homework Assignments H$ nThere will be several homework assignments. The due date will be on each assignment. Because we must cover so @smuch material, it is imperative you keep up with the class and labs.  We will not accept any late assignments. I({The handout  All About Homework Assignments   has more information on how to turn in homework and what we 0pexpect. Please submit your homework electronically as described in that handout; we will not accept handwritten tassignments. 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). K# `Laboratory Assignments 6$(There will be several laboratory assignments. The handout  All About Laboratory Assignments  has information on '@Yhow to turn in the lab assignments, how to get them graded, and what we expect from you. M#@`Grading N$R`-20%Homework30%Labs25%Midterm25%Final #k` Extra Credit E$} vSome of the assignments may include suggestions for extra credit. Extra credit scores are kept separate from regular 0tscores. If you end up on a borderline between two grades at the end of the course, extra credit will count in your xfavor. However, failure to do extra credit will never count against you, since grades are assigned on the basis of regzular scores. You should do extra credit if you find it interesting and think it might teach you something. But it never @Epays 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窑 lAll work submitted for credit must be your own. You may discuss your assignments with classmates or the TAs 0lor me to get ideas or a critique of your ideas, but the ideas and words you submit must be your own. Unless @mexplicitly stated otherwise in the assignment, collaboration is cheating and will be dealt with accordingly. e`iYou must write up your own homework solutions and may neither read nor copy another students solutions. A mYou and your lab partners (if any) must create and type in your own code for laboratory assignments and docu0)xment it yourself. You are free to seek help while debugging code once it is written.  However , the graders are nencouraged to ask technical questions of any member of the team. Passing grades for each assignment are based @nin part on each partner giving answers that demonstrate an understanding of the code and principles involved. gO qA good analogy between appropriate discussion and inappropriate collaboration is the following: you and a fellow p[nstudent work for competing software companies developing products to meet a given specification. You and your tcompetitor 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 }?xH =[D #?xH F;We Replace With }xH =]D"$xH F;W eHead }xH =_D#%xH F;W!e 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)e Character }?H =rD.0?H FEW*e Replace With }H =tD/1H FEW+e Comments }? =vD0B? FFW,e HUV ;.HUV 3We HUV ;05+HUV 22l H$ ;1H$ 5We H$ ;33H$ 44l HHˆ;4HHˆm&&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  n#n`Teaching Assistants s$`TPatrick LeBlanc (leblanc@cs.ucdavis.edu) and Tom Walcott (walcott@cs.ucdavis.edu). @#`Contacting Us q }You can contact me, or the TAs, by sending email to  cs150@csif.cs.ucdavis.edu . Please dont send us email individu0yally. That way, any of three people will be able to see it, so you should get a quicker answer. If we think the question @`is of general interest, we will ask you to post it to the news group and we will respond there. r&Ѫ`hNote : Please make the first words of the subject be  ECS 150  to help us see it quickly! 3#`!Lectures and Discussion Sections 3$ WSection 1: TuTh 1:40PM3:00PM in 223 Olson; discussion is F 4:10PM5:00PM in 205 Olson @XSection 2: MWF 10:00AM10:50AM in 1130 Hart; discussion is F 5:10PM6:00PM in 205 Olson 5#!`Course Outline 7$3 mBasic concepts of operating systems and system programming. Processes and interprocess communication/synchro0?rnization. Virtual memory, program loading and linking. File and I/O subsystems. Utility programs. Study of a real @operating system. 7#d` Course Goals 8$v` Some goals we hope you achieve: 19 nunderstand the basic concepts of operating systems, including file and process management, process scheduling @_and synchronization, memory management, deadlock, and protection in a multiprogramming system; <`Qlearn about the practical aspects of operating system design and implementation; ;`>apply these concepts to a small operating system (MINIX 2.0); :`:understand what system calls are and how to use them; and =`(gain experience in systems programming. `#`Course Prerequisites a$骖`ZWe expect you to be comfortable with the following concepts and able to do the following: l`5Assembly language programming, as covered in ECS 50; `GData structures, such as queues, stacks, lists, as covered in ECS 110; z`jBasics of computer architecture, especially interrupts and memory management, as covered in ECS 154A; and ;`HThe C programming language (you will need to use C,  not  C++). w' The official prerequisites for this class are ECS 40 and  either  ECS 154A  or  EEC 70. If you do not have the prerequi3@tsites for this course,  you will be dropped from it to make room for others who do have the prerequisites . >#L`Text ?$^ tAndrew S. Tanenbaum and Albert S. Woodhull,  Operating Systems: Design and Implementation , Second Edition, Pj@:Prentice-Hall, Inc., Upper Saddle River, NJ 07458 (1997). HHˆ;6HHˆ 66 l HHˆ>D!HHˆu**9- ` Syllabus 2,`Week #1. January 57, 2000 D% gTopics : Introduction, history and organization of operating systems; the kernel; virtual machines  G0Reading :  Tanenbaum  1.11.5  %@@Discussion Section : System calls for files and directories Ff`Week #2. January 1014, 2000 S%v oTopics : Processes, concurrency; the critical section problem; software and hardware solutions; semaphores  9Reading :  Tanenbaum  2.2.22.2.5, 2.3  %@CDiscussion Section : System calls for protection and processes P`Week #3. January 1721, 2000 R% ITopics : Monitors, eventcounters and sequencers, IPC constructs   ;Reading :  Tanenbaum  2.2.62.2.7, 2.2.9  %@XDiscussion Section : System calls for interprocess communication, including signals W`Week #4. January 2428, 2000 Z%쪡 %Topics : Process Scheduling   0Reading :  Tanenbaum  2.42.6  %@1Discussion Section : MINIX process structure X`%Week #5. January 31February 4, 2000 h%' #Topics : Input and Output   3JReading :  Tanenbaum  3.13.2, 3.4, 3.5, 3.6.1, 3.73.9  %@,Discussion Section : Review for midterm oR`&Week #6. February 7February 11, 2000 p%b $Topics : Memory management   n5Reading :  Tanenbaum  4.14.3, 4.6  %(Discussion Section : MINIX I/O  !@Midterm exam is this week  u`'Week #7. February 14February 18, 2000 v% )Topics : More memory management   9Reading :  Tanenbaum  4.44.5, 4.74.8  %@1Discussion Section : MINIX memory management |`'Week #8. February 21February 25, 2000 }%䪔 >Topics : File system organization and implementation   0Reading :  Tanenbaum  5.15.3  %@+Discussion Section : MINIX file system t`#Week #9. February 28March 3, 2000 % 8Topics : Deadlock models, principles, practise   +,Reading :  Tanenbaum  3.3  %@=Discussion Section : Some Example Problems and Solutions JJ`Week #10. March 610, 2000 Q%Z 0Topics : Security and protection mechanisms  f'Reading :  Tanenbaum  5.5 B%@*Discussion Section : Review for final HHˆ>F!HHˆ H88 ld>JHH d;;<@H$ ;<;>H$ == l H$ ;=;H$ <Wl7January 5, 2000ECS 150 Winter 2000Page 9  HUV ;>;<@HUV ?? l HUV ;?;HUV >Wl@Last modified at  10:10 pm on Monday, January 3, 2000  HHˆ;@;>HHˆAA l HHˆ;A;HHˆ@W$` }?H =xD1C?H FFW-e¢ }H =zDBgH FFW.a d=~EEd=DdFF l d=Dd$tZE$tvCFILORU X[^adgjmpsy| %).1gda^[X HHˆ>K:HHˆH#` Lectures a$ uBecause I teach to the students, and not to the syllabus, these dates and topics are tentative and subject to change 0{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. 0#J`Discussion Sections 1$\ pWe expect the discussion sections to amplify the material covered in class by relating it to MINIX and the UNIX 0hvoperating systems. In the lectures, I will discuss both MINIX and UNIX (as well as other systems), but Ill cover the tapplication of the principles to those systems. The teaching assistants will go into much more depth about MINIX in @the discussion sections. _' {However , the above discussion section topics are tentative and subject to change as we see fit. Regardless of what is $@9listed, all discussion sections have a few ground rules: @ pIf you dont understand something in lecture, or are having problems with the assignments, please ask the teach0qing assistant. The primary goal of a discussion section is to discuss points that are confusing you, and the TAs @[have standing instructions to clear up any confusion even if some material is not covered. AЪ nYou are responsible for material covered in discussion section. That material may be on homework assignments, Pܪ@lab assignments, and exams. HHˆ>M:HHˆ9KGG ld>QKK HHˆ>RIHHˆ‡..KY 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 0mtincentive to skip the class while finishing your homework at the last minute!) These will be graded and returned to @Wyou as quickly as possible; well 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 0generate these). If you submit PostScript, please be sure the file will print on our department printers (use  ghostscript  or  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 ecs150/hand-in/hw n  "$where  n  is the homework number. Be sure the account bishop can read that directory and the files in it! We will copy xthe homework out, and send you a letter saying what we copied and the date of last modification of the file. (This will pbe used as the time of submission.) At a later time, we 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 0*pany commands you give, and their output, to show how you did the problem); otherwise, even if you get the right answer, 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 $$ rWe do not mind being asked for help; indeed, we welcome it because it helps us know what the students are finding 0tdifficult or confusing, and sometimes a few words about the problem in class will clarify the assignment immensely. uYour questions may also point out ambiguities that we didnt think of, so the more questions you ask, the better for @ everyone! <Ϫ }We  do  mind being asked for help before you have tried to think the problem through; the classic objectionable ques0۪otion (this really happened) occurred on a programming assignment in which the class was given a buggy program. oThe assignment said the program did not work, and the homework was to debug it and make it work. Within 10 minwutes of the 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; ( oread all relevant handouts, sections of the textbook, and news articles (because your question may be answered 7@ there); and )F`:tried everything you could think of to solve the problem. *T rWhen you come to us, or send us a note, asking for help, please describe whatever you have done to solve the probp`wlem, because the first question we will ask you is What have you tried to solve the problem? This isnt because we vthink youre wasting our time; its because understanding how you have tried to solve the problem will help us figure tout exactly what your difficulty is and what we can do to help you. Remember, we will do everything we can to avoid @rsolving the problem for you; when we give you help, our goal is to help  you  solve the problem yourself. HHˆ>TIHHˆHNJJ ld>XNN HHˆ>YLHHˆN"#` Dont Delay! '$ sWe must emphasize the importance of taking time to think through, outline, and draft your answer, thoroughly. More 0wpoints are lost through unclear organization, or superficial answers, than anything else. So do think both your answer yand 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 0Xmyou write your answers for submission. When we decide on the due dates, we assume you will spend significant wamounts of time solving (at least some) of the problems. If you choose not to do this, you will have difficulty finish@ing the assignments on time. 2#`Grades ,$ lYour grades will be mailed to your CSIF account when the homework assignment is graded. Please be sure that 0account will forward mail to wherever you want to see the grade. If the letter bounces, we will  not  try to figure out @mwhy. (With 120 people at least! in this class, its simply not practical; the graders will be too busy.) +#`Late Homework 8$ڪ qUnless the assignment says otherwise, we wont accept them. The submission directory will be disabled at the due 0檞ttime, so you wont even be able to submit late homeworks. Requests for exceptions will be handled on a case-by-case @basis (in other words, ask). 9# `Grade Appeals :$ vIf you feel that there is an error in grading, please come see me or the TA and well look over it (and possibly talk 0'pwith you about it). However, dont dally; any such request must be made within one week of when the grades were @8made available. After that, we won't change your grade. ^#L`Important Note f$^ |Currently we have a lone grader for  both  sections. We are trying to hire two more, but if we cannot, we will only pjrgrade a portion of the homework, and scale the scores accordingly. (For example, if the questions we grade have a ~total point value of 30 points, we will treat the homework as though it were 30 points total.) We will  not  announce ubeforehand which questions we will grade, so you still will need to do all questions. We hope it wont come to this, @4but just in case, we wanted to warn you in advance. HHˆ>[LHHˆKQMM ld>_QQ HHˆ>`OHHˆ|--Qm h&All About Laboratory Assignments e$ uThere will be some laboratory assignments. The first will involve the use of the system calls of MINIX to write some 0simple C programs that could be part of a  shell . For this class the shell is not considered part of the operating system. pThe remaining assignments require minor modifications to MINIX to improve its performance and functionality, or wjust to play with its code. This handout describes some general thoughts and techniques for doing the labs, as well as @awhat is required, how to submit it, how late labs are handled, and other administrative matters. Oh tThe ECS 150 Pentium Laboratory is located in 083 Engineering Unit II (in the basement). Its hours have not yet been t@Cset, but it generally will be open for the same hours as the CSIF. .#` Lab Partners Z$ rYou may do these assignments individually, but we prefer you to work in teams of two to three. You will find this 0uhelpful, too.If you work in a group, then you should expect to stay with that group for the duration of the quarter, @Cunless the other member or members drop the class or go on strike. /#`"Turning In Laboratory Assignments Y$⪠ nLab assignments will be due by 5 PM on the due date, unless noted otherwise on the assignment. You must demon@Pstrate the solution to the grader (who will be one of the teachings assistant). 0 vTurn in lab assignments by copying all new and changed source code files for the assignment to a floppy diskette. The @ diskette is to be labeled with: 1 rThe name(s) of the person(s) turning in the assignment (if done by two or more people, then the names of  all #@#partners must be on the diskette). 62 The names of all files copied to the diskette for each problem ( e . g .,  #1:myprog1.c, myprog2.c ; 0>o #2:myprog2.c, myprog3.c ). It is perfectly fair for you to use some programs for more than one prob@lem in an assignment. n!X vIf you turn in a diskette that is missing files or has the wrong files for the assignment, you can substitute the cordrect ones with a 30% penalty.  I  really  hate doing this, but when it was not done, individuals abused substitution poli$@dcies that were more lenient. Then put the floppy into the homework box located on the second floor. i~ yYou also must sign up for a time slot to demonstrate your solution(s) to the graders. Sign-up sheets for time slots will 0qbe posted 2-3 days before each assignment is due. We encourage you to finish your assignments early. The TA will have significant office hours in the lab, and if you demonstrate your solutions before the due date ( all  problems must @vbe complete to demonstrate early), then you will have the opportunity to fix any bugs found during the demonstration. ] sIf you did the assignment as a group, then all members of the group must be present for the demonstration. Be sure 0tthat all members of the group are familiar with all code written and changed, because the grade for each assignment |depends in part on the answers given to questions the grader asks about the code and the reasons for your approach.  It %@is probable that you will fail a lab if you dont understand the solution ,  even though other members of that group pass V!⪌ |Important : Please remember that a TA cannot be present in the laboratory for all hours in which the lab is open (these 2$qhours are usually 10:00 AM to midnight, Monday through Friday. As the due date for a lab approaches, the TAs are slikely to be very busy; you will find them much more sympathetic if you approach them with questions well before a @ lab is due. =#`!Doing the Laboratory Assignments F$1 lYou may do the assignments on the Pentium computers in the lab or on your own PC. The books come with MINIX p=son a CD. If you do the assignments on a PC, then you may bring your PC to the lab to demonstrate your solutions or pyou may demonstrate them on a PC we will have in the lab for that purpose. However, if you decide to do the lab sassignments on a PC then you are responsible for ensuring that your solution works on the machine used for the demqonstration! There are many different PC configurations and corresponding versions of MINIX. Therefore if you are xplanning to use the grading PC for your demonstration, test your solutions on it to ensure that there are no compatibil@%ity problems before turning them in. HHˆ>bOHHˆNTPP ldDOTT HHˆDPRHHˆw  jjTD#`Asking For Help L$(Everything in  All About Homework Assignments  applies here. Please try to debug problems yourself  before  seeking @$help; you will learn more that way. M#` Dont Delay! ?$P pWe must emphasize the importance of taking time to design your program, or understand the code and the modifica0\ntions you must make, thoroughly. More programming problems arise from improper design than anything else, and othe few hours you spend on design will be amply repaid by shorter coding and debugging phases. So do think the vdesign and interfaces through, and as always try to find the simplest way to do the assignment (within the limits @%given in the assignment, of course)! C wDo not leave assignments for the last minute. The assignments are non-trivial and will require significant design time 0nbefore you start programming and debugging. When we decide on the due dates, we assume you will spend signifiwcant amounts of time on design as well as coding and debugging. If you choose not to do this, you will have difficulty @#finishing the assignments on time. P#` Some Notes >$ULUUUA(zPlease dont skip laboratory assignments. This will certainly bias the professor (me) against you. It also will hurt 4U@yyour grade substantially (check the weightings of the grades above to verify this). It will also hurt your understanding uof how real operating systems work. You have the opportunity to work with a little, but fully functioning, operating psystem. Many computer scientists learned operating systems by reading the code to UNIX Version 6, which was subtstantially smaller than current versions of UNIX. MINIX gives you essentially the same opportunity. This experience twill be invaluable to you. It will also impress interviewers when you go for interviews, and will help you immeasur@Iably if you ever have to work on a larger operating system (like Linux!) x5U: vIll let you in on a secret that faculty members who taught this class before told me. Except for the pain in dealing 0AU9twith the MINIX development environment (which is impoverished at best), the labs are really easy. Most students get @-perfect grades. But dont tell anyone else R#d` Late Labs S$vU7 wWe will accept late lab assignments up to one day after the due date and time, and will deduct 20% of the value of the 0U6zassignment (so if the lab assignment is worth 100 points, you lose 20 points regardless of your score; if it is worth 200 @tpoints, you lose 40 points). Requests for exceptions will be handled on a case-by-case basis (in other words, ask). T#`Grade Appeals $U4 vIf you feel that there is an error in grading, please come see me or the TA and well look over it (and possibly talk pU3swith you about it). However, dont dally; any such request must be made within one week of grading. After that, we @won't change your grade. HHˆDRRHHˆQWSS ldDWW HHˆDUHHˆ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 0mwaccess control, which will play a part in how you will use UCDisk. It also is accessbile from a large number of places xon 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 avail0rable 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 0tprotocol Kerberos is used to authenticate you, which in turn controls what you can access. This means your password is  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 lYour UCDisk home directory has your UCD login as its name. For example, my UCDisk home direcory is called 0 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 0FoUNIX computer systems. (Sorry, you cant do it through a Mac. The Mac doesnt handle the right versions of Kervberos.) 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ˆDUHHˆTVV l}? ND]Y? FBW{e }?H NDXZ?H FBW~e... }H NDYH FBWe }? N D`\? FGWe }?H N D[]?H FGWe- }H ND\XH FGWe }? NDc_? FHWe }?H ND^`?H FHWe-- }H ND_[H FHWe }? NDfb? FIWe }?H NDac?H FIWe° }H NDb^H FIW e }? NDie? FJW e }?H NDdf?H FJW e® }H N DeaH FJW e }? N"DCh? FKW e }?H N$Dgi?H FKWe© }H N&DhdH FKWe ~H¯!GRH¯!SG" uI would make penalties more dire, but I couldnt enforce any of the ones that come to mind, such as requiring you to pquse no system other than MS/DOS and no language other than machine language for the rest of your academic career @in computer science. }~H NDbc~H F.We }HNDefH F/We }HNDhiH F0We }HNDklH F1We }HNDnoH F2We }HNDqrH F3We } HNDtu H F4We }H Q<DxsH F5GeN }H Q>DrCH F5Ge }HQ@DuHF9g% P:ManHeadinEg2 }HQBDtvH F9G4eP }HQDDuwH F9G5eN }HQFDvxH F9GBeN }HQHDwvH F9GHe }HQJzHLgI% P:ManHeadEing }HQLy{H LGJeP }HQNz|H LGKeN }HQP{}H LGNeN }HQR|H LGOe }H QTH MGQe P:ManCode }H QV~H MGUeP }H QXH MGWeN }H QZH MGXeN }H Q\yH MG[e }H Q^ H NG\e P:ManBody }H Q`H NG^eP }H QbH NG_eN }H QdH NG`eN }H Qf~H NGbe }H QhB H OGceP:Line }H Qj H OGdeP }H Ql H OGeeN }H Qn H OGfeN }H Qp H OGge }DQDDFPgh% CSS Export E Encoding }HQD H FPGie }HQDXH FPGje }DRDWDFQgk% Export EnEcoding }HRDH FQGle }HRD H FQGme dLeftd;Rightd ReferenceddHTMLdDHTMLd Headingsd d !d :d Id Ld Od RdU @@ XMapping Table Title. @@ XBody. f@T Y#Heading1Body.  f@@YTitleBody. @@ XFooter. f@T X TableTitleT:Table : . f@ Y $2Body.  f@@Y TitleBody. @@ YMapping Table Cell. @@YMapping Table Cell. 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@ 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 Y X 1 X ڝXXEmphasis Y  BoldItalic Y  BoldItalic XItalicXEquationVariables ڝX 1   BoldItalic XItalic XBold X1 XY XItalic   Y Y  X Y Y  Y  Y  BoldItalic YZZThinMediumDoubleThick@ Very Thin HHHHHFormat AH Mapping Table HHHHHFormat BH))) Mapping Tableh65HHHHH$PDHH+4?HHH68?HH :C?HHHTDB?HH*< ? @ 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 "O>#?#@#A#B#» %FC$D$E$ $&FF%G%H%6%'FI&J&K& &(FL'M'N'')FO(P(Q(((*FR)S)T)D()QFU*V*W*Vd ,FX+Y++Z+f +-F[,\,,],r ,.F^-_--`-~ -/Fa.b.k.c..0Fd/e/l/f//1Fg0h0m0i002Fj1k1n1l113Fm2n2o2o224Fp3q3p3r3 3Fs4t4q4u4h 9Fv5w5x5r5s5,d 7Fy6z6{6< 68F|7}7~7H7F888hL5Ft9u9v9w9x9hd ;F::::x :CF ;";#;$;d =  <<<<> ====? >>>K >@ ???W ?A @@@c@ AAA GFXBYBZB ;F%C&C'C(Cd EF)D,D-D DFF.E/E0E EKF1FBFCF HBF[G\G]G IGF^H_H`H JHFaIbIcI KIFdJeJfJ FJFgKhKiKhM9yLzL{L|L}Lh NL~MMMMMh OMNNNNNh #NO O O O OQF PPP*PFQQQComment ;C ;G D_DkGfM9d 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 FrameRomanM.Times New Roman.ITimesNewRomanPS-ItalicMT FrameRoman M.Times.I Times-Italic FrameRomanM.Helvetica.BIHelvetica-BoldOblique FrameRomanM.Times New Roman.BITimesNewRomanPS-BoldItalicMT FrameRomanfCourier0 HelveticaWTimesXTimes New Roman"Regular$Roman MediumBoldRegular ObliqueItalicfxQt*9n%\WUUI~oBhD-rۏ̨