Operating Systems EDA092, DIT400

Laborationer / Programming Assignments

Important! Read this information before you work on your assignment:
The solutions you submit must be all your own work. Submitting code which is in whole or in part the work of another lab group (or anyone else) counts as cheating in an exam, and the penalties are potentially severe. It is important that you read this page on Cooperation vs. Cheating before you begin any lab exercises.
Please see Chalmers rules.
The assignments must be done in teams, consisting of 2 students each. If you cannot find a lab partner, please use this list. You can either add your name and email address (in the same field) for other people to contact you, or you can contact directly people on the list. A good idea would be also to look for potential partners at the lecture room, before or right after a lecture.
Programming Assignment 1

The description of Assignment 1 is at this link The source program for the parser is at this link or as a tar archive at this link. You can also find some self-testing examples that can help you with the assignment here.

Further instructions (administrative nature)

All teams are required to submit a preparation report before attending any lab-time-slot, to the Fire system. To do that, answer the questions you will find here using this template and submit your answers to the Fire system.
Note that you must be paired into a group of two to be able to submit a report and book a lab slot! Do so early on!
The lab-work can be carried our remotely, while there are also supervised lab hours in order to get support with questions and to present your solutions.

Booking instructions: You can find the supervised lab hours for lab 1 below (more info about the supervised lab hours here).
All labs take place in room 6125.

Period-week	Day	Date	Time	Type
2	Thu	111103	17-21	Q&A
3	Tue	111108	13-17	Q&A
	Thu	111110	17-21	Demo
4	Tue	111115	13-17	Demo

Each group can book one timeslot from the ones marked as Q&A and another one from the ones marked as Demo. The first are intended for solving questions that might arise during the lab and the second for demonstrating the group's solution to the lab assistants. Please respect the intented use of the timeslots: groups that are coming for the first time on the last Demo slot will have no time to complete lab 1 and are causing problems to their colleagues who want to demonstrate their solution.

Booking link: You can book through this link here but read first the following instructions:
- A Google account is needed to book a slot but in case you don't have one you can use the course's account, with account name 'opersys.cse@gmail.com' and password 'startworkingearly'.
- Important! When you claim a slot please write in the first field your Fire group number (instead of what is written there by default).
Reporting of the assignment will be done in person, during supervised lab hours. The solutions shall also be submitted to the Fire system, that you find at https://fire.cs.chalmers.se:8036/cgi/Fire-os.
Deadlines: The deadlines for the preparatory report and final handin are right before your first and right after your last lab timeslot respectively.

Some links for C tutorials:

"C Traps and Pitfalls", A Koenig, Addison-Wesley

http://www.eskimo.com/~scs/cclass/notes/top.html

http://www.physics.drexel.edu/courses/Comp_Phys/General/C_basics/c_tutorial.html

http://computer.howstuffworks.com/c.htm

C Standard Library

Introduction to C Programming (University of Leicester, Computer Centre)

C Programming (Steve Holmes)

Programming Assignment 2

The description of Programming Assignment 2 is at this link

preparatory report

Note

here

The questionnaire is based on the OSP documentation included in the printed course material. This course material is available through the student distribution center at "Student Centre Maskingrand" at Chalmers. Remember to ask for the Operating Systems material!(not the "OSP manual")).

Further instructions

All groups are required to submit the aforementioned preparation report before attending a lab-time slot to the Fire system.
The Labs will take place in room 6225 at the following times: Times for Lab2 . It is also possible to work remotely if you do not need support from the lab assistants.
In that case, log in to remotex.student.chalmers.se, where 1<=x<=5

Booking instructions: You can find the supervised lab hours for lab 2 below (more info about the supervised lab hours here).

Period-week	Day	Date	Time	Type
4	Wed	111116	17-21	Q&A
5	Tue	111122	13-17	Q&A
	Wed	111123	17-21	Q&A
6	Tue	111129	13-17	Q&A
	Wed	111130	17-21	Q&A + Demo
7	Tue	111206	13-17	Q&A + Demo
	Wed	111207	17-21	Q&A + Demo

Each group can book two timeslots from the ones marked as Q&A, one per week, and another one from the ones marked as Demo. The first and second are intended for solving questions that might arise during the lab and the last for final questions and demonstrating the group's solution to the lab assistants. Please respect the intented use of the timeslots, as well as the "one slot per group per week" rule.

Booking link: You can book through this link here but read first the following instructions:
- A Google account is needed to book a slot but in case you don't have one you can use the course's account, with account name 'opersys.cse@gmail.com' and password 'startworkingearly'.
- Important! When you claim a slot please write in the first field your Fire group number (instead of what is written there by default).
Reporting of the assignment will be done electronically, according to the instructions in the assignment description document.
Deadlines: The deadlines for the preparatory report and final handin are right before your first and right after your last lab timeslot respectively.