Mike's Guide to the CS 105 Labs

Forget Google to begin with!!! Look around the cs network to figure some things out before, during, and after a CS 105 lab.

• http://www.cs.hmc.edu/request will allow you to request system help from the staff. When Wilkes dies or goes very slow, http://www.cs.hmc.edu/request is the way to get the staff's attention.

• gcc NOT g++ All the C labs, except the bits lab, use gcc

• man -k is your friend. Recognize that a man does not always find pages hidden away in various manual sections.

• ps is a command that you should learn. Depending on options, ps will tell you about jobs you have running and about other jobs on the system. You can find out who has left a job hanging around.

• uptime is a quick way to see how loaded the system is.

• id will give you all your various user and group ids.

• top is a combination of uptime and ps on steroids.

• kill your jobs that are hanging around or someone else is going to be unhappy with you.

• README files are meant to be READ!!!

• QREFS are your source of HMC CS computer systems use.

• ssh is really important.

Mike Erlinger