This tutorial will help you get familiar with the Unix features of Mac OS X that we will be using in labs this semester. It assumes no Unix background, but it does assume that you are comfortable using computers with a graphical user interface, such as Mac OS or Microsoft Windows.
To get started, sit down at a Mac in the lab and go through this tutorial, trying things out as you go. Upon completion, you should be able to understand the basics of entering a command line, move around in the file system and view existing files, do basic manipulations of windows, do basic editing with the XEmacs text editor, and know where to find help.
The files you create in your "Home" folder are not actually stored on the computer on which you are working. Instead, they will be stored on our department's Macintosh file server, cortland. You can access your files on cortland from any computer in our lab.
All Mac Windows look like the following window:
Here are some basic window management operations:
You can start to get the feel for the environment by clicking on the Safari icon to start a web browser.
Go to the class web page and find the electronic version of this page. Bookmark this page; you will be referring to it often during lab.
The X11 Server will open a shell window in which will type Unix commands. For example, type the command "ls" in the shell window and press return. This command will list the files in your directory. A command consists of the name of a program, zero or more options preceded by '-', and zero or more arguments, which are themselves words. The command line is terminated with a carriage return.
If you make mistakes in typing on the command line, use the Delete or Backspace key to erase the previous character.
Here are other useful commands related to files:
One thing you will notice with Unix is that "no news is good news". Often if a Unix command is successful, it will produce no output! If it fails, you will receive an error message. Of the list of commands above, only ls and more produce output when they succeed.
ls List the files in the current directory cp file1 file2 Copy the file named file1 to a new file named file2 mv file1 file2 Rename the file named file1 to have the name file2. (mv is actually short for move, but it doesn't necessarily move anything!) rm file1 Remove the file named file1 (Warning: you may be used to your computers asking "Are you sure?" and moving things to the trash so you can recover things you deleted by mistake. This is not the case with the Unix "rm" command. You ask for it to be deleted and it will be deleted and it's not coming back!) more file1 Display the contents of a file lpr file1 Print the file named file1
The "more" command deserves some more comment because it is an interactive command. It displays your file one screenful at a time. After each screenful, it displays a prompt either consisting of the name of the file being displayed in reverse video (for the first screenful), (END) in reverse video (for the last screenful), or : (for all other screenfuls). The prompt appears at the bottom of the screen. At this prompt, you have several options, the most useful being:
You can try out "more" by typing "more /Network/Servers/cortland.cs.williams.edu/Volumes/Courses/cs136/examples/Hello/Hello.java". This will show you a file containing the Hello world program from class. (One useful tidbit: hitting the tab key will autocomplete directory and file names. Try typing "/Network/Ser" and then hitting the tab key.)
space Display the next screenful b Display the previous screenful q Quit more, returning to a shell prompt.
When you use ls to list your files, a directory will appear with / at the end of its name. At all times you have a current directory. Your commands are interpreted with respect to your current directory by default. So, for example, ls lists the files in your current directory if you give it no arguments. Here are some useful commands to manipulate directories:
Filenames in Unix can contain any characters, but they are often easier to deal with if you restrict yourself to filenames that consist only of letters, numbers, and '.'. A filename is typically divided into a descriptive name and an extension, separated by '.'. Extensions are purely by convention but typically indicate the type of file. For example, "myfile.txt" would be a text file, while "myfile.java" would contain a Java program. Extensions are generally optional although some programs, such as the Java compiler, expect them to be there.
mkdir dir1 Create a new directory named dir1. rmdir dir1 Remove the directory named dir1. You can only do this if the directory is empty. cd dir1 Make dir1 be the current directory pwd Display the name of the current working directory
Filenames can be given as names that are relative to the current working directory or as absolute names from the special root directory. Thus far, we have assumed relative names that refer simply to files in the current directory. We can also use relative names to identify files in subdirectories. For example, "mydir/myfile" is the file named "myfile" in the directory named "mydir", where "mydir" is located in the current working directory.
Each user also has a home directory. This is the directory that is the current directory when you start a new shell window. (You have already found your home directory through the standard Mac interface). No matter what the absolute pathname is to your home directory, you can always refer to it with the special relative pathname '~'. For example, no matter what your current directory is, if you type "ls ~", you will see a listing of the files in your home directory.
An absolute pathname always begins with / while a relative pathname never does. To find out the pathname that corresponds to your current directory, type pwd. Use pwd to find the absolute path for your home directory.
One last useful feature of the command line: Pressing the up arrow will give the last command you executed. Pressing return will run that command again. Try this. You can access older commands in your history by hitting the up arrow multiple times. To practice these commands, copy the Hello.java file to your home directory with the command
cp /Network/Servers/cortland.cs.williams.edu/Volumes/Courses/cs136/examples/Hello/Hello.java ~/Hello.java
Rename the file, move it into a newly created subdirectory, and practice the other basic Unix commands as well.
Close a terminal either by clicking on the red circle in the title bar or by typing the "exit" command at the prompt.
The top row are the titles of pulldown menus that are available. Initially, we will work with a few of these menus and a few keyboard commands. As you gain more experience, your repertoire of commands will grow and will move away from menus and toward keyboard commands. For now, let's create a new file. To do this, point at "File" and click the mouse button. Then select "Open...". At the bottom of the window, you will see "Find file: ~/" with a small black box following it. The box indicates where characters will go when you type. Type in the name of the file that you want to create and hit carriage return.
The last line of the XEmacs window is where command prompts and messages appear. The reverse video line immediately preceding it is a status line. It shows you the name of the file you are editing. Before that you should see -----. This means that the file is up-to-date. If it says, ---**, it means the buffer has been changed since it was last saved. If it says ---%%, it means that you cannot modify the file. After the filename is the "mode" that you are editing in. This should say "(Fundamental)", or "(Java)" when editing a Java file. Next is the current line number (L1 indicates the first line). Following that is an indication of how far the current line is in the file in terms of percentage. "All" indicates that the entire file is showing. "Top" indicates that you are on the first screenful. "Bottom" indicates that you are on the last screenful.
The area between the menu titles and the status line is the buffer that displays the contents of the file. Most of your typing goes directly into this buffer. Type some text. Notice the status line changes. You can move the cursor around using the arrow keys. Use the scrollbar to move through the file. Use the "Save" command from the Files menu to save the buffer to a file. Use "Exit XEmacs" from the Files menu to exit XEmacs. Notice the characters that appear in parentheses at the ends of command names in the menus. These tell you the keyboard characters to type to execute the commands without using the commands. For example, saving the buffer can be executed by typing Control-x Control-s. In the menu control characters appear as C-. Type these by holding the control key down at the same time as typing the second character. Another common way to enter commands is using the Escape key. This is abbreviated M-. In this case the escape key and the following key are typed separately. For example M-x represents typing the Escape key followed by the "x" key. You can also press the "Apple" key and "x" at the same time to achieve the same effect. Here are the keyboard sequences for the most common XEmacs commands:
C-v Next screenful M-v Previous screenful C-d Delete next character Backspace Delete previous character C-x C-s Save buffer to a file C-x C-f Open a file C-x C-c Exit XEmacs
You can find more XEmacs commands in the Emacs Hints Page.
Using keyboard commands is generally faster than moving one's hands back and forth between the mouse and keyboard as one must do to use the menus and scrollbar. While it takes extra effort to learn, the payoff is worth it in the long run in terms of speed of using the editor.
Assuming the program is free of compilation errors, a class file "Hello.class" will be created. This files contains the compiled representation of the program. To execute the program, you run the Java virtual machine with the command
The command line argument to java is the name of the class whose main method you would like to run. Copy the file /Network/Servers/cortland.cs.williams.edu/Volumes/Courses/cs136/examples/Hello/Hello.java to your home directory, compile it, and run it.
To create a tar file lab1.tar that contains files Odd.java, Date.Java, Conway.java, and conway.txt, you can use this command:
tar cvf lab1.tar Odd.java Date.java Conway.java conway.txtThe "cvf" are three flags meaning "create" "verbose" and "file". The v tells tar to give you some output describing what files it's operating on, and the f means use a specified filename rather than the default, which is actually a tape device for historical reasons. (Hence the command's name "tape archive"). You can list the contents of a tar file with
tar tvf lab1.tarAnd you can extract the contents of a tar file with
tar xvf lab1.tarBut beware! This will extract the files with no concern for whether it is overwriting files in your directory. For this reason, I recommend creating and changing into a brand new directory when extracting tar files.