Topics: Review of Unix basics and Intro to CVS I will be talking about pipes, redirection, job control, and wildcards, next week so you can keep it fairly basic. Feel free to use a few more complicated examples, just don't think you need to explain it all. One strategy I have used is to show them the list of common unix commands that is posted on the Online Tutorial section of the web site, and ask them which ones they are unfamiliar with. Tell them that they need to start learning more of them as they go along. You should pick 3 or 4 like grep, and diff and be ready to explain them. Please describe absolute and relative paths with some examples. This will also involve discussing the current working directory (and pwd). Explain ~/ as the home directory You may need to remind them that there is frequently more than one person working on a Unix machine, so they can use top or ps to find out what is happening (I will be talking about shell variables.) Try to spend no more than half the class on this topic. CVS --- Nearly all of the students have used CVS in CSC207 so many of them will be familiar with the basic procedure. There are a few who haven't so watch out for them. Go over the basic information in the Using CVS tutorial on the web site. (And point them to the tutorial.) You might ask them if they know how to permanently set an environment variable such as CVSROOT, and go over how to add the correct lines to .cshrc or .bashrc. I suspect students are still shaky on CVS. Doing an example would probably help them. My suggestion is to draw a picture on the board. repo working-copy / \ / \ / \ / \ c3ali CVS assignments / \ / / \ / CVSROOT assignments a1______________ / / \ \ / / \ \ a1 index.html Weather.java Weather.class ... / \ index.html,v Weather.java,v Then tell a story... - how does the working copy appear - where do I do all my work. (A student asked, "Do I run cvs commit in the repository or in my local copy?") - why is Weather.class in the working-copy but not in the repo? - how would I add a file? When does it appear in the repo? - what happens when I do an update? - what is th difference between update and commit - show them how to check out a new copy. Their working copy shouldn't change, and it is okay to delete the new copy if they want. - remind them never to edit or delete anything in the repo.