Labs are graded during the lab time. You must attend the lab to get the grade.
Week | Starting | Lab | Due | Posted |
---|---|---|---|---|
1 | No Lab | |||
2 | 1: Introduction Recorded Introduction |
2025-01-03 01:01 | ||
3 | 2: unix Commands I Recorded Introduction |
2025-01-21 12:01 | ||
4 | 3: unix Commands II Recorded Introduction |
2025-01-03 01:01 | ||
5 | 4: Text Processing I Recorded Introduction |
2025-01-03 01:01 | ||
6 | 5: Text Processing II Recorded Introduction |
2025-01-03 01:01 | ||
7 | Reading Week | |||
8 | 6: Make Files | 2025-01-03 01:01 | ||
9 | 7: Shell Programming I | 2025-01-03 01:01 | ||
10 | 8: Shell Programming II | 2025-01-03 01:01 | ||
11 | 9: Shell Programming III | 2025-01-03 01:01 | ||
12 | 10: The GNU Debugger | 2025-01-03 01:01 | ||
13 | 11: Git | 2025-01-03 01:01 |
The labs are the hands-on portion of the course. In labs you are taught how to use the hopper Linux development environment under EMACS. As well, labs are used to work on tasks and discuss assignments.
Each lab is broken down into two parts. In the first part, the Lab Instructor discusses the week's topics in terms of implementing them on the computer. This usually involves hands-on work on the PC network. After this instructional part is over, there is a lab task. Tasks are marked in the lab you start them in. You may not continue a task in later lab.
The Lab Instructor will make alternate arrangements in case of equipment failure, holidays, illness, etc.. These changes will be posted to the course mailing list. Check your email on a regular basis!
Switching labs is OK if you receive the Lab Instructor's permission ahead of time.
Please bring your course notes to each lab session.
Lab work builds upon previous work: if you fall behind, you stay behind, so keep on top of things. If you are taking far too much time to do your work, then you didn't understand something, you didn't remember something, or you don't know how to handle a tool. Get help immediately!