1. Understand and manage basic system and network security, including permissions for files and directories, ACLs (access control lists) and attributes, SetUID/SetGID, file locking and lock files
2. Understand the basics of isolation techniques (chroot, BSD jails, and Solaris zones), mandatory access controls (MAC) such as SE Linux, AppArmor, and LIDS), hashing, encryption, and digital signatures
3. Understand the basic concepts of role-based access control
4. Understand and manage security policies using sudo, PAM, and TCP Wrappers
5. Understand and use regular expressions
6. Understand and modify standard system shell scripts including boot up scripts and service scripts
7. Use and secure cron, anacron (and periodic), and at
8. Manage, locate on the Internet, and install documentation; and create man pages using nroff
9. Understand basic use of development tools: the C compiler, make, source code management tools (RCS and others such as CVS, Mercurial, and Git), using patch, creating RPM packages, using shared libraries
10. Understand software licensing and issues of open source software
11. Understand the concepts of a system kernel, including loading, booting, RAM disks, and loadable kernel modules
12. Understand, install, and upgrade kernel modules and use kernel patches
13. Customize, configure, and install kernels from scratch (rebuild from source)
14. Perform system and service monitoring, using alerting tools, and understand process accounting and system auditing
15. Understand, manage, and configure system logging, log file rotation, securing log data, using a central loghost, integrating logs from Windows, and using logs
16. Understand basic system tuning
17. Understand processes, threads and SMP (multiple core CPUs), and manage processes (create, monitor, control, and kill)
18. Understand networking and TCP/IP basics (addressing, port numbers, RPC)
19. Configure basic DHCP and static IP configuration, and use trouble-shooting tools
20. Setup, configure, and troubleshoot common problems for basic DNS services, including configuring the resolver, /etc/hosts and other files, configuring a caching-only name server, and using DNS related tools such as dig, nslookup, and whois
21. Understand and configure email services, including mail server, POP/IMAP, web mail, mailing lists, email aliases, and virus and spam control
22. Setup and configure time, time zones, locales, and using NTP
23. Understand (including hardware requirements), manage, and configure basic Apache web services"

A class wiki has been set up for your use, at YborStudent.hccfl.edu/UnixWiki/.  To add or modify any content you must create a login for yourself.  You can use this wiki to hold discussions, ask questions, and contribute information to the collaborative study guide. 

You will need your own floppies/flash disk, writing materials, and three Scantron 882–E or 882–ES forms.  You can use HawkNet (WebAdvisor) or Florida Virutal Campus (Formerly FACTS.org) to obtain your final grade for the course.

HCC DM Open Lab
Computers are located in the computer science department open lab in DTEC–462.  Lab hours are:

Grading scale:  A=90-100,   B=80-89,   C=70-79,   D=65-69,   F=0-64
(Or you can elect to "audit" the class during the add/drop period.)

(Collaborating on the class wiki counts as up to 5 points extra credit, as does active class participation.  See below for details.)

