Updated: 2013-05-08 21:04 EDT
11h00 (11am) Monday February 4, 2013 (start of Week 5)
WARNING: Some inattentive students upload Assignment #2 into the Assignment #1 upload area. Don’t make that mistake! Be exact.
This assignment is based on your weekly Class Notes.
less
pagination program.Remember to READ ALL THE WORDS to work effectively and not waste time.
This is an overview of what you will do in this assignment. Read all the words before you start working.
In Week 2 you had a lab on how to log in to the CLS and transfer files. That preparation work is outlined, below.
Complete the numbered Tasks listed below on the Course Linux Server (CLS). Run a Checking Program to verify your work as you finish each task. Submit your marks to Blackboard.
You will create file system structure in your CLS home directory containing various directories and files. You can use the Checking Program to check your work as you do the tasks. You can check your work with the checking program as often as you like before you submit your final mark. (Some tasks sections below require you to finish the whole section before running the checking program; you may not always be able to run the checking program successfully after every single task step.)
When you are finished the tasks, leave these files, directories, and links in place on the CLS as part of your deliverables. Do not delete any assignment work from the CLS until after the term is over! Assignments may be re-marked at any time on the CLS; you must have your term work available on the CLS right until term end.
In Week 2, you did the following practice in your lab period, in preparation for the assignment:
PuTTY
on Windows).
PuTTY
for Windows.$ date
$ who
$ ls
$ ls -la
$ figlet Hello World
$ toilet Hello World
$ toilet --gay Hello World
$ cal 9 1752
cal
with the year your were born, e.g. cal 1954
>
and then display the contents of the file:
$ cal 9 1752
$ cal 9 1752 >cal.txt
$ cat cal.txt
Filezilla
for Windows.file.txt
on Windows using Notepadfile.txt
file to Linux$ ls
$ ls -l
$ cat file.txt
$ file file.txt
cal.txt
on Linux using output redirection:
$ cal 9 1752
$ cal 9 1752 >cal.txt
$ cat cal.txt
$ file cal.txt
cal.txt
file to WindowsDo all this work logged in to your account on the CLS.
Do the following numbered tasks in order, from top to bottom. READ ALL THE WORDS! and do not skip steps.
Your instructor will mark on the due date the work you do in your account on the CLS. Leave all your work on the CLS and do not modify it. Do not delete any assignment work from the CLS until after the course is over.
All references to the “Source Directory” below are to the directory
~idallen/cst8207/13w/assignment02/
and that name starts with a tilde character “~
” followed by a userid with no intervening slash. The leading tilde indicates to the shell that the pathname starts with the HOME directory of the account idallen
.
This worksheet prepares you to do the numbered tasks listed below by executing commands while logged in remotely to the Course Linux Server.
You can download Libre Office (or Open Office) for Windows to edit the Worksheet *.odt
files and save your answers. (Or you can print the PDF and write your answers on paper.) Save your answers for quizzes!
[abcd0001@idallen-ubuntu ~]$
Set your prompt every time you log in to the CLS, so that the prompt changes to tell you you the basename of your current working directory. This is faster than typing pwd
all the time!
The CLS is on the public Internet; security is important. Choose your password carefully. Accounts that do not have their passwords changed before the due date of this assignment will be disabled.
Read “Guidelines for strong passwords” in http://en.wikipedia.org/wiki/Password_strength#Guidelines_for_strong_passwords
Now read this XKCD comic: http://xkcd.com/936/
Now RTFM for the Unix command named “passwd
” (note the spelling). No arguments or options are needed to change your own password. The passwd
command is also described in Lab Worksheet #02 HTML.
Change your password to one that is more secure than the one you were given. Find a way to remember your new password. If you forget your password, contact your Linux instructor to have it reset.
Create the following directory structure in your CLS HOME directory and record (for study purposes) the series of Unix commands you used to create it. Spelling and capitalization must be exactly as shown:
CST8207-13W/
`-- Assignments
`-- assignment02
`-- tree
|-- one
| `-- oneone
`-- two
`-- twotwo
CST8207-13W
” directory is created in your CLS HOME directory.
Assignments
” directory is created in the CST8207-13W
directory.
assignment02
” directory is created in the Assignments
directory.
tree
” directory is created in the assignment02
directory.
tree
are two new directories named “one
” and “two
”.
one
is new directory “oneone
”.two
is new directory “twotwo
”.You can check your work by making your HOME directory your current directory and using one of these commands below. Use the command that gives the best-looking output:
$ tree CST8207-13W
$ tree -A CST8207-13W
The correct output will be similar to the ASCII tree diagram above. The spelling and capitalization must be exactly as shown.
Note: You can create the entire directory tree above using one single command with one option and two pathname arguments. System administrators like to work efficiently - they learn how to do things quickly.
Make the assignment02
directory your current directory and then use a command to recursively generate a list of all pathnames under your tree
directory. (You used this command this at the end of Lab Worksheet #02 HTML). The recursive output of all pathnames under your tree
directory will be exactly five lines long and will contain this exact line in the output somewhere (along with another four lines):
tree/one/oneone
Recall that you can redirect any output that appears on your screen into a file by adding to the end of the command line a “greater than” angle bracket followed by a file name. (We did this using the cal
command to create the cal.txt
file in the Week 2 labs and you can see an example of this up above in the Practice section.)
When the recursive output above on your screen looks correct, redirect the output of the command into the file named “paths.txt
” in the oneone
directory that you created earlier. (Use a relative path down to the oneone
directory, as shown in the Week 3 lectures.)
Make the oneone
directory your current directory. Use a command to list the files in the current directory to confirm that the paths.txt
file is here. Use another command to display the contents of the paths.txt
file, and make sure it contains at least five lines of pathnames.
Copy the paths.txt
file (from the current oneone
directory) into the twotwo
directory that you created earlier, giving it the new name “paths.txt.copy
” as you copy it. Again, use relative paths to do the copy, as shown in the Week 3 lectures. (Hint: Draw a file system hierarchy picture to help you derive the correct relative pathname.)
Run the Checking Program to verify your work so far.
Execute this exact command line in your account on the CLS:
$ ~idallen/cst8207/13w/assignment02/create
There is a leading tilde character “~
” directly in front of the account name “idallen
”, indicating to the shell that the pathname starts with the HOME directory of idallen
.
The command will create a directory named “stuff
” in your assignment02
directory. It will contain some sub-directories and files.
You can re-execute the above line to start over from scratch, if you make errors in this part of the assignment.
To know what files and directories have been created by the above command line, use a command that will recursively show all the files and directories under a starting directory. (You already used this command, above.)
All the following commands in this section apply to files and directories under the new stuff
directory. You will have to use commands to find some of the file names mentioned here; they may be located under sub-directories. (See Searching and Finding Files.) Some of these tasks may require more than one command to complete.
Find and read the file named “README.txt
” (somewhere under stuff
).
Read and then delete the file “foo.txt
” that is in the same directory as “README.txt
”. (Do not delete any other decoy files named “foo.txt
” that may be in different directories.)
Move (rename) the file “dst
” to be “dst.bak
”. (This is a move, not a copy. It renames the file.)
Directly under the new “stuff
” directory, create a new empty directory named “dst
”. (Make sure you create “dst
” under stuff
, not in your HOME or any other directory.)
Find the file named “services
” (not the directory with the same name) and move (rename) that “services
” file to be named “ports
” under the new directory “dst
” that you just created. (This is a move/rename, not a copy.) Make sure you move the file, not the directory with the same name.
Run the Checking Program to verify your work so far.
Under the Source Directory there is a directory named “maze
”. This maze contains many hidden sub-directories. (You need a special option to see hidden files and directories.) In this maze, use a single command to recursively find the file with a 12-character basename that looks similar to “abcd0001.txt
” but where the eight-character “abcd0001
” part of the name is replaced by your own account userid. You must use a single command that finds files by basename to find this 12-character file name. Do not try to use “cd
” and “ls
” to find the file in the maze; the maze is very big.
When you have found your personal “abcd0001.txt
” file in the maze, copy your file into the “dst
” directory you created above, using the new name “me.txt
” under “dst
”. Read the file to make sure it’s the right one after you copy it into “dst
”.
Run the Checking Program to verify your work so far.
That is all the tasks you need to do. Next, mark your work:
Summary: Do some tasks, then run the checking program to verify your work as you go. You can run the checking program as often as you want. When you have the best mark, upload the marks file to Blackboard.
There is a Checking Program named assignment02check
in the Source Directory on the CLS. You can execute this program by typing its (long) pathname into the shell:
$ ~idallen/cst8207/13w/assignment02/assignment02check
Execute the above “check” program. This program will check your work, assign you a mark, and display the output on your screen. (You may want to paginate the long output so you can read all of it.)
You may run the “check” program as many times as you wish, to correct mistakes and get the best mark. Some tasks sections require you to finish the whole section before running the checking program at the end; you may not always be able to run the checking program successfully after every single task step.
When you are done with checking this assignment, and you like what you see on your screen, redirect the output of the Checking Program into the text file assignment02.txt
under your assignment02
directory. Use the exact name assignment02.txt
in your assignment02
directory. You only get one chance to get the name correct. Case (upper/lower case letters) matters. Be absolutely accurate, as if your marks depended on it. Do not edit the file.
Transfer the above assignment02.txt
file from the CLS to your local computer and verify its contents. Do not edit this file! No empty files, please! Edited or damaged files will not be marked. You may want to refer to your File Transfer notes.
Submit the assignment02.txt
file under the correct Assignment area on Blackboard (with the exact name) before the due date. Upload the file via the assignment02 “Upload Assignment” facility in Blackboard: click on the underlined assignment02 link in Blackboard. Use “Attach File” and “Submit” to upload your plain text file.
No word-processor documents. Do not send email. Use only “Attach File”. Do not enter any text into the Submission or Comments boxes on Blackboard; I do not read them. Use only the “Attach File” section followed by the Submit button. (If you want to send me comments about your assignment, use email.)
Your instructor may also mark the assignment02
directory in your CLS account after the due date. Leave everything there on the CLS. Do not delete any assignment work from the CLS until after the term is over!
Use the exact file name given above. Upload only one single file of plain text, not HTML, not MSWord. No fonts, no word-processing. Plain text only.
Did I mention that the format is plain text (suitable for VIM/Nano/Pico/Gedit or Notepad)?
NO EMAIL, WORD PROCESSOR, PDF, RTF, or HTML DOCUMENTS ACCEPTED.
No marks are awarded for submitting under the wrong assignment number or for using the wrong file name. Use the exact name given above.
WARNING: Some inattentive students don’t read all these words. Don’t make that mistake! Be exact.
READ ALL THE WORDS. OH PLEASE, PLEASE, PLEASE READ ALL THE WORDS!