Instructor: Randolph Langley
Email: langley@cs.fsu.edu
Tel: 645-1225
Office: 103 MCH Building
Tuesdays and Thursdays, 2:00 until 3:15 in 103 Love Building.
Class home page:
- Wednesday, 1:30 to 3:00; 3:30 to 5:00 in 103 MCH
If my office hours are not convenient, please speak with me and we can schedule an appointment at a mutually convenient time.
http://www.cs.fsu.edu/~langley/CNT4603/2014-Summer/index.html
Computer and Network System Administration is an increasingly complex and essential field. The last five years have seen an upturn in the number of system administrators:
2001: 227,840 (http://www.bls.gov/oes/2001/oes151071.htm) 2002: 232,560 (http://www.bls.gov/oes/2002/oes151071.htm) May 2003: 237,980 (http://www.bls.gov/oes/2003/may/oes151071.htm) November 2003: 244,610 (http://www.bls.gov/oes/2003/november/oes151071.htm) May 2004: 259,320 (http://www.bls.gov/oes/2004/may/oes151071.htm) November 2004: 262,930 (http://www.bls.gov/oes/2004/november/oes151071.htm) May 2005: 270,330 (http://www.bls.gov/oes/2005/may/oes151071.htm) May 2006: 289,520 (http://www.bls.gov/oes/2006/may/oes151071.htm) May 2007: 309,660 (http://www.bls.gov/oes/2007/may/oes151071.htm) May 2008: 327,850 (http://www.bls.gov/oes/2008/may/oes151071.htm) May 2009: 338,890 (http://www.bls.gov/oes/2009/may/oes151071.htm) May 2010: 333,210 (http://www.bls.gov/oes/2010/may/oes151142.htm) May 2011: 341,800 (http://www.bls.gov/oes/2011/may/oes151142.htm) May 2012: 350,320 (http://www.bls.gov/oes/current/oes151142.htm) May 2013: 362,310 (http://www.bls.gov/oes/current/oes151142.htm) This course is an attempt to provide professional approach to the System Administration field, as well as an introduction to current technology.
Required: CGS 3406 or COP 3014.
The following courses and skills are desirable prerequisite knowledge for this class. Although not formally required, you will likely do better in this class if you have
- Taken undergraduate Operating Systems (COP 4610);
- Taken undergraduate computer architecture;
- Taken advanced UNIX/network programming;
- Skill in C programming;
- Skill as an advanced UNIX user, including the ability to program effectively in the Unix environment;
- Familiarity with networking concepts and applications.
To produce students who are capable of managing a multi-user networked computer system. This will include providing students with practical experience in
- Designing, installing, maintaining, and extending interconnected servers (Microsoft and Unix);
- Development of policy and procedures for users, administrators, and for regulatory requirements;
- Advanced systems management;
- Networking and communication; and
- Emphasis on independent problem solving skills.
Unix and Linux System Administration Handbook, Fourth Edition, by Nemeth et al, Prentice Hall, 2011.
Mastering Windows Server 2008R2, by Minasi et al, Sybex, 2010.
|
ITEM |
POINTS |
|
Midterm (given on Thursday, June 26th, from 2:00 to 3:15 in Love 103) |
30 |
|
Final Exam (given on Thursday, July 31, from 2:00 to 3:15 in Love 103) |
30 |
|
Assignments |
20 |
|
Class participation |
10 |
|
Final Paper (due on Tuesday, July 22) |
20 |
| A | 90% - 100% |
| B+ | 88% - 89% |
| B | 80% - 87% |
| C+ | 78% - 79% |
| C | 70% - 77% |
| D | 60% - 69% |
| F | 0% - 59% |
- Introduction
- Installing & booting multiuser operating systems
- Rebooting issues
- Virtualization
- Drive layout and treatment
- Storage
- System Administrator's view of the operating systems
- System Administration tools
- Resource management and performance analysis
- Local and remote file systems
- Computer hardware operating system-specific nomenclature
- Network protocols and network activities
- Directory Services
- Security
- Your physical environment
- BCP, DR, COOP
- System Design: Structural and off-site redundancy
- Storage (as time permits)
- Clustering (as time permits)
- Three layer architectures (as time permits)
- Drive Layout and Treatment (as time permits)
Assignments
Notice that part of your grade is determined by the work done in the assignments. Due to the nature of the projects, they must be done within the space provided in the Networking/SysAdmin lab (LOV 016),
Guidelines for assignment writeup:
- State the assignment objectives.
- Provide, in a diary/journal format, the steps you took to do the assignment.
- Mention lessons learned, especially those that come from making, finding and correcting mistakes.
- The writeups will be graded based on the correctness of content, clean layout, and use of proper spelling and grammar.
Please turn in assignments on time. No late submissions will be accepted.
Assignments must be submitted as indicated in the assignment on the appropriate day at the beginning of class. If the submission is via Blackboard, the link will disappear at the beginning of class.
Academic Dishonesty
Academic dishonesty will not be tolerated. Do not turn in other people's work as your own; this includes, but is not limited to, unattributed copying from web pages, other students' work, books, journals, or broadcast media. Citations and clear delineation of cited material from your own original work is mandatory.
The Florida State University academic honor policy is at http://dof.fsu.edu/content/download/21140/136629/AHP2010Revision.pdf
Official FSU statement on the Academic Honor Policy:
ACADEMIC HONOR POLICY: The Florida State University Academic Honor Policy outlines the University's expectations for the integrity of students' academic work, the procedures for resolving alleged violations of those expectations, and the rights and responsibilities of students and faculty members throughout the process. Students are responsible for reading the Academic Honor Policy and for living up to their pledge to "... be honest and truthful and ... [to] strive for personal and institutional integrity at Florida State University."Attendance
Attendance at all class meetings is expected, and attendance will be taken each class session. Please extend courtesy in class by arriving on time, staying until dismissed, and refraining from food and drink. You are responsible for all information explained in class, some of which will not be available in written or electronic form. I will not feel obligated to repeat announcements of future exams, assignments, schedule changes, question sets, pop quizzes, or hints on assignments. If you are forced to miss a class, it is also your responsibility to get class notes from a friend and check with me for handouts. I will use email and the class home page to give out assignments and general class information.
Absence
Excused absences include documented illness, deaths in the immediate family and other documented crises, call to active military duty or jury duty, religious holy days, and official University activities. Accommodations for these excused absences will be made and will do so in a way that does not penalize students who have a valid excuse. Consideration will also be given to students whose dependent children experience serious illness.
Communication
You should check your electronic mail frequently for information about this course, as well as the class home page. You are also encouraged to use email to ask questions and report problems.
ADA compliance
Please advise me at your earliest convenience (within one week) if you have a disability that will require a reasonable accommodation for the successful completion of this course. Also, as indicated above, you should register with the and provide documentation to the Student Disability Resource Center, and provide me a letter indicating the need for accommodation and indicating what type.
If you are experiencing difficulties
If you are experiencing difficulty, either with the class or for reasons outside of the class, or are concerned about your progress, please speak with me immediately.
The
above schedule and procedures in this class are subject to change
in the event of university schedule changes, calendar errors on my part, exigent circumstances, or if other
reasons develop during the semester.