Study chapter 1 immediately, with attention to the skills needed for the exercises. Also begin working through chapter 2 as soon as possible.

Submit your solutions to the following problems, most of which are specific exercises from the end of chapter 1, by 1:00 PM, Saturday, 03 April 2010. You may hand in your work at Science Hall 131, if it is open, or at the faculty mailboxes in Briggs Hall.

1. Exercise 1–1 (the quality of the writing counts!)
2. Exercise 1–6
3. Exercise 1–8
4. Exercise 1–10
5. Exercise 1–11
6. Exercise 1–12

For work of this sort, some indication of method (not just final result) is appropriate.

As soon as possible, access your account on an Itanium workstation or server in order to become familiar with the HP-UX and/or Linux command line environment(s). Conduct the following explorations:

1. With an ftp or sftp access client, as required by the host system, be sure that you can upload a brief simple text file to the host system.
2. Make temporary notes of the files that already appear in your directory on the host system.
3. With a suitable telnet or secure shell access client, as required by the host system, establish a remote interactive connection to the host system.
   1. Use the command ls -l to produce a listing of the files in your top-level directory. How does this differ from what you saw in the file transfer client window?
   2. Use the command cat file to display the text file that you uploaded (where file is its name).
   3. Use the command rm file to delete the text file.
   4. Use the command printenv to find out which “shell” (command interpreter) is currently in effect for your account.
   5. On some systems, you can use the command chsh -l to see a list of available shell choices, but this command varies drastically among Linux and Unix systems in its behavior. Seek assistance if you think that you would prefer a different shell, a different shell prompt, etc. [Caution: On a BSD-derived system such as Mac OS X the chsh command displays current information by invoking the vi editor; to exit from vi without making any change, type :q! and press the enter key.]
   6. With some Unix and Linux shells, you can log out using the command logout, but others will only accept exit. More generally, if neither of these seem to work, nearly all Unix-like systems recognize CTRL/D as a command to terminate an interactive session.
4. Seek help if there appears to be a problem with your account.

Read Appendix A for background information about command-line environments.