- Attendance is required.Exceptions need to ask for permissions.
- If you have any questions, feel free to stopy by or email me and ask at any time.
- Better to start the assignments early and ask the questions early.
- DO NOT ask the questions in the last minute.
- Ask for the permission of late hand in before the due, NOT after the due.
- I am open to any suggestions or comments on the labs.
- All works for this class must be done individually.
- Discussion on how to solve the assignments is encouraged but also need to give credits by acknowledgements or to collaborators, especially from books, the Internet.
- Any work from other students or any other source SHOULD NOT be submitted as your own.
- Follow the instructions in Section IV of Clarkson's official regulations.
In this class, students will frequently use polaris to upload the assignments. The credentials for polaris should be the same with your clarkson email account and password. If you get access denied to polaris, don't hesitate to go to OIT or helpdesk for help.
Polaris behaves as a remote linux machine. Inside polaris, we are maintaining a class directory cs444/sp13/ to store OS assignments. Each assignment is a separate directory ASSIGNMENT_NAME/ ( a placehold for the real assignment name). Your assignment should be uploaded to your own directory, the same name as your clarkson id. You won't have permissions to other students' directories. You have write permissons to each assignment directory before its due time. You will only read permissons after the due.
Below are the common commands you may use in this class:
Log into Polaris
for example: ssh firstname.lastname@example.org
Change to your lab directory
for example: cd /afs/cu/class/cs444/sp13/attendance/huwj/
Upload your assignment
scp your_file email@example.com:/afs/cu/class/cs444/sp13/ASSIGNMENT_NAME/your_clarkson_id
for example: scp huwj_01182013.txt firstname.lastname@example.org:/afs/cu/class/cs444/sp13/attendance/huwj/
If you want to upload a sub-directory, you need to add option "
-r" in the
scp command.But don't wrap all your files in a directory and then just upload one directory into your class directory.Please upload all your files plus subdirectory directly. Thanks.
- Log into your assignment directory to validate the files' existence after you have uploaded.
- Don't compress your assignment files. Uncompress the files will take TA's extra efforts.
- Don't upload executable files or large files. The polaris has limited disk quota.
- Don't submit another assignment folder into your clarkson id folder.
Warning: This schedule is tentative and will change as the semester progresses!
|System Monitoring Lab||
Notes: System Monitoring Question Sheet is here
Due on 1/21/2013 Monday in class
|Write Your Own Shell||
Notes: C primer is here;
Lab PPT is here;
Shell Skeleton Code is here
|Write Your Own System Call||Note: VM only available in ITL lab machines|
Notes: Process vs Thread Question Sheet is here
Linux Code and Windows Code
Locking Granularity Assignment
Shell Assignment Due
|February break, enjoy!|
Linux Conditional variable Example is here;
Windows Semaphore Example is here
|Write Your Own Module||
Notes: helloworld Module code is here;
procfs Module skeleton code is here
|Introduction to the User-level File System||
User-level File System
Locking Assignment Due
|Write a Virtual Memory Management Module||Notes:
VM only available in ITL lab machines
vmm skeleton code is here
|Spring beak, have fun!|
|Hand-on Experience with Raid||Notes:
VM only available in ITL lab machines
iozone benchmark is here
|Raid Modelling Excercise||
Notes: RAID Questionsheet is here
Due on 4/12/2013
|Implement a Real-time Scheduler||
Notes: UFS skeleton code review
User-leve FS Assignment Due Extended
|Virtualization and Virtual Machine Management||
Notes: Question1-8 of RT lab Hardcopy Hand in
User-leve FS Assignment Hard Due
|Linux Kernel Bootstrapping||Notes: Last chance to make up Systemcall and RT labs|
|Week 17 Finals|
|Bye, Have a nice Summer Break!|