Introduces the basic concepts underlying computer operating systems and computer networks and provides hands-on experience with their implementation. Covers the basic structure of an operating system: application interfaces, processes, threads, synchronization, interprocess communication, processor allocation, deadlocks, memory management, file systems, and input/output control. Also introduces network architectures, network topologies, network protocols, layering concepts (for example, ISO/OSI, TCP/IP reference models), communication paradigms (point-to-point vs. multicast/broadcast, connectionless vs. connection oriented), and networking API's (sockets). Uses examples from many real operating systems and networks (UNIX, MS-DOS, Windows, TCP/IP, Ethernet, ATM, and token rings) to reinforce concepts.

The official prerequisite for this course is CS 2600. This course will be project-centric, and all students will complete in projects in groups of two (or possibly three, if necessary). Thus, to succeed in this course, you must be able to work in a group. I will allow you to form your own groups, and the course staff will serve as a matching service if necessary. As you are free to choose your partner(s), I will not be sympathetic to complaints at the end of the semester about how your group-mates did not do any work.

It is also highly recommended that you become familiar with using a debugger, as this will greatly aid you in completing the projects. At a high level, you should be motivated, eager to learn, willing to work hard, and make up, on your own, any prerequisite deficiencies you may have.

This is a junior-level course; I will not mandate you to come to class (you are still responsible for all the material covered in class). The class projects are a major part of this course, and please be aware that you will be working in groups of two. Lastly, note that 5% of your grade is based upon class participation. This is to encourage you to voice your ideas in class and to post them to the forum. Minimally, I must know your name by the end of the term in order for you to get any points for class participation.

We will be using Piazza as a course discussion/bulletin board. You are expected to check it at least once every few days, use it as the first place to ask questions, and answer others' questions. The course staff will regularly monitor the board, and your participation will count towards your grade.

For the C Bootcamp homeworks and the projects, we will be using resources and scripts that are available on the CCIS Linux machines. You need to have access to the CCIS Linux machines; if you do not have an account, be sure to sign up for a CCIS account as soon as possible.

You are welcome to use your personal machine if you wish. If you wish to remotely access CCIS resources, you should have an ssh client installed on your machine (they are available for all major operating systems). If you wish to compile and run code on your own machine, we recommend using a Linux distro or Mac OS X (it may be possible to get the code to compile on Windows, but you're on your own). Note that many of the testing scripts assume that they are being run on the CCIS network. Regardless, all of your submitted code must compile and run on the CCIS Linux machines.

Below is a rough schedule for the lectures in CS3600. This is subject to change; please check back often.

 

Lecture	Topic and slides	Reading	Due Date(s)
01  09/05 W	C Bootcamp 1	C §1–7
02  09/06 R	C Bootcamp 2	C §8–15	C Hw. 1
03  09/10 M	C Bootcamp 3	C §15–19	C Hw. 2
04  09/12 W	C Bootcamp 4, Overview	C §20	C Hw. 3
05  09/13 R	OS structures	OS §2.1–2.7	C Hw. 4
06  09/17 M	Processes	OS §3.1–3-3
07  09/19 W	Processes (cont.)	OS §3.1–3-3
08  09/20 R	Communication	OS §3.4–3.6
09  09/24 M	Threads	OS §4.1–4.4	Hw. 1
10  09/26 W	Scheduling	OS §5.1–5.4	Proj. 1 Milestone
11  09/27 R	Synchronization	OS §6.1–6.5
12  10/01 M	Deadlocks	OS §6.6–7.7;7.1–7.2	Hw. 2
13  10/03 W	Mass storage structure	OS §9.5–9.7	Proj. 1
14  10/04 R	File system interface	OS §12.2–12.7
—  10/08 M	No class—Columbus Day
15  10/10 W	File system implementation	OS §10.1–10.3	Hw. 3
16  10/11 R	File system implementation (cont.)	OS §11.1–11.3	Proj. 2 Milestone 1
17  10/15 M	Memory management	OS §8.1–8.3
18  10/17 W	Paging	OS §8.4–8.4	Hw. 4
19  10/18 R	Paging (cont.)	OS §8.5–8.6
20  10/22 M	Virtual memory	OS §9.1–9.4	Proj. 2 Milestone 2
21  10/24 W	Virtual memory (cont.)	OS §9.4–9.4	Hw. 5
—  10/25 R	Midterm exam
22  10/29 M	Networking overview	NET §1.1–1.5	Proj. 2
23  10/31 W	DNS	NET §2.1–2.3
24  11/01 R	Network architecture	NET §2.4–2.6
25  11/05 M	Data-link layer	NET §3.1	Hw. 6
26  11/07 W	Ethernet / Media access	NET §3.2
27  11/08 R	Bridging	NET §4.1	Proj. 3 Milestone
—  11/12 M	No class—Veterans Day
28  11/14 W	Internet Protocol	NET §4.1–4.2	Hw. 7
29  11/15 R	Internet Protocol (cont.)	NET §4.3
30  11/19 M	Reliable transport	NET §5.2	Proj. 3, Hw. 8
—  11/21 W	No class—Thanksgiving
—  11/22 R	No class—Thanksgiving
31  11/26 M	TCP	NET §5.2	Hw. 9
32  11/28 W	Congestion control	NET §6.2
33  11/29 R	Congestion control (cont.)	NET §6.3–6.4
34  12/03 M	Routing	NET §5.1	Hw. 9
35  12/05 W	NAT, BitTorrent	NET §8	Proj. 4
—  TBA	Final exam

Homework assignment and solutions will be posted here as they become available.

 

Homework 1 is due at the beginning of class on September 24th, 2012.

Homework 2 is due at the beginning of class on October 1st, 2012.

Homework 3 is due at the beginning of class on October 10th, 2012.

Homework 4 is due at the beginning of class on October 17th, 2012.

Homework 5 is due at the beginning of class on October 24th, 2012.

Homework 6 is due at the beginning of class on November 5th, 2012.

Homework 7 is due at the beginning of class on November 14th, 2012.

Homework 8 is due at the beginning of class on November 19th, 2012.

Homework 9 is due at the beginning of class on November 26th, 2012.

Homework 10 is due at the beginning of class on December 3rd, 2012.

Project descriptions will be posted here as they become available.

 

Project 1 is due at 11:59:59pm on October 3rd, 2012. The milestone for project 1 is due at 11:59:59pm on September 26th, 2012. No slip days may be used on the milestone deadline.

Project 2 is due at 11:59:59pm on October 29th, 2012 (Be sure read the FAT Implementation Notes or Inode Implementation Notes). The first milestone for project 2 is due at 11:59:59pm on October 11th, 2012, and the second milestone is due at 11:59:59pm on October 22th, 2012. No slip days may be used on the milestone deadlines.

Project 3 is due at 11:59:59pm on November 19th, 2012 (Be sure read the Implementation Notes). The milestone for project 3 is due at 11:59:59pm on November 8th, 2012. No slip days may be used on the milestone deadline.

Project 4 is due at 11:59:59pm on December 12th, 2012.

C Bootcamp project descriptions will be posted here as they become available.

 

C Bootcamp Project 1 is due at 11:59:59pm on September 9th, 2012. No slip days may be used.

C Bootcamp Project 2 is due at 11:59:59pm on September 10th, 2012. No slip days may be used.

C Bootcamp Project 3 is due at 11:59:59pm on September 14th, 2012. No slip days may be used.

C Bootcamp Project 4 is due at 11:59:59pm on September 19th, 2012. No slip days may be used.