CT320: Network and System Administration

What

CT320: Network and System Administration

When

Lecture: August 22–December 7, 2017; Tue/Thu 11:00ᴀᴍ–12:15ᴘᴍ
Recitation: L01: Mon 11:00ᴀᴍ–12:40ᴘᴍ, L02: Thu 5:00–6:50ᴘᴍ
Last drop: September 6; Last withdraw: October 16

Where

CSB 130 (lecture), CSB 315 (recitation)

Textbook

Unix and Linux Administration Handbook, Prentice Hall (2010),
ISBN: 0131480057, Nemeth, Snyder, Hein and Whaley (4th edition)

Instructor

Jack Applin <Applin [snail] ColoState [period] Edu> (email tips)

Office Hours

Wednesday 11:00ᴀᴍ–1:00ᴘᴍ and Thursday 1:00–2:00ᴘᴍ in CSB 246, and by appointment

GTA

Peter Qiu <yqiu [snail] mail [period] colostate [period] edu>

Office Hours

Wednesday 4:00–6:00ᴘᴍ, Thursday 4:00–5:00ᴘᴍ, and Friday 3:00–4:00ᴘᴍ in the Linux Lab

Grading

• The GTA grades everything. If you don’t like your score, talk with him first, then to the instructor if you still disagree.
• Assignments are done individually.
• Class participation will be measured with weekly iClicker quizzes. Get one; register it via Canvas.
• Recitation participation is necessary to complete the class successfully, since system administration is primarily a hands-on activity. Part of the class grade comes from successfully finishing the assigned lab work.

Homework is submitted & graded via ~ct320/bin/checkin and ~ct320/bin/grade, not Canvas. You can also check in homework via the web.

Late and Makeup Policy

Midterm and Final:

Recitations:

Assignments:

Conduct in Class

Don’t distract the students. I can’t force you to learn, but you must allow others to do so. This means:

• Do not distract others with conversation.
• Do not distract others with your phone.
• Do not distract others by reading the newspaper.
• Do not distract others by using your laptop in front of the class.
• If you snore, I will wake you up.

Policies

Students not already familiar with the CSU Honor Pledge should review this clear and simple pledge and always adhere to it.

Policies on cheating, plagiarism, incomplete grades, attendance, discrimination, sexual harassment, and student grievances are described in the Student Information Guide. All other matters follow the policies set in the current CSU General Catalog, and in the CS Dept. Code of Conduct.

Writing a program comprises two phases: design and implementation. You must do both on your own. It is unacceptable to have joint design but separate implementations.

• You may not copy or use, all or in part, someone else’s work.
• You may not give your work, all or in part, to someone else for any reason.
• You may not collaborate to produce one product turned in multiple times.
• You may not use work done in a previous semester by someone else.
• You may not post assignments on the internet.
• It is your responsibility to keep your work private from all others.

You MAY discuss assignments but the work you turn in must be your own. You have crossed the line if you start comparing someone else’s work to your own (or vice versa). You have crossed the line if you cannot explain/understand the work you submit. “I copied it from the internet” is not an explanation.