715
edits
Changes
Created page with "= LAB PREPARATION = {| width="40%" align="right" cellpadding="10" |- valign="top" | Image:package.png|thumb|right|200px|Learning how to conserve disk space is essential for..."
= LAB PREPARATION =
{| width="40%" align="right" cellpadding="10"
|- valign="top"
|
[[Image:package.png|thumb|right|200px|Learning how to conserve disk space is essential for the efficient operation of a Linux computer system. You will learn how to manipulate the size of Linux file-system sizes (via '''LVM''') in Lab 5. ]]
|
[[Image:lbreakout2.png|thumb|right|200px|You will download and compile the game called '''lbreakout2''' which is only available as compressed source code. ]]
|}
=== Purpose / Objectives of Lab 3===
In this lab, you are going to identify potential problems such as running out of space to run a GUI, or forgetting your root password. You will also learn to conserve hard disk space by learning how to compress and decompress files that are stored on your computer server. In addition, you will learn alternative methods of how to install applications (i.e. programs).
<u>Main Objectives</u>
*Learn to boot your CentOS VM into '''Single User mode''' for rescue purposes
*Create and extract '''archive''' files ('''tar''' and '''tar.gz''')
*Install applications using various methods:
:*'''Download''', '''decompress''' and archive file from the Internet, then '''compile source code''' in order to install an application.
:*Use '''yum''' utility to install software from '''local source programs''' (on DVD drive)
:*Use '''yum''' utility to install software from '''repositories''' (online storage areas)
:*Learn how to '''add repositories''' (online software storage areas) to install less common applications.
<ul><li value="4">Demonstrate the use of Bash Shell scripts to automate routine tasks (generate a customized software report)</li></ul>
{|width="100%" cellspacing="0"
|- valign="top"
|colspan="3" style="font-size:16px;font-weight:bold;border-bottom: thin solid black;border-spacing:0px;"|Minimum Required Materials<br>
|colspan="3" style="font-size:16px;font-weight:bold;border-bottom: thin solid black;border-spacing:0px;padding-left:20px;"|Linux Command Reference<br>
|- valign="top"
|width="10%" style="padding-left:20px;" |[[Image:ssd.png|thumb|left|85px|<b>Solid State Drive</b>]]
|width="10%" style="padding-left:20px;" |[[Image:ubs-key.png|thumb|left|85px|<b>USB key</b><br>(for backups)]]
|width="10%" style="padding-left:20px;" |[[Image:log-book.png|thumb|left|70px|<b>Lab3 Log Book</b>]]
| style="padding-left:20px;"|Archiving / Compiling
[http://man7.org/linux/man-pages/man1/tar.1.html tar]<br>
[http://linuxcommand.org/lc3_man_pages/gzip1.html gzip, gunzip]<br>
[http://man7.org/linux/man-pages/man1/make.1.html make]<br><br>
Software Manangement<br>
[https://linux.die.net/man/8/rpm rpm]<br>
[http://man7.org/linux/man-pages/man8/yum.8.html yum]
| style="padding-left:20px;"|Miscellaneous
[http://man7.org/linux/man-pages/man1/ls.1.html ls]<br>
[http://man7.org/linux/man-pages/man1/more.1.html more]<br>
[http://man7.org/linux/man-pages/man1/wget.1.html wget]<br>
[http://man7.org/linux/man-pages/man1/chmod.1.html chmod]<br>
[http://ss64.com/vi.html vi]
| style="padding-left:20px;"|Matrix On-line Tutorials:<ul><li>Shell Scripting Basics - Part 4 (The sed Utility):<br>'''/home/ops235/scripting-4'''</li></ul>
|}
= INVESTIGATION 1: TROUBLESHOOTING BOOTING & FORGOTTEN ROOT PASSWORD =
{| width="50%" align="right" cellpadding="10"
|- valign="top"
|
[[Image:grub1.png|thumb|right|600px|Press '''e''' at Grub Boot Menu to edit]]
|}
===Part 1: Common Booting Issues===
There are a few "classic problems" that students can encounter with their virtual machines and their host machine after performing lab2. Although all OPS245 students may not encounter these problems, it is good to be aware of what a potential problem may look like, and know how to solve that problem.
'''A few common problems are:'''
*I Can't boot into Graphical Mode on my '''c7host''' machine
*I Forgot My '''Regular User''' Password
*I Forgot My '''root''' Password
*I Can't Start My Virtual Machine
'''Troubleshooting consists of 3 basic elements:'''
*'''Asking Questions''' (eg. what was done recently prior to problem?)
*'''Eliminating''' what the problem '''IS NOT'''
*Having '''Tenacity''' and '''patience''' (ability to focus on finding the cause of the problem)
{| width="50%" align="right" cellpadding="10"
|- valign="top"
|
[[Image:grub2_1.png|thumb|right|600px|Add the boot option '''single''' and then press '''ctrl-x''' to boot into single user mode]]
|}
===Part 2: Booting into Single-User Mode===
If you cannot log graphically into your machine (first two common problems), there is a trick to boot your system into '''single-user''' mode. This mode does not provide networking, graphics, or logging in as other regular users, but can connect to a text-based interface as the '''root''' user. This method will only work if a GRUB (<u>'''Gr'''</u>and '''<u>U</u>'''nified <u>'''B'''</u>oot-loader) password has not been set, or that you haven't forgotten the GRUB password.
'''Perform the following steps:'''
#Launch the VMware application.
#Select Open Virtual Machine, and select the VM called c7host on your Solid State Drive.
#Launch your '''c7host''' machine, and login as as a regular user.
#Boot-up your '''centos1''' VM. ''' When the Grub Boot menu appears''', press the letter <b><code><span style="color:#3366CC;font-size:1.2em;">e</span></code></b> (for "edit").
#Using your arrow keys, scroll to next screen to '''linux''', or '''linux16''', or '''linux-efi''' command and type the word <b><code><span style="color:#3366CC;font-size:1.2em;">single</span></code></b> as an argument after '''quiet''' (see diagram for reference) and then press <b><code><span style="color:#3366CC;font-size:1.2em;">ctrl-x</span></code></b> to boot.
#The system should boot into text-based mode. Enter your '''root''' password.
#One thing to look at is partition space usage. Issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">df -h</span></code></b>
#If you notice 0% free space in the '''/''' partition, then there is a problem. This most likely is caused by not following steps to create a <u>compressed</u> copy of the VM image. If that is the case, locate the large image backup and remove it. Do NOT remove the image in ''/var/lib/libvirt/images'' directory!
#You can use the '''passwd''' command to reset your '''regular user''' password (eg. <b><code><span style="color:#3366CC;font-size:1.2em;">passwd regularuserid</span></code></b>). You can press '''ctrl-c''' if you wish to abort (i.e. not change password).
#To restart in graphical mode, simply enter the command <b><code><span style="color:#3366CC;font-size:1.2em;">reboot</span></code></b>.
{| width="50%" align="right" cellpadding="10"
|- valign="top"
|
[[Image:grub2_3.png|thumb|right|600px|Add '''rw init=/sysroot/bin/sh''' as shown and then press '''ctrl-x''' to boot into single user no root password mode]]
|}
===Part 3: Resetting Forgotten Root Password===
Unfortunately, booting into Single-User Mode does not work if you forgot your '''root''' password, since the procedure in the previous part requires that you enter your root password. In order to reset your root password, you need to perform a different procedure (shown below).
'''Perform the following steps:'''
#The procedure to reset root's password is different than shown above.
#Make certain that your centos1 VM that you used in Part 2 has been shutdown.
#Start your centos1 VM and press <b><code><span style="color:#3366CC;font-size:1.2em;">e</span></code></b> at the Grub boot menu.
#Using your arrow keys, move to '''linux''' or '''linux-efi''' command and replace the argument '''ro''' with the argument <b><code><span style="color:#3366CC;font-size:1.2em;">rw init=/sysroot/bin/sh</span></code></b> (see diagram for reference) and then press <b><code><span style="color:#3366CC;font-size:1.2em;">ctrl-x</span></code></b> to boot.
#The system should boot into text-based mode without prompting for root's password.
#Issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">chroot /sysroot</span></code></b><br>
#Issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">passwd root</span></code></b> in order to change your root password (press '''ctrl-c''' if you wish to abort - i.e. not change password).<br>'''NOTE:''' if you are using SELinux in '''enforcing''' or '''permissive''' mode, you will also need to issue the command: '''touch /.autorelabel''' <br>This may take some time depending on the amount of files you have on the file system (usually about 2 minutes).
#To restart in graphical mode, simply enter the command <b><code><span style="color:#3366CC;font-size:1.2em;">exit</span></code></b>, then <b><code><span style="color:#3366CC;font-size:1.2em;">reboot</span></code></b>.
{{Admon/important | What To Do If Reboot Doesn't Work | In this mode, the reboot command may not work. If it doesn't, go to the top of the centos1 VM window, select Send Key -> Ctrl+Alt+Delete.}}
===Catastrophic Boot Problems===
:Not being able to start your '''c7host''' due to '''Kernel Panic''' or some sort of '''catastrophic disk failure''' is not as easy to fix. You might be able to boot from your '''Centos LIVE DVD, open a terminal and mount the partition''' via command line and look for possible problems (setup files like '''/etc/fstab'''). '''Lab5''' will discuss more about mounting and the /etc/fstab file. The "worst-case scenario" would be to purchase a new hard disk, '''perform lab1 completely, perform lab2 to install and set-up virtualization software''', then '''restore your VM image and xml file backups''' (eg. decompressing images, issuing virsh define commands for .xml files). That is why consistently '''performing backups of ALL of your VMS at the end of each lab is absolutely essential! You have been warned!'''
'''Answer INVESTIGATION 1 observations / questions in your lab log book.'''
= INVESTIGATION 2: ARCHIVING & RESTORING FILES =
===Part 1: Creating a File Archive===
One method to help prevent running out of hard disk space is to compress or '''archive''' files so they take up less space on your computer system. Archiving files is also a popular method to '''bundle files together''' into one smaller file for fast transfers to other computer servers.
'''Perform the following steps:'''
#Boot up your '''centos3''' VM.
#Change your working directory to '''/usr/share/doc/sudo*'''
#Use the tar (tape archiver) command to create an archive file named "/tmp/archive1.tar" by issuing the following command:<br><b><code><span style="color:#3366CC;font-size:1.2em;">tar cvf /tmp/archive1.tar .</span></code></b>
{{Admon/important | Warning! | Don't miss the <code>.</code> at the end of the <code>tar</code> command (where indicated). It specifies what should go into the archive: the contents of the current directory.}}
<ol>
<li value="4">What do the options '''c''', '''v''', and '''f''' mean?</li>
<li>Record the archive file size.</li>
<li>Compress the file using '''gzip''' by issuing the command: <b><code><span style="color:#3366CC;font-size:1.2em;">gzip /tmp/archive1.tar</span></code></b></li>
<li>Record the archive file size after compression.</li>
<li>Make sure you're still in '''/usr/share/doc/sudo*''' and then create a compressed archive by issuing the following command:<br> <b><code><span style="color:#3366CC;font-size:1.2em;">tar cvzf /tmp/archive2.tar.gz .</span></code></b></li>
<li>What does the''' z''' option do?</li>
<li>Compare the sizes of '''/tmp/archive1.tar.gz''' and '''/tmp/archive2.tar.gz'''. Why are they so close in size?</li>
</ol>
===Part 2: Restoring Files From an Archive===
'''Perform the following steps:'''
#Remain in your '''centos3''' VM.
#Create the directory '''/tmp/extract1'''
#Change to the '''/tmp/extract1''' directory.
#Move the file '''archive1.tar.gz''' to your current directory.
#Unzip the first archive you created by issuing the command: <b><code><span style="color:#3366CC;font-size:1.2em;">gunzip archive1.tar.gz</span></code></b>
#Extract the files from the first archive by issuing the command: <b><code><span style="color:#3366CC;font-size:1.2em;">tar xvf archive1.tar</span></code></b>
#Are all the files there?
#Compare '''/tmp/extract1/README''' and '''/usr/share/doc/sudo*/README'''. Are they exactly the same? Why?
#Create the directory '''/tmp/extract2'''
#Move the file '''archive2.tar.gz''' to the '''/tmp/extract2''' directory.
#Extract the files from the second archive by issuing the following command: <b><code><span style="color:#3366CC;font-size:1.2em;">tar xvzf /tmp/extract2/archive2.tar.gz</span></code></b>
#Note that this time a separate <b><code><span style="color:#3366CC;font-size:1.2em;">gunzip</span></code></b> command was not needed. Why?
#Repeat the previous command, leaving out the option '''z'''. Does it work? Why?
#Compare the '''README''' file in this directory with the original file. Are they exactly the same?
'''Answer Investigation 2 observations / questions in your lab log book.'''
=INVESTIGATION 3: MANAGING SOFTWARE PACKAGES=
{| width="40%" align="right" cellpadding="10"
|- valign="top"
|colspan="2"|{{Admon/note|Internet Connection|In order for the '''yum install''' command to work you require a connection to the Internet.}}
|}
=== Part 1: Managing Software and Repositories with Yum ===
We will learn how to install software packages with the '''yum''' utility. This command is useful for installing software since it automatically resolves software dependencies prior to installing the software. Upon your Centos OS install, a link to a software repository is automatically made to allow for easy software updates.
Unfortunately, there is no guarantee that a particular software package is contained on the default repository. In order to overcome this problem, you can add other repositories that may contain the application that you wish to install.
'''Perform the following steps:'''
#Make certain that you are in your '''c7host''' machine.
#Issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo yum install elinks</span></code></b>
#Now issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">yum info elinks</span></code></b>
#How can you tell if the elinks package has been installed?
#To remove the elinks package issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo yum remove elinks</span></code></b>
# Verify that the elinks package has been removed. Also verify that the application called: '''xchat''' is not installed.
# Use the wget command to download the xchat rpm binary from the following URL:
::<b><code><span style="color:#3366CC;font-size:1.2em;">http://mirror.centos.org/centos/7/os/x86_64/Packages/xchat-2.8.8-25.el7.x86_64.rpm</span></code></b><br>
::What do you think is the purpose of the numbers also contained in the filename?
<ol><li value="8">Issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo yum localinstall xchat-2.8.8-25.el7.x86_64.rpm</span></code></b></li>
<li>Verify that the '''xchat''' command has been installed.</li>
<li>Run the xchat application.</li></ol>
{| width="40%" align="right" cellpadding="10"
|- valign="top"
|colspan="2"|{{Admon/tip|IRCs: A Great Tool for Linux Administrators|Although Search Engines (like Google) are a system administrator's good friend, Internet Relay Chats (IRCs) are also a great tool for system administrators to help obtain information. Many website offer information on how to connect to IRCs (both nodes (eg. FreeNode) and irc channel (eg. #linux). You can now use your newly-created application called '''xchat''' to do this.<br><br><u>'''A few tips to consider with IRCs'''</u>:<ul><li>Do your Homework (read docs first!)</li><li>Ask specific questions</li><li>Not all chats are friendly</li><li>Be patient when asking questions (use courtesy)</li><li>The advice is free (you get what you pay for!)</ul>}}
|}
<ol>
<li value="11">We will now look at how we can add different repositories to our '''c7host''' machine.</li><li>Issue the following command: <b><code><span style="color:#3366CC;font-size:1.3em;">yum repolist</span></code></b></li><li>Take a few moments to review the output. Do you see which repositories are used by the '''yum''' command? Write down the repositories in your lab logbook.</li><li>View the following link to see a general listing of repositories:<br>[ [http://wiki.centos.org/AdditionalResources/Repositories Available Repositories for Centos] ].</li><li>To add the epel repository, issue the command:<br><b><code><span style="color:#3366CC;font-size:1.3em;">sudo yum install epel-release</span></code></b></li><li>To verify that you have added the repository, you can issue the command: <b><code><span style="color:#3366CC;font-size:1.3em;">yum repolist</span></code></b></li><li>Unused and unneeded software can present a security risk and ties up disk space needlessly. Find '''at least 4 other packages''' to remove on your c7host machine(for example: '''sound & video''', '''games''', etc) that you're not using on your system. Be careful to ensure that removing those packages does not also remove other software that you do need.</li>
</ol>
===Part 2: Compiling Source Code from a Downloaded Archived File===
Sometimes, some software may <u>not</u> be available on repositories to install with the '''yum''' command. They may be available from web-pages to download, and compile. Now that you know how to create and decompress "zipped tarball archives", we will demonstrate how to install applications from websites containing these types of archives. Although this method is not as "user-friendly" as using the yum command, this method is useful if the application is NOT contained in regular software repositories...
In order to build software from source code, you must have the appropriate software development tools (such as make and gcc) and libraries (such as GTK) installed. The required tools will vary depending on the computer languages used in the software being built.
{| width="40%" align="right" cellpadding="10"
|- valign="top"
|colspan="2"|{{Admon/note|Installing Development Libraries|In the future, remember the above procedure whenever installing software from source. Sometimes, you need to install additional tools or libraries in order to compile a particular software package}}
|}
'''Perform the following steps:'''
# Remain in your '''c7host''' VM, but make certain that you are logged in as a regular user (i.e. NOT root!).
# Issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">which lbreakout2</span></code></b><br>Is there a program called '''lbreakout2''' on your system?
# Perform an Internet search for the pattern: <b><code><span style="color:#3366CC;font-size:1.2em;">lbreakout2 tar.gz</span></code></b>
# Go to an appropriate webpage and download a "zipped tarball" (compressed source code) for the '''lbreakout2''' game (filename should be something like: '''lbreakout2-2.6.5.tar.gz''')
#Change to the directory where you downloaded that file (most likely ''~/Download''s).
# Use the '''tar''' command to decompress the "zipped tarball" called something like (not may be exactly): '''lbreakout2-2.6.5.tar.gz'''.
# Change to the directory that contains that ''lbreakout2'' source code.
{| width="40%" align="right" cellpadding="10"
|- valign="top"
|colspan="2"|{{Admon/note|Using '''&&''' and '''||''' Conditional Statements|A very useful trick when running several commands in sequence is to use conditional statments. The '''&&''' conditional will run the subsequent command only if the previous command returns a true (0) exit status, for example:<br>'''./configure && make'''. The '''||''' conditional will run the subsequent command only if the previous command returns a false (non-zero) exit status, for example:<br>'''./configure || echo "Houston, we have a problem"'''. These conditional can be combined, for example:<br>'''./configure && make || echo "Houston, we have a problem"'''}}
|}
<ol>
<li value="8">Issue the following command:<br><b><code><span style="color:#3366CC;font-size:1.2em;">./configure && make</span></code></b><br>Most likely, you will get an '''ERROR!''' What do you think the error is telling you?<br></li>
<li>Issue the following command to install the files for application development by issuing the command:<br><b><code><span style="color:#3366CC;font-size:1.2em;">sudo yum groupinstall "Development Tools"</span></code></b></li>
<li>Issue the command in step 7. You should get another ERROR! What dependency is missing?</li>
<li>Issue the following command to install the library files for SQL by issuing the command:<br><b><code><span style="color:#3366CC;font-size:1.2em;">sudo yum install SDL-devel libpng-devel zlib-devel</span></code></b></li>
<li>Reissue the <b><code><span style="color:#3366CC;font-size:1.2em;">./configure && make</span></code></b> command. Were you successful?</li>
<li>Run the command <b><code><span style="color:#3366CC;font-size:1.2em;">lbreakout2</span></code></b>. Were you successful?</li>
<li>You need to run a command to make this program available regardless of your current directory (as opposed to running command in the directory that contains the program). So, issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo make install</span></code></b></li>
<li>Run the command: <b><code><span style="color:#3366CC;font-size:1.2em;">lbreakout2</span></code></b>. Did it work? Issue the command:<br> <b><code><span style="color:#3366CC;font-size:1.2em;">which lbreakout2</span></code></b>. What do you think that the '''make install''' command did?</li>
</ol>
{|width="40%" align="right" cellpadding="10"
|- valign="top"
|
{{Admon/tip|Bash Shell Tips:|<br /><u>Using sed to Manipulate Text</u>'''<ul><li>The Linux command '''sed''' stands for <u>'''S'''</u>treaming <u>'''Ed'''</u>itor which is an effective way to manipulate a text file, output sent from a command, or from within a "here document". This command can manipulate matching text on a variety of criteria (such as '''line number(s)''', '''regular expression match''', etc). Commands can then be used for manipulation such as '''omitting''', '''printing''', '''substituting''', '''adding''', and '''inserting''' text.<br><br></li><li>The sed option '''-n''' suppresses display of text so the print ('''p''') command can be used; otherwise, the text will be displayed (with edits via the sed command instructions).<br><br></li><li>Results of text manipulation with sed can be stored in a variable using command substitution, or redirected to a file. '''NEVER redirect the stdout from a sed command to the same input file (or the input file will be destroyed)!''' <br><br></li><li>Examples<br><br>''sed 's/|/ /g' <<+<br>I|like|weekends!<br>+''<br><br>''sed 's/$/\n/g' <<+<br>This text<br>should be<br>double-spaced!''<br>+<br><br></li></ul>}}
|}
===Part 3: Using sed to Filter Output from Commands===
We will continue with using commands to create a Software Information Report that manipulates output generated by the '''rpm''' command. The '''sed''' and '''awk''' commands are very useful tools in shell scripting to manipulate text. In this lab, we will be using ''sed'' to allow the user to select certain portions from the rpm command (options -qi).
'''Perform the following steps:'''
<ol>
<li> Use your '''c7host''' VM for this section.</li>
<li>Open a Bash terminal and run the command:
<br>
<code><span style="color:#3366CC;font-size:1.1em;"><b>
# Use sed with extended regular expressions to only print those matching report elements<br>
rpm -qi xchat
</b></span></code><br />
Notice that using the '''-i''' option with '''-q''' causes rpm to generate more output than we have seen from it so far.</li>
<li>Pick any five packages and run the <code><span style="color:#3366CC;font-size:1.1em;"><b>rpm -qi</b></span></code> command on all five at once. This should produce dozens of lines of output. Consider the output it would generate if we used -a instead of picking just a few packages.
<li>Run <code><span style="color:#3366CC;font-size:1.1em;"><b>rpm -qia</b></span></code> now.</li>
<li>That is way too much output for us to reasonably search through, but we have commands that can filter this down to a much more readable amount.</li>
<li>Try the command: <br><code><span style="color:#3366CC;font-size:1.1em;"><b>rpm -qia | sed -nre '/^Name[[:space:]]+:/ p' -e '/^Install Date[[:space:]]*:/ p'</b></span></code><br />
Instead of printing every line, this will only display the name and install date of each package.</li>
<li>Try modifying that command to display only the package Name and License.</li>
</ol>
'''Answer the Investigation 3 observations / questions in your lab log book.'''
=INVESTIGATION 4: USING LOGICAL STRUCTURES IN PYTHON=
Now that we have added some powerful logical structures to our python scripts, we can make our scripts much more adaptable. Our python scripts can now respond to different situations by executing different code, or repeating the same code several times (e.g. keep asking the user for input until they give us something useful). In this investigation you will write a python script that will prompt a user for a directory to archive, ask them if they want the archive compressed, and (only if they do want compression) what type of compression to apply.
<ol>
<li>In your bin directory, create the file tarchiver.py, and populate with our standard beginning:
<code style="color:#3366CC;font-family:courier;font-size:.9em;">
<br>
#!/usr/bin/env python3<br />
# tarchiver.py<br />
# Purpose: Creates a tar archive of a directory<br />
#<br />
# USAGE: ./tarchiver.py<br />
#<br />
# Author: *** INSERT YOUR NAME ***<br />
# Date: *** CURRENT DATE ***<br />
import os<br />
</code>
</li>
<li>Next, add prompts using the '''input()''' function to ask the user for:
<ul>
<li>The directory they wish to archive.</li>
<li>The name they want to give the archive.</li>
</ul>
Remember to store their responses in variables.</li>
<li>Add a line that uses the values provided by the user to execute a tar command and create and archive of the directory they requested.</li>
<li>Test your script to make sure it works.</li>
<li>Add a third prompt (immediately after the other two prompts and before the tar command), asking the user if they want the archive to be compressed. You'll need an if statement to run your tar command with gzip compression if they answered yes.</li>
<li>Test your script to make sure it works.</li>
<li>Add a fourth prompt asking the user what type of compression they want (present them with gzip, bzip2, and xzip as options). Note that this prompt should only be shown if the user opted for compression (if they don't want compression, there is no point asking what type they don't want).</li>
<li>Expand the if statement around your actual tar command to use whichever type of compression the user asked for.</li>
<li>Test your script to make sure it works.</li>
<li>Test your script again, but feed it nonsense data (e.g. answer 'very much so' instead of 'y' or 'n' when prompted about compression).</li>
<li>Add loops around your prompts for whether or not the user wants compression, and the compression type to make the script repeat each prompt until the user gives a response your script can actually use. Don't worry about doing anything with the archive name or path.</li>
<li>Now test your script again, with good data and with nonsense.</li>
<li>When you are confident your script works, you are ready to submit the lab.</li>
</ol>
= LAB 3 SIGN-OFF (SHOW INSTRUCTOR) =
Follow the submission instructions for lab 3 on Blackboard.
{{Admon/important|Time for a new backup!|If you have successfully completed this lab, make a new backup of your virtual machines as well as your host machine.}}
'''Perform the Following Steps:'''
# Make certain that your '''c7host''' and '''centos3''' VMs are running.
# Switch to your <u>'''c7host'''</u> machine, open a shell terminal as a regular user, and change to the directory: '''~/bin'''
# Download the Lab 3 check script: <b><code><span style="color:#3366CC;font-size:1.2em;">wget https://raw.githubusercontent.com/OPS245/labs/main/lab3-check.bash</span></code></b><!--<br>For Andrew's sections use this script instead: <b><code><span style="color:#3366CC;font-size:1.2em;">wget http://littlesvr.ca/ops245/lab3-check-andrew.bash</span></code></b>-->
# Give the '''lab3-check.bash''' file execute permissions (for the file owner).
# Run the shell script with <code>sudo</code>, and if any warnings appear, fix the issues noted by the script and rerun the check until you receive the "Congratulations!" message.
# Arrange proof of the following on the screen:<br><span style="color:green;font-size:1.5em;">✓</span> '''centos3''':<blockquote><ul><li> Archived files '''created'''</li><li>Archive files '''restored'''</ul></blockquote><span style="color:green;font-size:1.5em;">✓</span> '''c7host''':<blockquote><ul><li> '''One repository added''' for yum</li><li>Run the '''lab3-check.bash''' script (must have all <b><code><span style="color:#66cc00;border:thin solid black;font-size:1.2em;"> OK </span></code></b> messages)</li></ul></blockquote><span style="color:green;font-size:1.5em;">✓</span> '''Lab 3''' logbook pages filled out.
# Upload a screen of the proof from the previous step, along with the file generated by '''lab3-check.bash''', your log book, and your '''tarchiver.py''' script to blackboard.
= Practice For Quizzes, Tests, Midterm & Final Exam =
#What is the purpose of booting into single-user mode?
#List the steps in order to boot into single-user mode.
#List the steps to reset a forgotten root password.
#What is the difference between a .tgz file and a .tar.gz file? What do these stand for?
#What is the purpose of a repository?
#What is source code?
#How do you build software from source code?
#What does yum do that compiled source code does not?
#Other than running an installed package, what commands can you issue to verify that the package was installed?
#List the steps to remove a package via yum command.
#List the steps to install a package using the yum command.
#List the steps to add a repository to be used with yum.
#What is the command to list all repositories associated with the yum command?
#What is the command to view all repositories that have been added to-date?
#How do you use the '''sed''' command to modify text?
#What is the '''Here-Document''', and how can it be used in issuing command and shell scripting?
[[Category:OPS245]]
[[Category:OPS245 Labs]]
[[Category:Digital Classroom]]
{| width="40%" align="right" cellpadding="10"
|- valign="top"
|
[[Image:package.png|thumb|right|200px|Learning how to conserve disk space is essential for the efficient operation of a Linux computer system. You will learn how to manipulate the size of Linux file-system sizes (via '''LVM''') in Lab 5. ]]
|
[[Image:lbreakout2.png|thumb|right|200px|You will download and compile the game called '''lbreakout2''' which is only available as compressed source code. ]]
|}
=== Purpose / Objectives of Lab 3===
In this lab, you are going to identify potential problems such as running out of space to run a GUI, or forgetting your root password. You will also learn to conserve hard disk space by learning how to compress and decompress files that are stored on your computer server. In addition, you will learn alternative methods of how to install applications (i.e. programs).
<u>Main Objectives</u>
*Learn to boot your CentOS VM into '''Single User mode''' for rescue purposes
*Create and extract '''archive''' files ('''tar''' and '''tar.gz''')
*Install applications using various methods:
:*'''Download''', '''decompress''' and archive file from the Internet, then '''compile source code''' in order to install an application.
:*Use '''yum''' utility to install software from '''local source programs''' (on DVD drive)
:*Use '''yum''' utility to install software from '''repositories''' (online storage areas)
:*Learn how to '''add repositories''' (online software storage areas) to install less common applications.
<ul><li value="4">Demonstrate the use of Bash Shell scripts to automate routine tasks (generate a customized software report)</li></ul>
{|width="100%" cellspacing="0"
|- valign="top"
|colspan="3" style="font-size:16px;font-weight:bold;border-bottom: thin solid black;border-spacing:0px;"|Minimum Required Materials<br>
|colspan="3" style="font-size:16px;font-weight:bold;border-bottom: thin solid black;border-spacing:0px;padding-left:20px;"|Linux Command Reference<br>
|- valign="top"
|width="10%" style="padding-left:20px;" |[[Image:ssd.png|thumb|left|85px|<b>Solid State Drive</b>]]
|width="10%" style="padding-left:20px;" |[[Image:ubs-key.png|thumb|left|85px|<b>USB key</b><br>(for backups)]]
|width="10%" style="padding-left:20px;" |[[Image:log-book.png|thumb|left|70px|<b>Lab3 Log Book</b>]]
| style="padding-left:20px;"|Archiving / Compiling
[http://man7.org/linux/man-pages/man1/tar.1.html tar]<br>
[http://linuxcommand.org/lc3_man_pages/gzip1.html gzip, gunzip]<br>
[http://man7.org/linux/man-pages/man1/make.1.html make]<br><br>
Software Manangement<br>
[https://linux.die.net/man/8/rpm rpm]<br>
[http://man7.org/linux/man-pages/man8/yum.8.html yum]
| style="padding-left:20px;"|Miscellaneous
[http://man7.org/linux/man-pages/man1/ls.1.html ls]<br>
[http://man7.org/linux/man-pages/man1/more.1.html more]<br>
[http://man7.org/linux/man-pages/man1/wget.1.html wget]<br>
[http://man7.org/linux/man-pages/man1/chmod.1.html chmod]<br>
[http://ss64.com/vi.html vi]
| style="padding-left:20px;"|Matrix On-line Tutorials:<ul><li>Shell Scripting Basics - Part 4 (The sed Utility):<br>'''/home/ops235/scripting-4'''</li></ul>
|}
= INVESTIGATION 1: TROUBLESHOOTING BOOTING & FORGOTTEN ROOT PASSWORD =
{| width="50%" align="right" cellpadding="10"
|- valign="top"
|
[[Image:grub1.png|thumb|right|600px|Press '''e''' at Grub Boot Menu to edit]]
|}
===Part 1: Common Booting Issues===
There are a few "classic problems" that students can encounter with their virtual machines and their host machine after performing lab2. Although all OPS245 students may not encounter these problems, it is good to be aware of what a potential problem may look like, and know how to solve that problem.
'''A few common problems are:'''
*I Can't boot into Graphical Mode on my '''c7host''' machine
*I Forgot My '''Regular User''' Password
*I Forgot My '''root''' Password
*I Can't Start My Virtual Machine
'''Troubleshooting consists of 3 basic elements:'''
*'''Asking Questions''' (eg. what was done recently prior to problem?)
*'''Eliminating''' what the problem '''IS NOT'''
*Having '''Tenacity''' and '''patience''' (ability to focus on finding the cause of the problem)
{| width="50%" align="right" cellpadding="10"
|- valign="top"
|
[[Image:grub2_1.png|thumb|right|600px|Add the boot option '''single''' and then press '''ctrl-x''' to boot into single user mode]]
|}
===Part 2: Booting into Single-User Mode===
If you cannot log graphically into your machine (first two common problems), there is a trick to boot your system into '''single-user''' mode. This mode does not provide networking, graphics, or logging in as other regular users, but can connect to a text-based interface as the '''root''' user. This method will only work if a GRUB (<u>'''Gr'''</u>and '''<u>U</u>'''nified <u>'''B'''</u>oot-loader) password has not been set, or that you haven't forgotten the GRUB password.
'''Perform the following steps:'''
#Launch the VMware application.
#Select Open Virtual Machine, and select the VM called c7host on your Solid State Drive.
#Launch your '''c7host''' machine, and login as as a regular user.
#Boot-up your '''centos1''' VM. ''' When the Grub Boot menu appears''', press the letter <b><code><span style="color:#3366CC;font-size:1.2em;">e</span></code></b> (for "edit").
#Using your arrow keys, scroll to next screen to '''linux''', or '''linux16''', or '''linux-efi''' command and type the word <b><code><span style="color:#3366CC;font-size:1.2em;">single</span></code></b> as an argument after '''quiet''' (see diagram for reference) and then press <b><code><span style="color:#3366CC;font-size:1.2em;">ctrl-x</span></code></b> to boot.
#The system should boot into text-based mode. Enter your '''root''' password.
#One thing to look at is partition space usage. Issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">df -h</span></code></b>
#If you notice 0% free space in the '''/''' partition, then there is a problem. This most likely is caused by not following steps to create a <u>compressed</u> copy of the VM image. If that is the case, locate the large image backup and remove it. Do NOT remove the image in ''/var/lib/libvirt/images'' directory!
#You can use the '''passwd''' command to reset your '''regular user''' password (eg. <b><code><span style="color:#3366CC;font-size:1.2em;">passwd regularuserid</span></code></b>). You can press '''ctrl-c''' if you wish to abort (i.e. not change password).
#To restart in graphical mode, simply enter the command <b><code><span style="color:#3366CC;font-size:1.2em;">reboot</span></code></b>.
{| width="50%" align="right" cellpadding="10"
|- valign="top"
|
[[Image:grub2_3.png|thumb|right|600px|Add '''rw init=/sysroot/bin/sh''' as shown and then press '''ctrl-x''' to boot into single user no root password mode]]
|}
===Part 3: Resetting Forgotten Root Password===
Unfortunately, booting into Single-User Mode does not work if you forgot your '''root''' password, since the procedure in the previous part requires that you enter your root password. In order to reset your root password, you need to perform a different procedure (shown below).
'''Perform the following steps:'''
#The procedure to reset root's password is different than shown above.
#Make certain that your centos1 VM that you used in Part 2 has been shutdown.
#Start your centos1 VM and press <b><code><span style="color:#3366CC;font-size:1.2em;">e</span></code></b> at the Grub boot menu.
#Using your arrow keys, move to '''linux''' or '''linux-efi''' command and replace the argument '''ro''' with the argument <b><code><span style="color:#3366CC;font-size:1.2em;">rw init=/sysroot/bin/sh</span></code></b> (see diagram for reference) and then press <b><code><span style="color:#3366CC;font-size:1.2em;">ctrl-x</span></code></b> to boot.
#The system should boot into text-based mode without prompting for root's password.
#Issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">chroot /sysroot</span></code></b><br>
#Issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">passwd root</span></code></b> in order to change your root password (press '''ctrl-c''' if you wish to abort - i.e. not change password).<br>'''NOTE:''' if you are using SELinux in '''enforcing''' or '''permissive''' mode, you will also need to issue the command: '''touch /.autorelabel''' <br>This may take some time depending on the amount of files you have on the file system (usually about 2 minutes).
#To restart in graphical mode, simply enter the command <b><code><span style="color:#3366CC;font-size:1.2em;">exit</span></code></b>, then <b><code><span style="color:#3366CC;font-size:1.2em;">reboot</span></code></b>.
{{Admon/important | What To Do If Reboot Doesn't Work | In this mode, the reboot command may not work. If it doesn't, go to the top of the centos1 VM window, select Send Key -> Ctrl+Alt+Delete.}}
===Catastrophic Boot Problems===
:Not being able to start your '''c7host''' due to '''Kernel Panic''' or some sort of '''catastrophic disk failure''' is not as easy to fix. You might be able to boot from your '''Centos LIVE DVD, open a terminal and mount the partition''' via command line and look for possible problems (setup files like '''/etc/fstab'''). '''Lab5''' will discuss more about mounting and the /etc/fstab file. The "worst-case scenario" would be to purchase a new hard disk, '''perform lab1 completely, perform lab2 to install and set-up virtualization software''', then '''restore your VM image and xml file backups''' (eg. decompressing images, issuing virsh define commands for .xml files). That is why consistently '''performing backups of ALL of your VMS at the end of each lab is absolutely essential! You have been warned!'''
'''Answer INVESTIGATION 1 observations / questions in your lab log book.'''
= INVESTIGATION 2: ARCHIVING & RESTORING FILES =
===Part 1: Creating a File Archive===
One method to help prevent running out of hard disk space is to compress or '''archive''' files so they take up less space on your computer system. Archiving files is also a popular method to '''bundle files together''' into one smaller file for fast transfers to other computer servers.
'''Perform the following steps:'''
#Boot up your '''centos3''' VM.
#Change your working directory to '''/usr/share/doc/sudo*'''
#Use the tar (tape archiver) command to create an archive file named "/tmp/archive1.tar" by issuing the following command:<br><b><code><span style="color:#3366CC;font-size:1.2em;">tar cvf /tmp/archive1.tar .</span></code></b>
{{Admon/important | Warning! | Don't miss the <code>.</code> at the end of the <code>tar</code> command (where indicated). It specifies what should go into the archive: the contents of the current directory.}}
<ol>
<li value="4">What do the options '''c''', '''v''', and '''f''' mean?</li>
<li>Record the archive file size.</li>
<li>Compress the file using '''gzip''' by issuing the command: <b><code><span style="color:#3366CC;font-size:1.2em;">gzip /tmp/archive1.tar</span></code></b></li>
<li>Record the archive file size after compression.</li>
<li>Make sure you're still in '''/usr/share/doc/sudo*''' and then create a compressed archive by issuing the following command:<br> <b><code><span style="color:#3366CC;font-size:1.2em;">tar cvzf /tmp/archive2.tar.gz .</span></code></b></li>
<li>What does the''' z''' option do?</li>
<li>Compare the sizes of '''/tmp/archive1.tar.gz''' and '''/tmp/archive2.tar.gz'''. Why are they so close in size?</li>
</ol>
===Part 2: Restoring Files From an Archive===
'''Perform the following steps:'''
#Remain in your '''centos3''' VM.
#Create the directory '''/tmp/extract1'''
#Change to the '''/tmp/extract1''' directory.
#Move the file '''archive1.tar.gz''' to your current directory.
#Unzip the first archive you created by issuing the command: <b><code><span style="color:#3366CC;font-size:1.2em;">gunzip archive1.tar.gz</span></code></b>
#Extract the files from the first archive by issuing the command: <b><code><span style="color:#3366CC;font-size:1.2em;">tar xvf archive1.tar</span></code></b>
#Are all the files there?
#Compare '''/tmp/extract1/README''' and '''/usr/share/doc/sudo*/README'''. Are they exactly the same? Why?
#Create the directory '''/tmp/extract2'''
#Move the file '''archive2.tar.gz''' to the '''/tmp/extract2''' directory.
#Extract the files from the second archive by issuing the following command: <b><code><span style="color:#3366CC;font-size:1.2em;">tar xvzf /tmp/extract2/archive2.tar.gz</span></code></b>
#Note that this time a separate <b><code><span style="color:#3366CC;font-size:1.2em;">gunzip</span></code></b> command was not needed. Why?
#Repeat the previous command, leaving out the option '''z'''. Does it work? Why?
#Compare the '''README''' file in this directory with the original file. Are they exactly the same?
'''Answer Investigation 2 observations / questions in your lab log book.'''
=INVESTIGATION 3: MANAGING SOFTWARE PACKAGES=
{| width="40%" align="right" cellpadding="10"
|- valign="top"
|colspan="2"|{{Admon/note|Internet Connection|In order for the '''yum install''' command to work you require a connection to the Internet.}}
|}
=== Part 1: Managing Software and Repositories with Yum ===
We will learn how to install software packages with the '''yum''' utility. This command is useful for installing software since it automatically resolves software dependencies prior to installing the software. Upon your Centos OS install, a link to a software repository is automatically made to allow for easy software updates.
Unfortunately, there is no guarantee that a particular software package is contained on the default repository. In order to overcome this problem, you can add other repositories that may contain the application that you wish to install.
'''Perform the following steps:'''
#Make certain that you are in your '''c7host''' machine.
#Issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo yum install elinks</span></code></b>
#Now issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">yum info elinks</span></code></b>
#How can you tell if the elinks package has been installed?
#To remove the elinks package issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo yum remove elinks</span></code></b>
# Verify that the elinks package has been removed. Also verify that the application called: '''xchat''' is not installed.
# Use the wget command to download the xchat rpm binary from the following URL:
::<b><code><span style="color:#3366CC;font-size:1.2em;">http://mirror.centos.org/centos/7/os/x86_64/Packages/xchat-2.8.8-25.el7.x86_64.rpm</span></code></b><br>
::What do you think is the purpose of the numbers also contained in the filename?
<ol><li value="8">Issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo yum localinstall xchat-2.8.8-25.el7.x86_64.rpm</span></code></b></li>
<li>Verify that the '''xchat''' command has been installed.</li>
<li>Run the xchat application.</li></ol>
{| width="40%" align="right" cellpadding="10"
|- valign="top"
|colspan="2"|{{Admon/tip|IRCs: A Great Tool for Linux Administrators|Although Search Engines (like Google) are a system administrator's good friend, Internet Relay Chats (IRCs) are also a great tool for system administrators to help obtain information. Many website offer information on how to connect to IRCs (both nodes (eg. FreeNode) and irc channel (eg. #linux). You can now use your newly-created application called '''xchat''' to do this.<br><br><u>'''A few tips to consider with IRCs'''</u>:<ul><li>Do your Homework (read docs first!)</li><li>Ask specific questions</li><li>Not all chats are friendly</li><li>Be patient when asking questions (use courtesy)</li><li>The advice is free (you get what you pay for!)</ul>}}
|}
<ol>
<li value="11">We will now look at how we can add different repositories to our '''c7host''' machine.</li><li>Issue the following command: <b><code><span style="color:#3366CC;font-size:1.3em;">yum repolist</span></code></b></li><li>Take a few moments to review the output. Do you see which repositories are used by the '''yum''' command? Write down the repositories in your lab logbook.</li><li>View the following link to see a general listing of repositories:<br>[ [http://wiki.centos.org/AdditionalResources/Repositories Available Repositories for Centos] ].</li><li>To add the epel repository, issue the command:<br><b><code><span style="color:#3366CC;font-size:1.3em;">sudo yum install epel-release</span></code></b></li><li>To verify that you have added the repository, you can issue the command: <b><code><span style="color:#3366CC;font-size:1.3em;">yum repolist</span></code></b></li><li>Unused and unneeded software can present a security risk and ties up disk space needlessly. Find '''at least 4 other packages''' to remove on your c7host machine(for example: '''sound & video''', '''games''', etc) that you're not using on your system. Be careful to ensure that removing those packages does not also remove other software that you do need.</li>
</ol>
===Part 2: Compiling Source Code from a Downloaded Archived File===
Sometimes, some software may <u>not</u> be available on repositories to install with the '''yum''' command. They may be available from web-pages to download, and compile. Now that you know how to create and decompress "zipped tarball archives", we will demonstrate how to install applications from websites containing these types of archives. Although this method is not as "user-friendly" as using the yum command, this method is useful if the application is NOT contained in regular software repositories...
In order to build software from source code, you must have the appropriate software development tools (such as make and gcc) and libraries (such as GTK) installed. The required tools will vary depending on the computer languages used in the software being built.
{| width="40%" align="right" cellpadding="10"
|- valign="top"
|colspan="2"|{{Admon/note|Installing Development Libraries|In the future, remember the above procedure whenever installing software from source. Sometimes, you need to install additional tools or libraries in order to compile a particular software package}}
|}
'''Perform the following steps:'''
# Remain in your '''c7host''' VM, but make certain that you are logged in as a regular user (i.e. NOT root!).
# Issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">which lbreakout2</span></code></b><br>Is there a program called '''lbreakout2''' on your system?
# Perform an Internet search for the pattern: <b><code><span style="color:#3366CC;font-size:1.2em;">lbreakout2 tar.gz</span></code></b>
# Go to an appropriate webpage and download a "zipped tarball" (compressed source code) for the '''lbreakout2''' game (filename should be something like: '''lbreakout2-2.6.5.tar.gz''')
#Change to the directory where you downloaded that file (most likely ''~/Download''s).
# Use the '''tar''' command to decompress the "zipped tarball" called something like (not may be exactly): '''lbreakout2-2.6.5.tar.gz'''.
# Change to the directory that contains that ''lbreakout2'' source code.
{| width="40%" align="right" cellpadding="10"
|- valign="top"
|colspan="2"|{{Admon/note|Using '''&&''' and '''||''' Conditional Statements|A very useful trick when running several commands in sequence is to use conditional statments. The '''&&''' conditional will run the subsequent command only if the previous command returns a true (0) exit status, for example:<br>'''./configure && make'''. The '''||''' conditional will run the subsequent command only if the previous command returns a false (non-zero) exit status, for example:<br>'''./configure || echo "Houston, we have a problem"'''. These conditional can be combined, for example:<br>'''./configure && make || echo "Houston, we have a problem"'''}}
|}
<ol>
<li value="8">Issue the following command:<br><b><code><span style="color:#3366CC;font-size:1.2em;">./configure && make</span></code></b><br>Most likely, you will get an '''ERROR!''' What do you think the error is telling you?<br></li>
<li>Issue the following command to install the files for application development by issuing the command:<br><b><code><span style="color:#3366CC;font-size:1.2em;">sudo yum groupinstall "Development Tools"</span></code></b></li>
<li>Issue the command in step 7. You should get another ERROR! What dependency is missing?</li>
<li>Issue the following command to install the library files for SQL by issuing the command:<br><b><code><span style="color:#3366CC;font-size:1.2em;">sudo yum install SDL-devel libpng-devel zlib-devel</span></code></b></li>
<li>Reissue the <b><code><span style="color:#3366CC;font-size:1.2em;">./configure && make</span></code></b> command. Were you successful?</li>
<li>Run the command <b><code><span style="color:#3366CC;font-size:1.2em;">lbreakout2</span></code></b>. Were you successful?</li>
<li>You need to run a command to make this program available regardless of your current directory (as opposed to running command in the directory that contains the program). So, issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo make install</span></code></b></li>
<li>Run the command: <b><code><span style="color:#3366CC;font-size:1.2em;">lbreakout2</span></code></b>. Did it work? Issue the command:<br> <b><code><span style="color:#3366CC;font-size:1.2em;">which lbreakout2</span></code></b>. What do you think that the '''make install''' command did?</li>
</ol>
{|width="40%" align="right" cellpadding="10"
|- valign="top"
|
{{Admon/tip|Bash Shell Tips:|<br /><u>Using sed to Manipulate Text</u>'''<ul><li>The Linux command '''sed''' stands for <u>'''S'''</u>treaming <u>'''Ed'''</u>itor which is an effective way to manipulate a text file, output sent from a command, or from within a "here document". This command can manipulate matching text on a variety of criteria (such as '''line number(s)''', '''regular expression match''', etc). Commands can then be used for manipulation such as '''omitting''', '''printing''', '''substituting''', '''adding''', and '''inserting''' text.<br><br></li><li>The sed option '''-n''' suppresses display of text so the print ('''p''') command can be used; otherwise, the text will be displayed (with edits via the sed command instructions).<br><br></li><li>Results of text manipulation with sed can be stored in a variable using command substitution, or redirected to a file. '''NEVER redirect the stdout from a sed command to the same input file (or the input file will be destroyed)!''' <br><br></li><li>Examples<br><br>''sed 's/|/ /g' <<+<br>I|like|weekends!<br>+''<br><br>''sed 's/$/\n/g' <<+<br>This text<br>should be<br>double-spaced!''<br>+<br><br></li></ul>}}
|}
===Part 3: Using sed to Filter Output from Commands===
We will continue with using commands to create a Software Information Report that manipulates output generated by the '''rpm''' command. The '''sed''' and '''awk''' commands are very useful tools in shell scripting to manipulate text. In this lab, we will be using ''sed'' to allow the user to select certain portions from the rpm command (options -qi).
'''Perform the following steps:'''
<ol>
<li> Use your '''c7host''' VM for this section.</li>
<li>Open a Bash terminal and run the command:
<br>
<code><span style="color:#3366CC;font-size:1.1em;"><b>
# Use sed with extended regular expressions to only print those matching report elements<br>
rpm -qi xchat
</b></span></code><br />
Notice that using the '''-i''' option with '''-q''' causes rpm to generate more output than we have seen from it so far.</li>
<li>Pick any five packages and run the <code><span style="color:#3366CC;font-size:1.1em;"><b>rpm -qi</b></span></code> command on all five at once. This should produce dozens of lines of output. Consider the output it would generate if we used -a instead of picking just a few packages.
<li>Run <code><span style="color:#3366CC;font-size:1.1em;"><b>rpm -qia</b></span></code> now.</li>
<li>That is way too much output for us to reasonably search through, but we have commands that can filter this down to a much more readable amount.</li>
<li>Try the command: <br><code><span style="color:#3366CC;font-size:1.1em;"><b>rpm -qia | sed -nre '/^Name[[:space:]]+:/ p' -e '/^Install Date[[:space:]]*:/ p'</b></span></code><br />
Instead of printing every line, this will only display the name and install date of each package.</li>
<li>Try modifying that command to display only the package Name and License.</li>
</ol>
'''Answer the Investigation 3 observations / questions in your lab log book.'''
=INVESTIGATION 4: USING LOGICAL STRUCTURES IN PYTHON=
Now that we have added some powerful logical structures to our python scripts, we can make our scripts much more adaptable. Our python scripts can now respond to different situations by executing different code, or repeating the same code several times (e.g. keep asking the user for input until they give us something useful). In this investigation you will write a python script that will prompt a user for a directory to archive, ask them if they want the archive compressed, and (only if they do want compression) what type of compression to apply.
<ol>
<li>In your bin directory, create the file tarchiver.py, and populate with our standard beginning:
<code style="color:#3366CC;font-family:courier;font-size:.9em;">
<br>
#!/usr/bin/env python3<br />
# tarchiver.py<br />
# Purpose: Creates a tar archive of a directory<br />
#<br />
# USAGE: ./tarchiver.py<br />
#<br />
# Author: *** INSERT YOUR NAME ***<br />
# Date: *** CURRENT DATE ***<br />
import os<br />
</code>
</li>
<li>Next, add prompts using the '''input()''' function to ask the user for:
<ul>
<li>The directory they wish to archive.</li>
<li>The name they want to give the archive.</li>
</ul>
Remember to store their responses in variables.</li>
<li>Add a line that uses the values provided by the user to execute a tar command and create and archive of the directory they requested.</li>
<li>Test your script to make sure it works.</li>
<li>Add a third prompt (immediately after the other two prompts and before the tar command), asking the user if they want the archive to be compressed. You'll need an if statement to run your tar command with gzip compression if they answered yes.</li>
<li>Test your script to make sure it works.</li>
<li>Add a fourth prompt asking the user what type of compression they want (present them with gzip, bzip2, and xzip as options). Note that this prompt should only be shown if the user opted for compression (if they don't want compression, there is no point asking what type they don't want).</li>
<li>Expand the if statement around your actual tar command to use whichever type of compression the user asked for.</li>
<li>Test your script to make sure it works.</li>
<li>Test your script again, but feed it nonsense data (e.g. answer 'very much so' instead of 'y' or 'n' when prompted about compression).</li>
<li>Add loops around your prompts for whether or not the user wants compression, and the compression type to make the script repeat each prompt until the user gives a response your script can actually use. Don't worry about doing anything with the archive name or path.</li>
<li>Now test your script again, with good data and with nonsense.</li>
<li>When you are confident your script works, you are ready to submit the lab.</li>
</ol>
= LAB 3 SIGN-OFF (SHOW INSTRUCTOR) =
Follow the submission instructions for lab 3 on Blackboard.
{{Admon/important|Time for a new backup!|If you have successfully completed this lab, make a new backup of your virtual machines as well as your host machine.}}
'''Perform the Following Steps:'''
# Make certain that your '''c7host''' and '''centos3''' VMs are running.
# Switch to your <u>'''c7host'''</u> machine, open a shell terminal as a regular user, and change to the directory: '''~/bin'''
# Download the Lab 3 check script: <b><code><span style="color:#3366CC;font-size:1.2em;">wget https://raw.githubusercontent.com/OPS245/labs/main/lab3-check.bash</span></code></b><!--<br>For Andrew's sections use this script instead: <b><code><span style="color:#3366CC;font-size:1.2em;">wget http://littlesvr.ca/ops245/lab3-check-andrew.bash</span></code></b>-->
# Give the '''lab3-check.bash''' file execute permissions (for the file owner).
# Run the shell script with <code>sudo</code>, and if any warnings appear, fix the issues noted by the script and rerun the check until you receive the "Congratulations!" message.
# Arrange proof of the following on the screen:<br><span style="color:green;font-size:1.5em;">✓</span> '''centos3''':<blockquote><ul><li> Archived files '''created'''</li><li>Archive files '''restored'''</ul></blockquote><span style="color:green;font-size:1.5em;">✓</span> '''c7host''':<blockquote><ul><li> '''One repository added''' for yum</li><li>Run the '''lab3-check.bash''' script (must have all <b><code><span style="color:#66cc00;border:thin solid black;font-size:1.2em;"> OK </span></code></b> messages)</li></ul></blockquote><span style="color:green;font-size:1.5em;">✓</span> '''Lab 3''' logbook pages filled out.
# Upload a screen of the proof from the previous step, along with the file generated by '''lab3-check.bash''', your log book, and your '''tarchiver.py''' script to blackboard.
= Practice For Quizzes, Tests, Midterm & Final Exam =
#What is the purpose of booting into single-user mode?
#List the steps in order to boot into single-user mode.
#List the steps to reset a forgotten root password.
#What is the difference between a .tgz file and a .tar.gz file? What do these stand for?
#What is the purpose of a repository?
#What is source code?
#How do you build software from source code?
#What does yum do that compiled source code does not?
#Other than running an installed package, what commands can you issue to verify that the package was installed?
#List the steps to remove a package via yum command.
#List the steps to install a package using the yum command.
#List the steps to add a repository to be used with yum.
#What is the command to list all repositories associated with the yum command?
#What is the command to view all repositories that have been added to-date?
#How do you use the '''sed''' command to modify text?
#What is the '''Here-Document''', and how can it be used in issuing command and shell scripting?
[[Category:OPS245]]
[[Category:OPS245 Labs]]
[[Category:Digital Classroom]]