HCC bookstore on-line

1. Discuss computer hardware, including CPU (also SMP and multi-core), I/O, memory (RAM and ROM), storage (disks and removable media), system clock, and bus.
2. Understand concepts and definitions of operating systems, including kernels, utilities, application software, application and user interfaces.
3. Discuss the history of Unix and Linux, including major innovations and features such as large number of utilities, pipelines, hierarchical filesystems, powerful user interface (the shell), multi-tasking (and time-slicing), and multi-user (and security), as well as the role of POSIX and Gnu.
4. Know of Unix related careers, certifications, and professional societies.
5. Understand login and logout procedures, including remote login using SSH, and setting, protecting, and changing passwords.
6. Transfer files between systems with sftp and scp.
7. Know the difference between Unix and Windows text files and how to convert files from one format to the other.
8. Run various commands from the command line, including communication/messaging tools such as mesg, write, talk, wall, xmessage, and irc.
9. Understand the X window GUI concepts including desktop environments (CDE, Gnome, and KDE), window managers, and remote GUI sessions.
10. Use the on-line manual and other available information resources.
11. Understand and use Unix filesystem security, including the role of the root user, users and groups.
12. Understand concepts of email including Internet email addresses, mailboxes, mail servers, mailer-daemon errors, and various related protocols such as SMTP, POP, IMAP, and MIME.  Use command line email commands such as pine and mailx.
13. Use the UNIX text editor vim to create and edit text files.
14. Use file related utilities, including understanding filenames and pathnames, special (device) files (such as /dev/null, /dev/tty, and /proc).
15. Use and understand various filter commands and other file processing commands such as file, diff, gzip, and tar.
16. Manage directories and use related commands.  Know standard directories (the Filesystem Hierarchy Standard).
17. Understand disk and filesystem concepts including disk formatting, filesystems, inodes and directories, and mounting filesystems.  Reporting disk space usage and limits with df, du, and quota.
18. Use removable media (e.g., flash drives, CDs, etc.) with mtools and auto-mounters.
19. Understand and use hard and soft (symbolic) links.
20. Search for files using find and locate.
21. Set file and directory permissions and attributes correctly, using chmod, chown, chgrp, umask, and touch.  Use octal numbers for permissions.
22. Discuss different shells including Bourne shell, C shell, Korn shell, Bash, and Z shell.  Use POSIX shell features effectively including quoting, command grouping (and sub-shells), wildcards (globbing), command history, I/O redirections (including noclobber mode), and aliases.
23. Use basic Korn, Bash, and Z shell extensions such as auto-completions.
24. Set and examine standard environment variables, including HOME, TERM, PATH, PS1, TZ, etc.  Change and examine locale settings (locale command and the locale environment variables (LC_*).  Change and examine other settings with set, set -o.  Use and modify login and other startup scripts (e.g., .profile, .bashrc, and /etc/profile).
25. Understand the basics of shell scripts, including running scripts in the current directory, correct permissions for shell scripts, comments, the she-bang line, sourcing scripts, command line arguments to scripts, arithmetic, command substitution, the exit status, and exit, test, and the if statements.
26. Know process concepts including process IDs, fork and exec, system (daemon) processes such as init, be able to examine processes with standard utilities and change process priorities with nice and renice.
27. Understand how to run processes in the background and use job control.
28. Understand signals, and be able to send signals to processes with kill.  Allow processes continue after your session ends (using nohup).
29. Understand job scheduling concepts and use job scheduling commands including at, atrm, atq, and crontab and anacron (or periodic).  Control the use of these commands with allow and deny files.

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.)

• 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 only cover material discussed in class or assigned as reading before the exam.  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 unexcused 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, projects, and homework assignments.
• 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 Unix 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.
• 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 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, 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.
• 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, being out of town for work, or military service.  Remember documentation will be required.)

• The current flu pandemic requires 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.  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 prevent 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 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).  Every effort will be make to grade projects within a week of the due date, or as soon thereafter as possible.  Further details will be provided with your first project.  (See also submitting assignments below.)

You may work together in small groups (two or three people) for the homework assignments, provided the names of all who worked together are listed.  Each student must still submit their own copy.

Homework assignment questions are intended to focus your studying of the readings and to stimulate class questions and discussion.  For this reason they are generally due before the class where that material is covered.  It is not intended that students can answer all the questions assigned, but you must show you have thought about the questions and read the required material in order to earn an B grade or higher.