3.1 Searching the course notesIndex

The previous term’s course notes are always available on the Internet here: CST8207 GNU/Linux Operating Systems I.

All the current and previous terms notes files are also stored on the CLS. You can learn about how to read and search these files using the command line on the CLS under the heading Copies of the CST8207 course notes near the bottom of the page Course Linux Server. The current CST8177 term notes are searchable there, too!

3.2 The CLS Source DirectoryIndex

All references to the “Source Directory” below are to the CLS directory ~idallen/cst8177/14w/assignment10/ 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 (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.

3.3 Review of CST8207 partitioning and filesystemsIndex

Review your work from CST8207 GNU/Linux Operating Systems I:

• In this assignment you will need to remember how to use: fdisk, mkfs, mount, /etc/fstab
• CST8207 Partitions and File Systems – fdisk, mkfs, mount, swap
• CST8207 Booting and GRUB – how to boot into single user mode.

3.4 Backup and Recovery on CentOSIndex

1. Take a snapshot of your virtual machine before you begin each section of this lab so that you can recover back to the snapshot if needed.
   • You can delete the unused snapshots if everything works well.
   • CentOS snapshots are very small and fast compared to your Windows snapshots; you can save lots of them.
2. Are you keeping an external backup copy of all your coursework (including your virtual machines) somewhere? You should be!

3.5 Use a remote login, not the VMware consoleIndex

I recommend that once you have booted your CentOS VM, you connect to it and work using a remote login session (e.g. ssh or PuTTY) where copy-and-paste works and where you can have multiple simultaneous connections into the VM. The VMware console is not friendly.

If you can’t get an SSH (PuTTY or ssh) connection working into your Linux VM, see the Network Diagnostics page.

Note that SSH sessions (and whatever you are doing inside them) do not survive across a VMware suspend. Make sure you save your editor files and exit your SSH session before you pause or suspend your virtual machine. (Editor sessions that run inside the VMware console do survive across suspend and resume, since they don’t depend on a network connection.)

Advanced users may look into the various virtual terminal programs such as tmux and screen that do allow you to suspend and resume your sessions even from a remote login.

4.1 Set Up – The Base Directory on the CLSIndex

1. Do a Remote Login to the Course Linux Server (CLS) from any existing computer, using the host name appropriate for whether you are on-campus or off-campus.

2. Create the CLS directory ~/CST8177-14W/Assignments/assignment10

3. Create the check symbolic link needed to run the Checking Program, as described in the section Part II - Check and Submit below.

Run Part II - Check and Submit to verify your work so far.

4.2 CentOS: SnapshotIndex

0. Complete your CentOS Virtual Machine Installation and Verification.
   • Make sure it passes the checks for disk sizes and package counts.
   • Complete these critical system administration tasks required in Assignment #08 and Assignment #09:
     1. Create the sudoers group.
     2. Create your own personal sysadmin account.
     3. Install and configure the NTP package.
1. Before you begin this assignment, create a snapshot of your CentOS Virtual Machine.
   • Enter a comment explaining where and when you took this snapshot.
   • You can restore back to this snapshot if anything goes wrong.

4.3 CentOS: Set Up – The Base Directory on CentOSIndex

1. In your own account in your CentOS Virtual Machine, also make the directory ~/CST8177-14W/Assignments/assignment10 (the same hierarchy as you have already made on the CLS).

This CentOS assignment10 directory in your sysadmin account is the base directory for all pathnames in this assignment. Store your CentOS files and answers below in this sysadmin base assignment10 directory.

Run the Fetch and Checking Program to verify your work so far.

4.4 CentOS: Add a second disk to your VM: sdbIndex

You will add a second hard disk to your CentOS Virtual Machine, and partition it. The procedure for adding a hard disk to an actual physical computer is different only in the steps that take place while the machine is powered off. Any step carried out while the machine is running would be the same for physical machines as it is for virtual machines. The console of a physical machine is its actual keyboard and monitor, but in the case of a VM, the console is the VMware window of the machine.

Most of the system admin commands in this assignment access the raw disk and will require you to prefix the actual command name with sudo to gain root permissions (unless you are in single-user mode and therefore running everything as root). If you get “permission denied” errors, you forgot to use sudo.

1. If your CentOS Virtual Machine is not already powered off, login and use the correct command to power off the virtual machine.

   • Never user the VMware Power Off button to kill power!
   • Never unplug a running Linux machine!

2. With your CentOS machine still powered off, use the VMware Settings menu for your CentOS VM to add to your VM a virtual 10GB hard disk, accepting defaults for everything except the size. (You did similar work in CST8207 adding a VMware disk; review the notes.)

3. After adding the new disk, power on your VM, then login as your system administrator user.

   • Recall that you cannot log in as root since the root account password is locked.

4. Ensure the /proc/partitions file contains the second disk you added.

   • Verify that there is a second disk of the correct size:
     • The size of your second drive should be 10485760.
     • Divide: 10485760/1024/1024 to confirm the number of gigabytes.
   • Verify that no partitions are listed for the second disk.
   • If you have any sdb1 or sdb2 or other sdb partitions, this is not a new disk with no partition table. Get help.
   • Note the three-letter device name of the second disk.

5. When the second disk is correct, copy /proc/partitions to file partitions_before.txt in your CentOS sysadmin base directory (6 lines, 20 words). Remember: all files should eventually be moved to under your sysadmin base directory on CentOS for marking.

6. Verify that the three-letter device name for the second disk also exists under the /dev directory. Put a long (ls -l) listing of all names under /dev that start with the first two letters of the new disk name into file sd_all.txt in your base directory.

   • Do not change your current directory.
   • Use the absolute pathnames for the device names.
   • No pipeline or other command is needed.
   • The output should show the absolute paths of two disks, and two partitions in the first disk.
   • Hint

4.5 CentOS: Viewing and Creating Partitions: fdiskIndex

1. First, you must have added a new 10GB hard drive in VMware and rebooted, as described above. Log in to the machine.

2. Run (always with root privileges) fdisk -cul /dev/sdb and make sure you see Disk /dev/sdb: 10.7 GB with no errors and no partitions listed under it.

   $ sudo fdisk -cul /dev/sdb
   Disk /dev/sdb: 10.7 GB, 10737418240 bytes

   If you don’t see 10.7 GB, then shut down, delete the disk, recreate the disk, and reboot until your 10GB disk install works.

Make sure you only change things on this new sdb disk in this section! The sda disk is your Linux ROOT disk; if you damage it you will need to recover back to your snapshot. Make sure you have a snapshot to go back to!

3. In the man page for the fdisk command, locate and make a note of two option letters:

   • The option to “Switch off DOS-compatible mode. (Recommended)”
   • The option to “give sizes in sectors instead of cylinders”

4. Run the command fdiskdevicename, where devicename is the absolute path of the device corresponding to the new disk under /dev. This will start the fdisk program, just as you did in CST8207 Fdisk Command.

   1. As fdisk starts, read the WARNING about DOS-compatible mode.
   2. This is a serious warning. Quit the fdisk program.
   3. Re-run fdisk command, this time inserting the two option letters you found in the man page. (Keep the same device name.)
   4. The WARNING should be gone when you start fdisk with those two options. Always use these two options on CentOS. (Other versions of fdisk use these options as defaults.)
   5. Display the partition table and verify that the disk you are working on is the 10GiBi disk with no partition table.

5. Inside fdisk use the command to display the partition table and verify that the disk you are working on is the 10GiBi disk with no partition table. Use fdisk commands to partition the new disk as follows:

   1. First, make sure the new disk has no partitions configured. If you see partitions, you are using fdisk on the wrong disk. Make sure you use fdisk on the new disk device name!
   2. Create a 500MB primary partition as Partition 1 (notice that one of the options for specifying the last cylinder of a partition is +sizeM where size is the number of megabytes).
   3. Create an extended partition as Partition 2, consuming the rest of the disk.
   4. Create a 400 MB logical partition
   5. Create another logical partition consuming the rest of Partition 2.
   6. Save your changes.
   7. Notice whether fdisk tells you as it quits whether you need to reboot for the new partition table to take effect. Do what it says.

6. Copy the new version of /proc/partitions (showing the new partitions you just created) to partitions_after.txt in your sysadmin base directory.

   • Also note that the new partitions now appear under the /dev directory.

7. Use the diff command to find the differences between the old and new partitions_{before,after}.txt and redirect the results to partitions_diff.txt in your sysadmin base directory.

8. Examine the differences file, and verify that your new partitions are the only differences. You should see four additional lines in the new partition file, corresponding to the four partitions you created:

   6a7,10
   >    8       17     512000 sdb1
   >    8       18          1 sdb2
   >    8       21     409600 sdb5
   >    8       22    9561088 sdb6

   If your numbers differ, perhaps you forgot to use the fdisk options that turn off DOS-compatibility mode and switch to using sectors instead of cylinders. Delete and start over.

4.6 CentOS: Migrate the /home directory to its own filesystemIndex

You will create an ext4 filesystem on the primary partition of the new hard disk. Then, in single user mode, you will migrate the contents of the /home directory to that new filesystem. You will configure the /etc/fstab so that the new filesystem will be automatically mounted on /home, with the option for giving the users disk space quotas.

4.7 CentOS: Add a third disk to your VM and partition itIndex

You will add a third hard disk to your CentOS Virtual Machine, and partition it.

Remember to take snapshots often. You can delete the older snapshots if everything works.

1. Use VMware to add a 2G hard disk to your virtual machine.

   • Follow the same method as you used when you added the second hard disk earlier in this assignment.
   • This will be its third hard disk.

2. Ensure the /proc/partitions file contains the third disk you added.

   • Verify that there is a third disk of the correct size:
     • The size of your third drive should be 2097152.
     • Divide: 2097152/1024/1024 to confirm the number of gigabytes.
   • Verify that no partitions are listed for the third disk.
   • Note the three-letter device name of the third disk.
   • If you don’t see any disk, perhaps you aren’t reading all the words of the method you used when adding the second disk. Follow all the steps.

3. When the third disk is correct, copy /proc/partitions to file partitions_LVM_before.txt in your sysadmin base directory.

4. Verify that the three-letter device name for the third disk also exists under the /dev directory. Repeat the command you used to create sd_all.txt and redirect the new output into file sd_all2.txt (note the digit 2) in your sysadmin base directory. (See above for how you created sd_all.txt.)

5. Partition the third disk as follows:

   1. If you see that WARNING message about DOS compatibility, you forgot to use the correct options. Start over.
   2. First, make sure the disk you are partitioning has no partitions configured. If you see partitions, you are using the wrong disk. Make sure you use the third disk device name!
   3. Create a primary partition as Partition 1 to occupy the whole disk.
   4. Save your changes.
   5. Notice whether it tells you as it quits whether you need to reboot for the new partition table to take effect. Do what it says.

6. Copy the new version of /proc/partitions (showing the new partition you just created) to partitions_LVM_after.txt in your sysadmin base directory.

   • Also note that the new partition now appears under the /dev directory.

7. Use the diff command to find the differences between the old and new partitions_LVM_{before,after}.txt and redirect the results to partitions_LVM_diff.txt in your sysadmin base directory.

8. Examine the differences file, and verify that your new partition is the only difference. You should see only one additional line in the new partition file, corresponding to the single partition you created:

   11a12
   >    8       33    2096128 sdc1

   If your numbers differ, perhaps you forgot to use the fdisk options that turn off DOS-compatibility mode and switch to using sectors instead of cylinders. Delete and start over.

4.8 CentOS: Practice with LVM and grow a filesystemIndex

You will use LVM capabilities and disk partitions to create the volume group VolGroup00 and the logical volume LogVol00 with an ext4 filesystem. Then you will extend VolGroup00 using the first logical partition on the first disk you added (the 400MB logical partition). Then you’ll grow the LogVol00 logical volume, and then you’ll grow the filesystem that resides on that volume. Each step of the way, you’ll record the state before, then after, and record the difference.

4.9 CentOS: Practice with rsyncIndex

The rsync command is an intelligent form of copy command that only transfers data if the data isn’t already there. You will practice using rsync between your CentOS VM and its loop-back network adapter, which we will call the Backup machine (even though it’s really the same machine). A trivial change to the remote host name lets you transfer files to any machine on the Internet that lets you run rsync.

The modern rsync command uses an underlying SSH protocol to actually transfer the data, so any configuration you have done for SSH (such as private keys, host aliases, or SSH agents) applies to rsync as well.

$ date >foo
$ rsync -avH foo backup@localhost:
$ rsync -avH foo abcd0001@cst8177.idallen.ca:

4.10 CentOS: Boot into single user modeIndex

If you find yourself locked out of a Linux machine, and you have access to the console, booting into single user mode will will often not require a password, and in single-user mode you can change passwords or perform various other repair tasks. (Some systems do password-protect single-user mode, in which case you would need to boot a “live” or “rescue” CD to reset your root password.)

1. Use the correct command to reboot your CentOS VM, and when you see the GNU GRUB menu and the countdown timer, halt the GRUB countdown by pressing the space bar or an arrow key.

2. Use GRUB to edit your boot options so you boot into single user mode. (Refer to last term’s CST8207 Booting and GRUB.)

3. Verify that you are in single user mode: when you issue the command runlevel, the output should be either N S or unknown

4. Note that you are running as root and can change the password of any user in single-user mode, including the root password.

5. Put the output of the command ps auxww into a file named ps_auxww.txt in your sysadmin base directory, and change the ownership and group of this file to your ordinary sysadmin user. (Don’t leave root-owned files in ordinary user accounts!)

6. Exit this single-user shell, which will allow the system to boot into the default runlevel.

7. Log in (using SSH if possible) and verify you’re in the default runlevel by issuing the runlevel command.

   • You should see: S 3

Run the Fetch and Checking Program to verify your work so far.

4.11 CentOS: Boot into rescue modeIndex

If you find a Linux machine is unbootable, and you have console access, you may be able to rescue it by booting the machine from a “Live CD”. You will use the CentOS installation DVD to boot into “rescue” mode, which is a “Live CD” mode.

1. Shut down or power down your CentOS VM gracefully using the proper command.

2. Attach the CentOS Installation ISO image file to your VMware virtual DVD drive, connect it, and make sure it will be connected at Power On. (You did exactly this when you first installed CentOS.)

3. Access the VMware Settings for your Virtual Machine and increase the RAM to at least 1024MB. (The installer and Rescue mode needs more RAM for the graphics than the server-style CentOS machine.)

4. Boot into the VMware BIOS of your virtual machine, as follows:

   1. On VMware Workstation 7.x and later, to enter the BIOS setup for the guest operating system, click VM > Power > Power On to BIOS
   2. On VMware Fusion, or an earlier version of VMware Workstation:
      • Shut down the virtual machine
      • Take a backup of the *.vmx file
      • Add this line to the end of the *.vmx file to give a longer pause on the VMware BIOS screen: bios.bootDelay = "60000"
      • Reboot your virtual machine and you should have 60 seconds to use the correct key to enter the VMware BIOS menu.

5. In the VMware BIOS menu, use the keyboard to change the “Boot” settings so that the CD/DVD drive is before the hard disk in the boot order, if it isn’t already.

6. Save and Exit the VMware BIOS to boot from the virtual CD/DVD drive that contains the CentOS installation ISO image file.

   • If you boot into your regular CentOS, then you didn’t set up either the Boot menu or the CD/DVD device correctly. Wait until the machine has finished booting, log in, shut it down and try again.

7. If the ISO image boots, you will see the blue CentOS Welcome boot screen below with the large CentOS-6 banner on the screen. The Welcome menu includes the item Rescue installed system. Use the arrow keys to select the Rescue line and boot it by pressing Enter:

8. Follow the instructions on the screen, choosing the defaults, to finish booting into rescue mode, allowing it to search for and mount your Linux system when it asks you:

   • You do not need to enable networking – choose No
   • Make note of the directory under /mnt that will be used to mount and access your Linux installation.
   • Use Continue and not Read-Only for your Linux installation, since we need to write on the file system.
   • If it fails to find and mount your Linux installation, you will have to find it and do it manually. See your instructor.

9. At the three-item menu that starts with shell Start shell, choose the first item (start a shell).

10. When you finally have a bash root prompt, cat the password file to see that this is not your own CentOS system running. It is the Rescue system, with its own Rescue password file.

    • If you see your CentOS password file, you didn’t boot from the Rescue CD. Shut down and try again.

11. Running df will confirm that your CentOS ROOT partition /dev/sda1 is mounted on directory /mnt/sysimage and your CentOS HOME partition /dev/sdb1 is mounted on directory /mnt/sysimage/home

12. Run ls -l on all the HOME directories and note that they all have numeric owners and groups.

    • Exam question: Why are all these HOME directories showing as numbers instead of userids when viewed from the Rescue CD?

13. Save a copy of the LiveCD’s password file, preserving timestamps, permissions, etc., to the file livecd_passwd.txt in your sysadmin base directory in your mounted CentOS system.

    • Use the correct path to your sysadmin base directory on its current mount point. (The correct path to your sysadmin base directory is NOT under /home when mounted on the Rescue CD! Read all the words above.)
    • The sum of your livecd_passwd.txt file should be 63933 2

14. The owner and group of the livecd_passwd.txt file you just created is currently root. Try (and fail) to change the file to be owned by your CentOS system admin account.

    • It will say your userid doesn’t exist: chown: invalid user: 'abcd0001'
    • Exam question: Why did the chown fail when run from the Rescue CD? Why is your userid invalid (doesn’t exist)?

15. Run the command chroot /mnt/sysimage to obtain a root shell running with that directory (your CentOS ROOT) as its ROOT directory. As long as you remain in the chroot shell, this directory will be ROOT.

    Now when you cat the password file, you will see the password file relative to the new chroot ROOT directory, which is your CentOS ROOT directory, so you see your CentOS password file, not the LiveCD password file.

    • If you don’t see your own CentOS password file, get help.
    • All programs you run from this chroot shell will behave as if they used your CentOS file system as the ROOT.
    • You could fix a broken MBR with the command grub-install at this point, or do any other repairs to your CentOS Linux file system.

16. In the chroot shell you are running, confirm that you can now see your livecd_passwd.txt file in your CentOS sysadmin base directory using its usual path with respect to the usual ROOT directory:

    # cd /home/abcd0001/CST8177-14W/Assignments/assignment10
    # ls -l livecd_passwd.txt

    Note that the file is still owned by root.

17. Change the owner and group of the livecd_passwd.txt file to your system admin account. It will succeed this time.

    • Exam question: Why did the chown succeed in the chroot shell but fail before using chroot?

18. Exit the chroot shell back to the Rescue CD shell prompt.

19. At the Rescue CD shell prompt, use a command to shut down the machine.

    • Wait until the machine is powered off.

20. With the machine powered off:

    1. Go to the VMware VM Settings, Hardware CD/DVD tab, under Device Status, and un-check Connect at power on.
    2. On the same screen, take the ISO file out of the virtual CD/DVD drive by switching the Connection back to Use a physical drive.
    3. Save the settings so that you do NOT boot again from the Rescue ISO image file.
    4. Go to the Hardware Memory settings and reduce the memory back to 256MB.
    5. Save the settings.

21. Power on your CentOS VM. You should see a familiar GNU GRUB menu.

    • If you end up booting the CD/DVD again, use the VMware menu to disconnect it. Reboot or choose Boot from local drive.

22. When your CentOS has rebooted, log back in as your system admin account (using SSH if possible, since it’s nicer than the console).

23. Change the ownership and group (to you) of any remaining root owner or group files anywhere in your system admin account. (If you’ve done your work carefully, there should be nothing owned by root.)

    • System administrators often scan home directories, looking for root-owned files as an indication that someone has broken into the system. Don’t leave root-owned files in your own CentOS sysadmin account.
    • NOTE: The Checking Program does create root files in your CLS assignment directories. This is intentional: don’t delete these!

Run the Fetch and Checking Program to verify your work so far.

4.12 When you are All DoneIndex

That is all the tasks you need to do.

Check your work a final time using the Fetch and Checking Program and save the output as described below. Submit your mark following the directions below.

Optional: Keeping your main CentOS Virtual Machine snapshot, remove any intermediate snapshots you no longer require, to free up disk space. - Be careful not to remove your current work!

5.1 Part I - Fetch and CheckIndex

Do all the following steps on your CentOS Virtual Machine. Read through the whole list before you start typing anything. An example of what to type is given below the descriptions that follow.

Failure to read all the words will lock your account out of the CLS.

1. Log in to CentOS. Use your sysadmin non-root account (same userid as Blackboard).
2. Create a directory in your sysadmin account named CST8177-14W/Assignments/assignment10 (use the same directory hierarchy as you already have in your own account on the CLS). This is your base directory for this assignment.
3. Change to the above sysadmin base directory (on CentOS!).
4. As shown below, use curl to get a copy of the Fetch program from the given URL into a file named do.sh. Make sure you have a file named do.sh in your sysadmin base directory. You only need to download this once per assignment.
5. Warning: If you printed this page on paper, you may not be able to scroll right to read the whole web URL that you must pass to the curl program.

$ whoami ; hostname ; pwd
abcd0001                                 # your userid, not abcd0001
abcd0001                                 # your userid, not abcd0001
/home/abcd0001/CST8177-14W/Assignments/assignment10
$ url=http://teaching.idallen.com/cst8177/14w/notes/data/assignment10do.sh
$ curl -A mozilla "$url" >do.sh
[... make sure you scroll right to read the full web URL above ...]
[... various download statistics print here ...]

$ fgrep -i 'error' do.sh                 # make sure no errors (no output)
$ head -n1 do.sh                         # make sure it's a shell script
#!/bin/sh -u

5. You must run the do.sh script you just downloaded. You must run the script as the root user with the USER environment variable set to your own CLS account userid. (Do not use abcd0001; use your own.) Failure to set the USER= variable as shown below will cause your account to be locked out of the CLS.

   As shown below, use sudo and sh to run the do.sh script you just downloaded to CentOS with the USER environment variable set to your own CLS account userid (as stored in the USER variable).

   $ echo "$USER" ; pwd
   abcd0001                                 # your userid, not abcd0001
   /home/abcd0001/CST8177-14W/Assignments/assignment10
   $ sudo USER=$USER sh do.sh

   This do.sh script runs a Fetch program that will connect from your CentOS machine to the CLS using your account name in the USER variable. It will copy selected files from your CentOS machine to your assignment10 directory on the CLS. It will then run the checking program on the CLS to check your work. You will need to answer one question about your IP address, and then wait and type in your CLS password, as shown below:

   ---------------------------------------------------------------------------
   abcd0001: FETCH version 3.  Connecting to CLS as USER='abcd0001' using ssh
   ---------------------------------------------------------------------------
   abcd0001: Use local Algonquin IP cst8177-alg.idallen.ca [y/N/?]? n
   abcd0001: Please wait; using ssh to connect to user 'abcd0001' on cst8177.idallen.ca ...
   *** COURSE LINUX SERVER ***
   abcd0001@cst8177.idallen.ca's password:         # enter your CLS password
   ---------------------------------------------------------------------------
   idallen-ubuntu assignment10fetch_server.sh version 8 run by abcd0001.
   Please wait; collecting info from abcd0001 Virtual Machine
   ---------------------------------------------------------------------------
   VM files collected into CST8177-14W/Assignments/assignment10/abcd0001.tar.bz on CLS.
   Now running checking program for abcd0001 on CLS:
   [... checking program output appears here ...]

5.2 Part II - Check and SubmitIndex

When you are done with your assignment, you need to run the checking program one last time on the CLS (not from CentOS) and submit the output file, as follows:

Do all this on the Course Linux Server when you are ready to submit:

1. There is a Checking Program named assignment10check in the Source Directory on the CLS. Create a Symbolic Link to this program named check under your new assignment10 directory on the CLS so that you can easily run the program to check your work and assign your work a mark on the CLS. Note: You can create a symbolic link to this executable program but you do not have permission to read or copy the program file.

2. Execute the above “check” program on the CLS using its symbolic link. (Review the Search Path notes if you forget how to run a program by pathname from the command line.) This program will check your fetched CentOS 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.)

   Remember: The checking program does not fetch new files to the CLS from your CentOS VM. You must run the Fetch program on your CentOS VM to update the fetched files on the CLS so that the checking program can mark them on the CLS.

   You may run the “check” program as many times as you wish, to correct mistakes and get the best mark. Some task 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.