• No makeup exams will be offered without the prior approval of the instructor.
• Exams will be closed book and closed note multiple choice exams.  While the exams are non-cumulative, each does build upon knowledge acquired earlier.  Exams are based mostly upon material presented in class however some questions may be from assigned readings (the textbook and on-line resources).
• Exams will never cover material not yet discussed in class.  Should the class fall behind the course schedule some topics shown on the syllabus due for an earlier exam will be tested on the following exam instead.
• Regular attendance is imperative for the successful completion of this class.  The textbook and on-line resources should be considered as required course supplements; in other words the course is not based on the text.
• All phones, pagers, and beepers must be turned off during class time, except with prior permission of the instructor.  No food or drink is permitted in HCC classrooms.
• Attendance will be taken within 5 minutes of the start of class; after 4 absences and/or lateness, the student will lose 2 points off the final grade for each additional occurrence.
• If you miss a class you are still responsible for the material covered in that class.  All students should exchange contact information (name, email address, phone number) with at least one other student in the class.  If you must miss a class, you should then contact another student and request they take class notes for you.  (Note Campus Cruiser has email and discussion board areas for our course.)
• Credit for class participation includes attendance, preparedness, and adding to class discussions by asking questions and participating in discussions.  Playing computer games, surfing the Internet, or working on assignments for this or other classes during class time will lose you credit.
• Additional time outside of class will be required.  For typical students an average of between 6 and 10 hours each week outside of class are required for preparation, practice, and projects.  Note some projects will require you to complete them from our classroom (or the open lab).
• Students are expected to prepare for each class by completing all reading assignments, reviewing examples and model solutions provided, and practicing outside of class.  This is important — you can't learn a skill such as system administration only by attending class and reading books.  You must practice several hours a few days each week!  If you won't have enough time available, consider auditing the course.
• Students are expected to check the class website regularly.  Any syllabus changes, class cancellations, project assignments, and homework assignments are announced in class and posted to the website and the RSS feed for this class.
• A student shall not, without my express authorization, make or receive any recording, including but not limited to audio and video recordings, of any class, co-curricular meeting, organizational meeting, or meeting with me.  Further you do not have my permission to post on the web or otherwise distribute my class lectures and other course materials.  (You can distribute freely any materials I make publicly available from the HCC (or the wpollock.com) website, without asking permission, provided you give me credit for the work and don't alter it.  Any other use will require expressly given permission.
• Working together on individual assignments is considered as cheating!  Turning in someone else's work without giving them credit is also considered cheating (plagiarism).  Cheating will result in an automatic F (zero) for the project for all parties.  Note that some projects may be group projects, where each member of a small group works together on a project.  It is also OK to ask a fellow student for class notes (in the event you miss a class) or for help in understanding the text or material given to the class (e.g., examples on the class website).  It is encouraged to study together as well.
• You must follow the academic honesty policy and the student code of conduct for HCC.  A second cheating offense will result in an F for the course, and your name will be turned over to the dean for further handling.  I take these matters very seriously.  You have been warned!
• Communications Policy:  I will respond to your emails within 48 hours or two business days.  HCC policy is that grades can only be discussed in person during office hours, or via email only if you use your assigned HCC HawkNet (or Campus Cruiser) email account.
• Every effort will be made to stick to the weekly schedule for our course.  However it may happen that we will fall behind the schedule at some point.  If so no topics will be skipped.  Instead we will attempt to catch up over the following weeks.
• Please be aware that if we fall behind on the weekly schedule, the topics discussed may not match what shows on the syllabus.  The weekly schedule may (but probably won't be) updated in this case.
• In the case we fall behind, the homework assignments are automatically postponed until we do discuss that topic in class (i.e., the next class).  Projects and in-class exams will not be automatically postponed.  Should your instructor deem it necessary, projects and exams may be rescheduled; this will be announced in class.
• Hawk Alert text messaging service allows you to receive important information regarding campus closures or emergencies.  You may also sign up for financial aid notifications and registration and payment deadlines.  This is a free service, although some fees may be applied by your cellular service provider or plan for text messages.  To sign up, or for more information, visit www.hccfl.edu/alerts/.
• No appointment is necessary to see me during my scheduled, on-campus office hours.  You can just walk-in.  You can make appointments for other times as long as I'm available. 
• Occasionally my office hours will be canceled on short (or no) notice, for example if the dean calls me for a meeting.  Before driving out to campus just for my office hours, you can contact me the night before to make sure I still plan to be there.
• Late Policies:  Late assignments ( homework assignments, projects, or exams) generally will not be accepted.  An assignment is late if not turned in by the start of class on the day it is due.

  Late assignments will be accepted late only if you obtain the instructor's permission prior to the due date of the assignment, or for a documented serious medical reason.  All late assignments are subject to a late penalty of at least one letter grade (10%) regardless of the reason for the delay.

  Projects and homework assignments later than one week will receive a more severe late penalty; very late assignments without adequate excuses will receive a grade of F (0).  However if you have a very good reason your instructor may waive any or all of the late penalty.  (Examples of good reasons include extended illness that prevents working, or being out of town for work reasons.  Remember documentation will be required.)

• The dangers of the flu or another contagious disease require some changes to normal policies.  HCC is implementing the recommendations for institutions of higher learning of the CDC.  (See www.cdc.gov/h1n1flu/guidance/ and www.flu.gov/ for guidance from the CDC.)  You won't need documentation if you miss class due to the flu.  (But if you think you have the flu, you should see a doctor as soon as you can.)  In the unlikely event of a school closure, some plan to make up the missed work will be made.

  If you think you have the flu, stay home.  Do not come to HCC until 48 hours after your fever has broken as you are still infectious.  Also people are infectious to others for a day or so before they have any symptoms.  Flu is spread by touching doorknobs, computer keyboards, railings on stairs, etc., that were touched by someone with the flu.  Avoid shaking hands; use the fist shake (touching of fists) if you must use a physical greeting.  The most effective way to avoid catching the flu is to wash your hands frequently, especially after touching something that was touched by others.  Avoid unnecessary touching of eyes, nose and mouth.  While not as good as properly washing hands, hand sanitizers have been installed throughout the campus; use them often.

Projects will be assigned at various times.  You will have sufficient time to complete the projects, usually at least a week.  You must work on the projects typically outside of regular class hours.  You may work together in small groups on projects provided the names of all who worked together are listed on each student's submission.  Each student must still submit their own copy of the assignment.

There is no requirement that you re-install your system; you are permitted to continue using the same disk as for Administration I, if it it available.  However if that system is unstable you are encouraged to install it again.  directions for doing so are shown at the top of this class web page, but grayed-out.

If you did not submit the final project Backups from the previous term, then that project will be your first required project of this term.  If you submitted this project for credit last term, do not submit it again (so you will have one fewer project required than those who didn't complete it already.)

Projects are graded on the following scale:

A = 95% (Excellent: Good design with good comments, style, and extras)
B = 85% (Good: Good design, some comments, readable style, and it works)
C = 75% (Acceptable: Project objectives are met or are close to being met)
D = 65% (Unacceptable)
E = 10-64% (Variable credit: At least you tried)
F =  0% (Didn't hand in the project)

Minor extras worth +5 points, minor omissions or poor design worth -5.

Projects are not graded when turned in.  They are graded all at once, sometime after the project deadline has passed (usually the next weekend).  (See also submitting assignments below.)

Your instructor is the editor and moderator of this study guide (and for all material posted on this wiki site).  Some time will be given for students to correct postings.  However, in order to ensure an accurate study guide, the instructor may edit, add to, or remove material posted by students.

Your contributions will be graded based on correctness, completness, and clarity.  Note regular posting is required to earn extra credit; one large post the last week of the term will not earn much (if any) extra credit.