Lab Schedule
All the C programs you write for this class should follow the well established good C coding conventions. If you turn in code that deviates from these conventions, you may not earn full credit for your solutions.
Your work MUST be handed in as git submissions to your repository for this class. Be sure to observe the name of the repository and to grant developer access to the instructors and all the class TAs. As a matter of practice, you are expected to:
- Add your solutions (to lab or pre-lab) periodically to your own git repository. Whenever you work on our solutions, in or outside a lab session, it is to your benefit to commit the files you advanced when you determine that they advanced your work. This will ensure that it will be possible to restore your correct work, if you happen to inadvertently break a solution that was working fine.
- Be sure to add, commit, and push all the files that are necessary to build all the executables in any given assignment. Don’t expect the assignment to enumerate all the names of the files you should submit. Rule of thumb: if you worked on something, add it to your git repo.
- If you ever get your git repo in a corrupted state, it is your responsibility to fix it and/or to ask for help to fix it. We understand that git can be finicky and that bad things may happen, but we trust you to work on ensuring that your repository is good shape by the due dates of your assignments. If you ran into git trouble, don’t wait until the last minute to seek help.
- It is your responsibility to commit your work by the deadline. Please understand that your git repo is your hand in – if files are missing or if the entire lab assignment is missing by the due date, your work will be graded accordingly. This means, don’t count on the instructors or the TAs reaching out to you to let you know that your work was not complete as submitted.
Pre-labs and Labs are due at 01:00pm on the dates listed. Note that the schedule is tentative and the topics may change. Finally, note that the link to the lab does not open until the day of the lab. Important: pre-labs will always be due at the start of their corresponding lab. It is essential that you complete the pre-lab BEFORE you tackle the lab assignment.
| Week | Date | Topic | Pre-lab | Lab |
| 1 | 01/20/2026 | Systems Programming in C (review) | Pre-lab 0 01/27/2026 | Lab 0 01/27/2026 |
| 2 | 01/27/2026 | Unix Processes | Pre-lab 1 01/27/2026 | Lab 1 02/03/2026 |
| 3 | 02/03/2026 | Interprocess communication: pipes | Pre-lab 2 02/03/2026 | Lab 2 02/10/2026 |
| 4 | 02/10/2026 | POSIX Pthreads | Pre-lab 3 02/10/2026 | Lab 3 02/17/2026 |
| 5 | 02/17/2026 | Interprocess communication: TCP sockets | Pre-lab 4 | Lab 4 |
| 6 | 02/24/2026 | Thread synchronization | Pre-lab 5 | Lab 5 |
| 7 | 03/03/2026 | Dining philosophers | Pre-lab 6 | Lab 6 |
| 8 | 03/10/2026 | Spring Recess | ||
| 9 | 03/17/2026 | Memory allocation I | Pre-lab 7 | Lab 7 |
| 10 | 03/24/2026 | Memory allocation II | No pre-lab | Lab 8 |
| 11 | 03/31/2026 | No new lab assignment | ||
| 12 | 04/07/2026 | Building a Unix Shell | No pre-lab | Lab 9 |
| 13 | 04/14/2026 | File system interface | Pre-lab 10 | Lab 10 no extensions |
| 14 | 04/21/2026 | |||
| 15 | 04/28/2026 | No new lab assignment |
