University of North Carolina at Chapel Hill
School of Information and Library Science

INLS 183: Distributed Systems and Analysis

Course Syllabus

Class Overview: All aspects of configuring and managing an Internet-based server with the Unix/Linux operating system. Software configuration, installation, upkeep and management; user management and issues; security and data integrity. Class sessions consist mostly of presentation and demonstration of the installation of a wide variety of software. Class assignments focus on hands-on experience with server administration.

Catalog description: Distributed and client/server-based computing. Includes operating system basics, security concerns, and issues and trends in network administration.

Class Goals:

1. To gain hands-on experience with Linux administration using a PC-type computer system;
2. To understand administrative tasks, topics and concerns;
3. To critically evaluate new systems, products or services related to server administration or use; and
4. To develop good habits for effective administration and for keeping informed of emerging issues.

Computer Usage: INLS 183 makes use of the SILS laptop requirement. This means that any student enrolled in any SILS program, or under UNC's CCI requirement, is expected to have unlimited access to a laptop computer. Unless otherwise announced in class or on the class schedule, laptops should be brought to class for each session, and be connected to the campus LAN by wireless or otherwise.

In addition, the class will make use of a small "lab" of PCs. Each student will be assigned to a small group that will share a PC throughout the semester. The PCs will be configured to run RedHat Linux version 7.3. Some students will choose to use their laptops as Linux servers instead, or to use a combination of available systems. Administrator (root) access is required for most INLS 183 assignments. Physical access to the "lab" is available when the SILS library is open (hours are posted online), but physical access is seldom required for assignment completion.

Pre-requisite knowledge: INLS 102, INLS 181 or comparable experience with the Internet. Basic Unix/Linux skills are assumed. The ability to author Web pages using HTML is assumed.

This is a Paperless Course: The course syllabus, assignment descriptions and notes will be online, linked from these INLS 183 Web pages. Student assignments will also be online. For more details about moving towards paperless courses, see Prof. Newby's Paperless Pages

Texts: Two texts are "recommended." Depending on your prior experience with Unix/Linux and your preferred style of reading, you might choose to employ an alternate text or none at all. In many cases, weekly readings will consist of online materials that can replace or supplement readings from the texts. You should complete readings before the class they are assigned for, then review afterwards as needed. The recommended texts are:

Stanfield, Vickie & Smith, Roderick W. 2001. Linux System Administration. Alameda, California: Sybex. ISBN: 0-7821-2735-5. Errata are online.

Sarwar, Syed M.; Koretsky, Robert; Sarwar, Syed A. 2002. Linux: The Textbook. Boston: Addison-Wesley. ISBN: 0-201-72595-9.

Evaluation: Students must complete all assigned work in order to receive a passing grade in INLS 183. Required work for the class consists of 10 systems administration exercises. For each exercise, students will choose some software to install or another systems administration task. There are 11 due dates for exercises during the semester, meaning that one weekly due date may be skipped.

Each exercise will be written up as a Web page, and linked to the student projects page for the class. Each exercise is worth 10 points, as follows:

• Presentation and layout (1 point)
• Introduction (1 point): overview of what the software is for and why it was chosen
• Narrative (3 points): description of the installation process
• Instructions for use (3 points): briefly, how to use the software
• Functionality (2 points): that the software actually works

Late assignments are downgraded at the rate of 1 point per day. Although the choice of what software to install or other systems administration task to perform is up to the individual, some basic criteria must be met:

1. Assignments must be progressively harder
2. Each assignment write-up must identify at least one problem, challenge or unexpected occurrence
3. Each assignment will include a link to an online script file or other log of the installation process
4. By the end of the semester, each of these must be accomplished at least once:
   • Install software that uses the X-Windows graphical interface
   • Install security-related software
   • Install system diagnostics or maintenance software
   • Install a server or daemon
   • Install a software package using RPM (the RedHat Package Manager)

Group work is permitted but not required. If you want to work with someone else for an assignment, these additional guidelines apply. Maximum group size is 3 persons for any assignment. Guidelines:

• Each person must write a portion of the assignment. Indicate within the assignment who wrote which portion.
• All people who work together on an assignment will get the same grade for that assignment.
• More work is expected of more people - the assignments should involve harder software, more writing, more problems solved, or otherwise go beyond what an individual would do alone.

Grading:

Class grading is based 95% on the systems administration exercises, and 5% on class preparation, preparedness and participation.

Letter grades for graduate and undergraduate students are as follows. Note that graduate +/- grading is used internally by SILS, but only the full letter grade (H, P, L or F) will appear on transcripts.

Points	95-100	90-94	85-89	80-84	78-79	75-77	70-74	70-79	0-69
Grad	H	P+	P	P-				L	F
Ugrad	A	A-	B+	B	B-	C+	C		F