1,576
edits
Changes
no edit summary
[[Category:OPS235]][[Category:OPS235 Labs]]
{{Admon/caution|THIS IS AN OLD VERSION OF THE LAB|'''This is an archived version. Do not use this in your OPS235 course.'''}}
=Logical Volume Management and Software Package Management=
:* Learn how to add and remove software packages on your different Linux systems.
:* Learn how to properly adjust your various Linux file systems by using and managing LVM both graphically (fedora2) as well as command line (fedora3).
== Required Materials (Bring to All Labs) ==
RPM maintains a database of installed software. This information is very useful to system administrators. In Lab 3, you queried that database using RPM with the -q argument. When you query the RPM database, you can separately specify:
:* Which packages you want information aboutto do an <u>operational task</u> (like installing or removing a package), using a '''select-option''':* What <u>information </u> you want about those packages, using a '''query-option'''
'''Perform the following steps:'''
== Investigation 2: How do you install and remove software with RPM? ==
# Change Use the graphical file manager (Nautilus) to change to the directory on your Installation DVD containing . Go to the sub-directory called '''Packages''' and then go to the sub-directory '''l''' (for files beginning with the letter l like the '''lynx''' package). You should see a filecalled: <code>lynx-2.8.7-78.fc16fc17.x86_64.rpm</code># Execute this the following command: <code>rpm -i lynx-2.8.7-78.fc16fc17.x86_64.rpm</code># Issue an RPM query to check that lynx is installed.# ___________________________________________________Record this command in your lab log-book.# Issue this the following command: <code>rpm -e lynx</code># Issue an RPM query to verify that lynx is no longer installed. Record this command in your lab log-book.# ___________________________________________________Move to the appropriate sub-directory for packages that begin with the letter '''b'''.# Issue this the following command: <code>rpm -i BackupPC-3.2.1-7.fc17.x86_64.rpm</code> and note the result
'''Answer the Investigation 2 observations / questions in your lab log book.'''
</ol>
</li>
<li>Issue an RPM query to verify that BackupPC is installed. Record this command in your lab log-book.</li>____________________________________________________
<li>Issue the command: <code>yum remove BackupPC</code></li>
<li>Issue an RPM query to verify that BackupPC is no longer installed. Record this command in your lab log-book.</li>____________________________________________________ <li>Install <code>nled</code> using '''yum'''. Record this command in your lab log-book.</li>____________________________________________________
<li>Issue this command: <code>yum info cups</code></li>
</ol>
'''Answer the Investigation 3 observations / questions in your lab log book.'''
=Logical Volume Management(Introduction)=
== Check Current LVM Information Prior to Performing Investigations ==
lv_swap vg_fedora3 -wi-ao 520.00m
* '''f16host f17host (i.e. "removable hard disk" or "disk pack")'''
Does not use LVM. Confirm this using the same commands used above.
<li>Now we'll make the new device as a physical volume, add it to the volume group, and extend lv_root:</li>
<code>pvcreate /dev/vdb
vgextend vg_fedora3 /dev/vdb
lvextend -l +100%FREE -r vg_fedora3/lv_root</code>
<li>Now rerun the ls/pvs/vgs/lvs/df commands. What has changed and what caused those changes?</li>
'''Answer the Investigation 5 observations / questions in your lab log book.'''
= Updated backup instructions =
If you completed this lab correctly - please make sure you are still making full backups of your virtual machines.
Remember adding a new harddrive to fedora3? You will need to back up that drive as well. If you don't - you will only have half of your machine backed up, which is of no use for a recovery.
= Completing the lab =
{{Admon/important|Time for a new backup!|If you have successfully completed this lab, make a new backup of your virtual machines.}}
'''Notes:'''
# rpm command options
# yum command options
# How to use pvs/vgs/lvs/df/pvcreate/vgextend/lvextend
# Answer to this question "What is the license of the nautilus package?"
'''Arrange evidence for each of these items on your screen, then ask your instructor to review them and sign off on the lab's completion:'''
# Larger <code>/home</code> nled installed on '''fedora2'''.# Listing of Linux commands to perform Investigation #3 the host (via CLIdisk pack - main system f16host).
# Unnecessary/unused packages have been deleted (list at least 4, and show that they are no longer installed).
# Fresh backup of the virtual machines.
= Preparing for Quizzes =
# What is a VG? PV? LV?
# What commands are used to determine VG / PV / LV information?
