Updated: 2017-01-20 00:52 EST
Do not print this assignment on paper!
- On paper, you will miss updates, corrections, and hints added to the online version.
- On paper, you cannot follow any of the hyperlink URLs that lead you to hints and course notes relevant to answering a question.
- On paper, scrolling text boxes will be cut off and not print properly.
08h00 (8am) Monday September 19, 2016 (start of Week 3)
Do not print this assignment on paper! On paper, you cannot follow any of the hyperlink URLs that lead you to hints and course notes relevant to answering a question.
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 how you are expected to complete this assignment. Read all the words before you start working.
For full marks, follow these directions exactly.
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 task 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 the files and directories in place on the CLS as part of your deliverables. Do not delete any assignment work 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.
Since I also do manual marking of student assignments, your final mark may not be the same as the mark submitted using the current version of the Checking Program. I do not guarantee that any version of the Checking Program will find all the errors in your work. Complete your assignments according to the specifications, not according to the incomplete set of the mistakes detected by the Checking Program.
All references to the Source Directory below are to the CLS directory ~idallen/cst8207/16f/assignment02/
and that name starts with a tilde character ~
followed by a user name with no intervening slash. The leading tilde indicates to the shell that the pathname starts with the HOME directory of the account idallen
(seven letters).
You do not have permission to list the names of all the files in the Source Directory, but you can access any files whose names you already know.
See Remote Login for the background you need to read the document Course Linux Server.
Your instructor will demonstrate logging in to the Course Linux Server and the commands below and File Transfer in your lab periods in the first two weeks of school. Attend any lab period for assistance.
Keep notes for every command name used in this course, giving its name, an explanation of what it does, and a short example. Quizzes and tests will require you to remember these command names.
PuTTY
on Windows and Terminal
with ssh
on Mac OSX).
The CLS is on the public Internet; security is important. Choose your password carefully, or else Internet attackers will break into the CLS through your account. Don’t let this happen!
Read on Wikipedia: Guidelines for strong passwords
Read this XKCD comic on good passwords
Now RTFM in the Manual for the Linux command named passwd
(note the odd spelling). No arguments or options are needed to this command to change your own password.
Change your CLS 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.
Accounts that do not have their passwords changed before the due date of this assignment will be disabled.
This task shows you some simple Linux command lines that were introduced in class and lab. It also demonstrates file output redirection using the >
character, where you can save the output of a Linux command line in a file instead of having the output display on your screen.
All of these Linux command names have manual pages – man
pages – and you can read the manual page for a command by using the man
command followed by the name of the command, e.g. man date
or man users
As you did in class, try each of the Linux command lines below at the bash
shell prompt on the CLS. Do not type the leading dollar ($
) prompt character. Only type the command name and any arguments to the command, separated by spaces as you see below.
$
) after you enter a command and push Enter
, try typing ^C
(CTRL-C
– hold down the Ctrl
key and type the letter C
at the same time) to interrupt the command and get the bash
dollar prompt back. This is described in Interrupting Programs with ^C
.$ date
$ users
$ who
$ echo Hello World
$ cal 9 1752
$ figlet Hello World
$ toilet Hello World
$ history
cal
with the year or month and year you were born, e.g. cal 1954
or cal 7 1954
sl
and cmatrix -s
date.txt
on the CLS as follows: Use shell file Output Redirection to save the output of the date
command into an output file by adding to the right end of the command line a space, the right angle-bracket redirection character >
, and then an output file named date.txt
on the command line, like this:
$ date >date.txt
Note the space between the command name and the added redirection syntax. You can add redirection syntax to most any Unix/Linux command line.
ls
shows the names of files in your account, and it should show you the name of the date.txt
file you just created. You can use the -l
option (it’s a letter, not a digit) to get more information about files, like this:
$ ls
$ ls -l
$ ls -l date.txt
Use the above three command lines and note how the output differs.
file
command tells you what type of file it is (text):
$ file date.txt
Use the above command line to show the type of the date.txt
file.
cat
displays the contents of a file on your screen:
$ cat date.txt
Use the above command line to display on your screen the contents of the date.txt
file you created earlier using Output Redirection. (If you get an error No such file or directory, check your spelling.)
We can repeat the same sequence of commands with most any Unix/Linux command. We could redirect the output of the echo
command into a file named foo
, show the properties of the file, and then show the contents of the file:
$ echo Hello World
Hello World # output appears on your screen
$ echo Hello World >foo # output goes into the file foo
$ ls -l foo # use ls command to show information
-rw-rw-r-- 1 abcd0001 abcd0001 12 Jan 15 05:12 foo
$ file foo # use file command to show type
foo: ASCII text
$ cat foo # display file contents on screen
Hello World
Using the left angle-bracket >
followed by a file name allows you to redirect or save the output of almost any Linux command into any file name. This is called Output Redirection. We will cover redirection in more detail later in the course.
Re-do all of the simple Linux commands that you used at the start of this task, exactly as you used each above, with the same command arguments, redirecting the output of each of the commands into a file that is the name of the command with a .txt
extension added. Use the same command arguments as given above. View the file contents after each command. It will look like this:
$ date >date.txt
$ cat date.txt
$ echo Hello World >echo.txt
$ cat echo.txt
Repeat for all of the commands used at the start of this task. The output file name uses the name of the command (not including any arguments to the command). Leave these output files (corresponding to the command names) in your account on the CLS.
The syntax and format of each command line is described in Typing Command Lines and Basic Command Line Syntax. Read those pages to know how to distinguish a command name from command arguments. Your output file names must use only the command name not the command arguments.
Run the Checking Program to verify your work so far.
Your instructor will walk you through the following File Transfer task this week. Come to any lab period for assistance in making this work for you.
Do a practice File Transfer, fetching from the CLS to your local machine (e.g. to your local Windows or OSX laptop), like this:
First, make sure you have a file cal.txt
on the Linux CLS containing some calendar output. You can create this file using file output redirection, as you did above. Use ls
to see the file name and cat
to see the content of the cal.txt
file, as you did above. Make sure the file is not empty!
cal.txt
file from the Linux CLS to your local machine using the instructions in the page File Transfer.
WinSCP
or Filezilla
program for Windows and use a Terminal
with the scp
command for Mac OSX.cal.txt
file from the CLS to your local machine, open the transferred file on your local machine.
You must know how to redirect program output into a file and transfer that file from the CLS to your local machine to be able to submit the output of the Checking Program for marking.
man
commandIndexYou need to know RTFM in the Manual to do this task, especially the section on Reading manual pages SYNOPSIS Line(s).
Your instructor may ask you in the lab about the answers to the five questions in the above RTFM page relating to the SYNOPSIS section of a manual page. Be ready with any of the five answers, and show that you know how to search for text inside the less
program.
That is all the tasks you need to do.
Check your work a final time using the Checking Program below and save the standard output of that program into a file as described below. Submit that file (and only that one file) to Blackboard following the directions below.
When you are done, log out of the CLS before you close your laptop or close the PuTTY window, by using the shell exit
command:
$ exit
Nothing seriously bad will happen if you forget to log out, but you may leave behind an empty, “ghost” login session that may take some days to time out and disappear. Always exit
before you close your laptop, PuTTY, or Terminal session.
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 single file that is the output of the Checking Program to Blackboard.
Since I also do manual marking of student assignments, your final mark may not be the same as the mark submitted using the current version of the Checking Program. I do not guarantee that any version of the Checking Program will find all the errors in your work. Complete your assignments according to the specifications, not according to the incomplete set of the mistakes detected by the Checking Program.
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 as a command name:
$ ~idallen/cst8207/16f/assignment02/assignment02check
Note the leading tilde ~
character on the command name. You will learn of ways to make this long line shorter in future assignments.
Execute the above Checking Program as a command line on the CLS. This program will check your work, assign you a mark, and display the output on your screen.
You may run the Checking Program as many times as you wish, allowing you to correct mistakes and get the best mark.
When you are done with this assignment, and you like the mark displayed on your screen by the Checking Program, you must redirect only the standard output of the Checking Program into the text file assignment02.txt
on the CLS, like this:
$ ~idallen/cst8207/16f/assignment02/assignment02check >assignment02.txt
$ less assignment02.txt
assignment02.txt
file name.YOUR MARK for
assignment02.txt
(containing the output from the Checking Program) from the CLS to your local computer.
YOUR MARK for
assignment02.txt
file from your local computer to the correct Assignment area on Blackboard (with the exact name) before the due date:
assignment02.txt
file from your local computer. Make sure the assignment file has the correct name on your local computer before you attach it. Attach only your assignment02.txt
file for upload. Do not attach any other file names.assignment02.txt
file on the Upload Assignment page, scroll down to the bottom of the page and use the Submit button to actually upload your attached assignment02.txt
file to Blackboard.Use only Attach File on the Upload Assignment page. Do not enter any text into the Text Submission or Comments boxes on Blackboard; I do not read them. Use only the Attach File section followed by the Submit button. If you need to comment on any assignment submission, send me EMail.
You can revise and upload the file more than once using the Start New button on the Review Submission History page to open a new Upload Assignment page. I only look at the most recent submission.
You must upload the file with the correct name from your local computer; you cannot correct the name as you upload it to Blackboard.
assignment02.txt
under the SUBMISSION heading.You will also see the Review Submission History page any time you already have an assignment attempt uploaded and you click on the underlined assignment02 link. You can use the Start New button on this page to re-upload your assignment as many times as you like.
You cannot delete an assignment attempt, but you can always upload a new version. I only mark the latest version.
Your instructor may also mark files in your 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!
I do not accept any assignment submissions by EMail. Use only the Blackboard Attach File. No word processor documents. Plain Text only.
Use the exact file name given above. Upload only one single file of Linux-format plain text, not HTML, not RTF, not MSWord. No fonts, no word-processing. Linux plain text only.
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 16-character, lower-case 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!