3. 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 assignment10.txt under your assignment10 directory on the CLS. Use the exact name assignment10.txt in your assignment10 directory. Case (upper/lower case letters) matters. Be absolutely accurate, as if your marks depended on it. Do not edit the file.

   • Make sure the file actually contains the output of the checking program!
   • The last text line of the file should begin with: YOUR MARK for
   • Really! MAKE SURE THE FILE HAS YOUR MARKS IN IT!

4. Transfer the above assignment10.txt file from the CLS to your local computer and verify that the file still contains all the output from the checking program. 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.

   • Make sure the file actually contains the output of the checking program!
   • The last text line of the file should begin with: YOUR MARK for
   • Really! MAKE SURE THE FILE HAS YOUR MARKS IN IT!

5. Upload the assignment10.txt file under the correct Assignment area on Blackboard (with the exact correct name) before the due date. Upload the file via the assignment10 “Upload Assignment” facility in Blackboard: click on the underlined assignment10 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 need to comment on any assignment submission, send me email.

   You can upload the file more than once; I only look at the most recent. You must upload the file with the correct name; you cannot correct the name as you upload it to Blackboard.

6. Verify that Blackboard has received your submission: After using the Submit button, you will see a page titled Review Submission History that will show all your submissions.

   1. Verify that your latest submission has the correct 16-character, lower-case file name beside the Attached Files heading.
   2. The Submission Field and Student Comments headings must be empty. (I do not read them.)
   3. Save a screen capture showing the uploaded file name. If there is an upload missing, you will need this to prove that you uploaded the file. (Blackboard has never lost a file.)

   You will also see the Review Submission History page any time you already have an assignment attempt uploaded and you click on the underlined assignment10 link.

   You cannot delete an assignment attempt, but you can always upload a new version. I only mark the latest version.

7. 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!