Changes

{{Admon/caution|THIS IS AN OLD VERSION OF THE LAB|'''This is an archived version. Do not use this in your OPS235 course.'''}}=OPS235 Lab 3: LVM / Logical Volume Management and Software Package / User Management=

:* In this lab, you are 're going to learn how to properly adjust your various Linux file system sizes by managing LVM.:

:* Although this will be a simple install, this Fedora Operating System will be a platform for other Virtual Machine Fedora installations (in future labs). Therefore, it is very important that you take the time Learn how to carefully read add and perform ALL steps, and take time remove software packages on your different Linux systems.:* Learn how to check properly adjust your workvarious Linux file systems by using and managing LVM both graphically (fedora2) as well as command line (fedora3).

:* After performing the Fedora16 DVD installation, you will collect baseline information about your Fedora GNU/Linux system, and perform some post installation configuration == Required Materials (Bring to prepare your system for the remainder of the labs.All Labs) ==

==Objectives== #Perform a GNU/Linux installation using the Fedora 16 distribution#Investigate information during and after the Fedora 16 installation#Perform an upgrade after a recent installation  ==Required Materials (Bring to All Labs)== * '''Fedora 16 17 LIVE CD''' - You can burn this onto a CD-R in the Open Lab* '''Fedora 16 x_64 17 x86_64 Installation DVD''' - You can burn this onto a DVD-R in the Open Lab (or burn image onto a DVD+R if you are using the Freedom Toaster).* '''SATA Hard Disk''' (in removable disk tray)* '''USB Memory Stick''' (minimum 64M)* '''Lab Logbook (Lab3 Reference Sheet)''' (to make notes and observations).

* '''None''' (First Completion and Instructor "Sign-off" of Lab)2: [[OPS235 Lab 2]]

 {|width="100%" cellpadding="5"|'''LVM Information Utilities:'''|'''LVM Management Utilities:'''|'''Additional Utilities:'''|- valign="top"|* [http://linuxmanpages.com/man8/rpmvgs.8.php rpmvgs]*[http://linuxmanpages.com/man8/lvs.8.php lvs]* [http://linuxmanpages.com/man1man8/hostnamepvs.18.php hostnamepvs]*[http://linuxmanpages.com/man8/vgdisplay.8.php vgdisplay]*[http://linuxmanpages.com/man8/lvdisplay.8.php lvdisplay]* [http://linuxmanpages.com/man1man8/unamepvdisplay.18.php unamepvdisplay]|*[http://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-system-config-lvm.html system-config-lvm] (Tutorial)* [http://linuxmanpages.com/man1man8/pslvextend.18.php pslvextend]*[http://linuxmanpages.com/man8/resize2fs.8.php resize2fs]* [http://linuxmanpages.com/man8/ifconfiglvcreate.8.php ifconfiglvcreate]*[http://linuxmanpages.com/man8/lvreduce.8.php lvreduce]* [http://linuxmanpages.com/man8/netstatpvcreate.8.php netstatpvcreate]*[http://linuxmanpages.com/man8/vgextend.8.php vgextend]|* [http://linuxmanpages.com/man8/routemount.8.php routemount]*[http://linuxmanpages.com/man8/umount.8.php umount]* [http://linuxmanpages.com/man1man8/nslookupyum.18.php nslookupyum]:* [http://linuxmanpages.com/man1man8/wcrpm.18.php wcrpm]|}

'''Please read this page to get an overview of LVM:'''<br /><br />:* [[Logical Volume Management]] ('''Note:''' It is recommended to return to this guide as a reference when performing the next several investigations):* [http://fedoranews.<br org/alex/tutorial/><br rpm/>Using the RPM Utility]:* [[Logical Volume Management]http://www.centos.org/docs/5/html/yum/ Using the YUM Utility]

=Performing Lab 3Software Package Management =

== State when starting Lab 3 Investigation 1: How do you query the RPM database? ==

At this point, having completed [[OPS235 Lab 3|Lab 3]] you should have <u>roughly</u> the following disk storage setup:<br />('''Note:''' These results are output from the '''vgs''', '''lvs''', and '''pvs''' commands within each virtual machine. You will be using these commands in the following lab investigations)<br /><br /> * '''fedora1'''  This VM has RPM maintains a GUI and no free space in the VGdatabase of installed software. VG #PV #LV #SN Attr VSize VFree vg_fedora1 1 2 0 wz--n- 9.80G 0 LV VG Attr LSize lv_root vg_fedora1 -wi-ao 8.83G lv_swap vg_fedora1 -wi-ao 992.00M PV VG Fmt Attr PSize PFree /dev/vda2 vg_fedora1 lvm2 a- 9.80G 0 * '''fedora2'''  This VM has a GUI and free space in the VG. VG #PV #LV #SN Attr VSize VFree vg_fedora2 1 3 0 wz--n- 14.80G 4.07G LV VG Attr LSize lv_home vg_fedora2 -wi-ao 1.95G lv_root vg_fedora2 -wi-ao 7.81G lv_swap vg_fedora2 -wi-ao 992.00M PV VG Fmt Attr PSize PFree /dev/vda2 vg_fedora2 lvm2 a- 14.80G 4.07G * '''fedora3'''  This VM has no GUI installed. VG #PV #LV #SN Attr VSize VFree vg_fedora3 1 3 0 wz--n- 9.80G 3.83G LV VG Attr LSize lv_home vg_fedora3 -wi-ao 1.00G lv_root vg_fedora3 -wi-ao 4.00G lv_swap vg_fedora3 -wi-ao 992.00M PV VG Fmt Attr PSize PFree /dev/vda2 vg_fedora3 lvm2 a- 9.80G 3.83G * '''f13host (i.e. "disk pack")'''  Four PVs, minimum VG size 60G Single filesystem on vg_main/root, size 50G At least 10G available space in VG 20% of disk space unallocated information is very useful to any partition (min 15G)  {{Admon/note|Recovering VMs|'''Most of these investigations will take place in you virtual machinessystem administrators.''' If you make a significant mistake, your virtual machine may not boot. Remember that you created backups of your virtual machines in In Lab 3, and you can '''restore them if something goes wrong'''.}}  == Investigation 1: How are LVMs are managed using system-config-lvm? =='''Perform this investigation on the VM named ''<u>fedora2</u>''.'''[[Image:Ops235_lab4_1.png|thumb|right|Screenshot of system-config-lvm in Fedora. Click to enlarge.]]# Let's learn to manage or administer our LVM graphically for our Virtual Machine ('''Fedora2''').<br />Fedora provides a tool called <code>system-config-lvm</code> to graphically administer LVM. It will appear on the menu as System>Administration>Logical Volume Management. Verify queried that this package is present, and install it if required (<code>yum install system-config-lvm</code>).# Use this tool to determine the current LVM configuration by clicking on the appropriate element and reading the properties in the right-hand panel -- write down the answers:#* What are the names and sizes of the PVs?#* What is the name and size of the VG?#* What are the names and sizes of the LVs?#* Is there any space in the VG which is not allocated to a LV?# Increase the size of the home filesystem to 2 GB:## Click on the LV containing the home filesystem.## Click on ''Edit Properties''.## Change the size to 2 GB and click ''Ok''.# Create a new 2G LV (LV Properties: linear) containing an ext4 filesystem named lv_archive and mount it at /archive## Click on ''Logical View''.## Click the ''Create New Logical Volume''.## Set the name, size, filesystem, and mount point.## Click ''Ok''.# Backup <code>/etc</code> into <code>/archive</code>#* Copy the files in /etc into the filesystem mounted at <code>/archive</code> (use the graphical tools or the command line. If database using cp, remember to use RPM with the -R option)q argument.# Shrink the size of <code>lv_archive</code> to 1 GB.# Try shrinking <code>/</code> -- what happens? Why? == Investigation 2: How are LVMs are managed using Command-Line Tools ==# You are going to repeat the same LVM management operations (as your did with the ''fedora2'' VM), but When you will using command-line tools in query the '''fedora 3''' VM. Since the fedora3 VM only operates in command-line modeRPM database, you will need to refer to the '''"Logical Volume Management"''' link above.# Write down the exact commands used at each step, and record appropriate command outputcan separately specify:## Determine the current LVM configuration using the <code>pvs</code>, <code>vgs</code>, and <code>lvs</code> command.## Grow the home filesystem to 2G using the command <code>lvextend</code> and <code>resize2fs</code>.## Create a new 2G LV containing an ext4 filesystem and mount it at /archive (use <code>lvcreate</code>, <code>mkfs</code>, <code>mount</code>, edit the file <code>/etc/fstab</code>, and then reboot to confirm automatic mount).## Copy the contents of <code>/etc</code> into <code>/archive</code>.## Shrink <code>lv_archive</code> to 1G (use <code>umount</code>, <code>resize2fs</code>, <code>lvreduce</code>, and <code>mount</code>) == Investigation 3: How can a PV be added * Which packages you want to do an existing VG? =='''Add an additional 2 GB virtual disk to your ''<u>fedora1operational task</u>'' system, and use it as an additional physical volume:'''# Start <code>virt-manager</code>.# Shutdown ''fedora1'' if it is running.# Open the console window for ''fedora1''.# Select the menu option View>Details.# Click ''Add Hardware'' button at the bottom left-hand corner.# In the ''Adding new virtual hardware'' window that appears, select a Hardware Type of ''"storage"'' and click ''"Forward"''.# Make certain option "Managed (like installing or other existing storage" is selected. Click on the ''Browse'' button, then click on ''New Volume''.# Give the new virtual disk file removing a name of <code>fedora1b</code>package), using a format of ''raw'', with a ''Max Capacity'' and ''Allocation'' of 2000 MB. Click ''Finish''.# Select the new virtual disk file ''fedora1b.img'' and click ''Choose Volume''.# Select a device type of ''Virtio Disk''.# Finish creating the new virtual disk by clicking ''Forward'' and then ''Finish''.# Boot the system. You should now have both <code>/dev/vda</code> and <code>/dev/vdb</code>.# Record the size of the volume group and the amount of free space <span class="plainlinks">[http://www.inleds.com/products/?cid=2<span style="color:black;fontselect-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"> led downlight singapore</span>](Hint: use a command that you learned in a previous lab).# Partition /dev/vdb with a single partition that fills the whole disk.# Check the messages printed when <code>fdisk</code> exits -- you may need to reboot the system in order for the new partition table to take effect.# Run this command to format the physical volume: <code>pvcreate /dev/'option'vdb1''</code># Add the new physical volume to the existing volume group: <code>vgextend ''nameOfVolumeGroup'' /dev/vdb1</code># Verify that the volume group is larger and has more free space. {{Admon/note|Think!|The next part of this investigation requires some research, thought, and creativity.}}'''Using that additional space, create a separate filesystem for <code>/home</code>:'''# Create the logical volume <code>lv_home</code> (1G ext4)# Find a way to move the contents of <code>/home</code> onto it.# Change your system configuration so that the new filesystem is mounted on <code>/home</code> from now on. {{Admon/tip|SELinux relabelling may be required|Your system may report that the files are not present in the new /home filesystem when they are clearly there. This is due to the Security-Enhanced Linux system (SELinux) preventing access to the files, because the files were tampered with (moved) and are no longer recognized as home directory content. You can fix this problem by restoring the file context labels so that SELinux accepts the files as valid home directory content: <code>restorecon -r /home</code>}} == Investigation 4: How can I use LVM to manage storage on my disk pack? =='''On your * What <u>f13hostinformation</u> (i.e. "disk pack")you want about those packages, using your choice of the GUI and/or command-line tools:'''# Create a new logical partition ('''NOT a logical volume!query-option''') - minimum 5G, leaving at least 10G free space in the extended partition.# Add that partition as a PV into the existing VG (using the commands you used in the previous investigation).# Grow the root filesystem to fill the available space. = Package Management =

== Investigation 5'''Perform the following steps: How do you query the RPM database? =='''

RPM maintains a database of installed software. This # Using information is very useful to system administrators. In Lab 3, you queried that database using RPM with the -q argument. When you query from the RPM databaseman page for <code>rpm</code>, you can separately specifyfill in this information:* Which packages you want information about, using a select-option* What information you want about those packages, using a query-option

Steps: 1. Using information from the man page for <code>rpm</code>, fill in this information:{|width="100%" border="1" cellpadding="5"

!Is this a select-option Select or a query-option?!Example command

|Show the package license, packager, URL, description, and other general information.|

| -f '''filename'''|

|'''packagename'''

Make sure that '''Answer the Investigation 1 observations / table contents in your lab notes answer the Investigation 5 questionlog book.'''

== Investigation 62: 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-28.fc13fc17.x86_64.rpm</code># Execute this the following command: <code>rpm -i lynx-2.8.7-28.fc13fc17.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.0-137.fc13fc17.noarchx86_64.rpm</code> and note the result

'''Answer the Investigation 6 question2 observations / questions in your lab log book.'''

== Investigation 73: How do you install and remove software with ''yum''? ==

# <ol> <li value="2">Issue the command: <code>yum install BackupPC</code> and answer <code>y</code> to the question about installation.#* <ol type="a"> <li>Where did ''yum'' get the BackupPC software?</li>#* <li>Why could ''yum'' install BackupPC when rpm couldn't?</li> </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>::* Based on the result, do you think that cups is a useful package for your system? If not, try removing it.# <ol> <li value="8">Unused and unneeded software can present a security risk and ties up disk space needlessly. Find at least 4 other packages that you're not using on your system, and remove them. Be careful to ensure that removing those packages does not also remove other software that you do need.</li></ol> '''Answer the Investigation 3 observations / questions in your lab log book.''' =Logical Volume Management (Introduction)=

Answer == Check Current LVM Information Prior to Performing Investigations == '''LVM''' ('''Logical Volume Management''') is used to manage hard disk drives / partitions for Unix/Linux systems. LVM provides more flexibility than just working with hard disks / hard disk partitions. '''Volume Groups''' are areas used to define '''Physical Volumes''' (i.e. hard disks, disk partitions, or other forms of storage devices). '''Logical Volumes''' are then used to relate directories (mount points) to a specific physical volume or for a "range" or "span" of physical volumes. Therefore, LVM allows more flexibility and growth potential for Linux systems (for example, having Logical volumes span multiple hard disks). Fedora uses LVM by default upon installation. Other Linux distributions may provide the capacity to install LVM, or later install and then use Logical Volume Management. '''Although the concept of LVM is simple, it takes practice and preparation (or "thinking ahead") in order to correctly use this valuable tool'''. It is important for students to gain an understanding of LVM, and how to manage their file-systems using LVM. It is recommended for students to read the following resource prior to this lab and/or return to the following resource while performing this lab: [[Logical Volume Management]] At this point, having completed [[OPS235 Lab 2|Lab 2]] you should have roughly the following disk storage setup:<br />('''Note:''' These results are output from the Investigation 7 question'''vgs''', '''lvs''', and '''pvs''' commands that provide volume group, physical volume and logical volume information for each of the virtual machines that you created in lab2. Before proceeding, check these values with your own system to see if you are generally "on the right track".<br /><br /> * '''fedora1'''  VG #PV #LV #SN Attr VSize VFree vg_fedora1 1 2 0 wz--n- 9.50g 0

= User PV VG Fmt Attr PSize PFree /Group Management =dev/vda3 vg_fedora1 lvm2 a-- 9.50g 0

== Investigation LV VG Attr LSize Origin Snap% Move Log Copy% Convert lv_root vg_fedora1 -wi-ao 8: The /etc/passwd file ==.03g lv_swap vg_fedora1 -wi-ao 1.47g

{{Admon PV VG Fmt Attr PSize PFree /note|Use f13host|Perform these steps in the '''f13host''' systemdev/vda3 vg_fedora2 lvm2 a-- 14. Due to a configuration issue, these steps may not work normally in the fedora1 virtual host (previous versions of this lab used fedora1 for this investigation)50g 3.}}25g

# Read the man page for the useradd command.# Create a new user account for each of your pod mates, using their learn account name as a user name. Give each user a password.# Grep the /etc/passwd file for each of the new users.#* What is the home directory of each user?#* What group is each user in?#* What else do you know about each user?#* Where are the passwords stored?# Look at the man page for /etc/shadow using the command man 5 shadow#* Grep the /etc/shadow file for each of the new users.#* Make note of this information. # Create two new dummy users, ops235_1 and ops235_2.# Investigate the home directory of one of your new users.#* What files are there? Be sure to include hidden files.#* What do you think these files are used for <span LV VG Attr LSize Origin Snap% class="plainlinks">?#* How does the operating system determine which files are created in a new home account? The answer can be found here: http://www.linuxhowtos.org/TipsMove Log Copy%20and%20Tricks/using_skel.htm#* Look at the files (including hidden files) in the template directory referred to in the article. Compare them to what is in a home directory for a new user. What do you notice?#* Create a new file in this directory with the following command: <code>touch foo</code> Convert#* Create a new user named foobar, with the option to automatically create a home directory lv_home vg_fedora2 -wi-ao 1.97g #* Look at the contents of foobar's home directory lv_root vg_fedora2 -wi-ao 7. What do you notice?81g # Be sure to record your observations in your lab notes lv_swap vg_fedora2 -wi-ao 1.47g

{{Admon/note|Use fedora3|Perform these steps in the * '''fedora3 (Note: This VM has no GUI installed)''' virtual machine.}} VG # Add your matrix account user to '''fedora3'''PV #LV #SN Attr VSize VFree vg_fedora3 1 3 0 wz--n- 9.51g 0

{{Admon/note|Use fedora1|Perform these steps in the LV VG Attr LSize Origin Snap% Move Log Copy% Convert lv_home vg_fedora3 -wi-ao 1.00g lv_root vg_fedora3 -wi-ao 8.00g lv_swap vg_fedora3 -wi-ao 520.00m * '''fedora1f17host (i.e. "removable hard disk" or "disk pack")''' virtual machine.}}

# Read the man page for the groupadd and groupdel commands.# Note which option allows you to set the Group ID number (GID) when you create a new group.# Examine the file /etc/group#* Which values of GID are reserved for system accounts?#* Which values of GID are reserved for non-system user accounts?#8 What is the lowest available GID number for non-system users?#* What is the default group name of a new user?#* Add a new group named ops235 with a GID of 600.#* You are angry at some irresponsible users on your system.#** Add a new group named idiots.#** Look at /etc/group and note the GID of idiots.#** What GID is given to a new group if if you do Does not specify it?#** Your anger has subsideduse LVM. Delete Confirm this using the idiots group.#** Look at /etc/group again and note the changesame commands used above.

Be sure to record {{Admon/note|VM Backups and Recovery|Most of these investigations will take place in your virtual machines. If you make a significant mistake, your virtual machine may not boot. Remember that you created backups of your observations virtual machines in Lab 2, and you can restore them if something goes wrong.<br /><br />'''Remember: if you did not create backups for all of your lab notes.VMs, then you don't have any restoration points to fall-back to!'''|}}

== Investigation 114: Deleting users Extend the size of lv_root using command-line tools ==

{{Admon/note|Use fedora1|Perform these steps this investigation in the '''fedora1''' virtual machinefedora3.}}

# Read Let's say that you have run out of disk space on your computer (fedora3), you need more space on the man page for root filesystem, perhaps to host more webpages or a larger database or new software. What are your options? Getting a replacement harddrive would probably require reinstallation of the userdel command. Note which option automatically removes operating system and backup/restore of the users home directory when that user is deleteddata.

# Delete the user ops235_1 Because we're using the command <code>userdel ops235_1</code># Delete the user ops235_2 using the same command with the option LVM though - we can avoid that. We can add a new harddrive (which removes will serve as a physical volume) to the home directory of the user.# Check the contents of the /home directory. What do you notice?# Check volume group, and extend the contents root logical volume to make use of the /etc/group directorynew available space. What do you notice?

Be sure '''Perform the following operations to record your observations increase the size of lv_root in your lab notes.fedora3:'''

== Investigation 12<ol> <li>Run the following commands and make note of the output: Modifying users ==</li> <code>ls /dev/vd* pvs vgs lvs df -h</code> <li>Open the fedora3 virtual machine console</li> <li>Go to the hardware details view</li> <li>Click "Add Hardware" and add a new storage device of 2GBs, make sure it's a VirtIO disk.</li> <li>Go back to the console view</li> <li>Run the same ls command now, what's changed?</li> <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

{{Admon vgextend vg_fedora3 /note|Use fedora1|Perform these steps in the '''fedora1''' virtual machine.}}dev/vdb

# Read lvextend -l +100%FREE -r vg_fedora3/lv_root</code> <li>Now rerun the man page for the usermod commandls/pvs/vgs/lvs/df commands. Note which options change What has changed and what caused those changes?</li> <li>Among the user's full name, primary group, supplementary groupschanges, note that your root filesystem is now 2GB bigger - and shell.you have not even rebooted your machine!</li></ol>

# Add each of your new users to the group ops235 (in other words, add ops235 to each user as a supplementary group).# Examine <code>/etc/group</code>. What has changed?# Use the usermod command to associate each of your pod mates' full name to their user name, as shown in your text. With each change, examine their entries in ''Answer the <code>/etc/passwd<Investigation 4 observations /code> file. What has changed?# Be sure to record your observations questions in your lab noteslog book.'''

'''Perform this investigation on the VM named ''<!u>fedora2</u>''.'''[[Image:Ops235_lab4_1.png|thumb|right|Screenshot of system-config-lvm in Fedora. Click to enlarge.]]# Let's learn to administer (manage) our LVM graphically for our '''Fedora2''' Virtual Machine.<br />Fedora provides a tool called <code>system-config-lvm</code> to graphically administer LVM. It will appear on the menu as '''Application'''>'''Other'''>'''Logical Volume Management'''. The package may not be installed by default, so you will need to install it by issuing: (<code>yum install system-config- lvm</code>).<ol> <li value="2">Use this tool to determine the current LVM configuration by clicking on the appropriate element and reading the properties in the right-hand panel -- write down the answers: <ol type= Investigation 13"a"> <li>What are the names and sizes of the '''PV'''s?</li> <li>What is the name and size of the '''VG'''?</li> <li>What are the names and sizes of the '''LV'''s?</li> <li>Is there any space in the VG which is not allocated to a LV?</li> </ol> </li> <li>Increase the size of the home file-system to '''2 GB''': Security Tip <ol type="a"> <li>Click on the LV containing the '''home''' filesystem.</li> <li>Click on ''Edit Properties''.</li> <li>Change the size to '''2 GB''' and click ''Ok''.</li> </ol> <li>Create a '''new 2G LV''' (LV Properties: Removing Unnecessary Users linear) containing an ext4 filesystem named lv_archive and Groups mount it at '''/archive''' <ol type="a"> <li>Click on ''Logical View''.</li> <li>Click the ''Create New Logical Volume''.</li> <li>Set the name, size, filesystem, and mount point.</li> <li>Click ''Ok''.</li> </ol> <li>Backup <code>'''/etc'''</code> into <code>'''/archive'''</code></li></ol>::* Copy the files in /etc into the filesystem mounted at <code>/archive</code><br />(use the graphical tools or the command line. If using cp, remember to use the -R option).<ol> <li value="6">Shrink the size of <code>lv_archive</code> to '''1 GB'''.</li> <li>Try shrinking the home file-system. What happens? Why?</li></ol>

{{Admon/note|Use fedora1|Perform these steps in the '''fedora1Answer the Investigation 5 observations / questions in your lab log book.''' virtual machine.}}

There is no set list If you completed this lab correctly - please make sure you are still making full backups of users we can safely remove. The requirements of each system varies greatly, and it is up to the administrator to know these requirements, and understand which accounts can be removed. However, the list we provide here can usually be removed, unless their services are specifically requiredyour virtual machines.

# Before attempting the following, make backup copies of your /etc/passwd and /etc/group files, in case we delete Remember adding a user or group new harddrive to fedora3? You will need to back up that is essential to our systemdrive as well. If you don's operation.# Carefully remove the following users from t - you will only have half of your systemmachine backed up, if they exist: #* games#* gopher#* lp (if no printer which is installed)#* news#* nfsnobody#* nscd (if not using nscd)#* uucp# Carefully remove the following groups from your system, if they exist: #* games#* gopher#* lp (if of no printer is installed)#* news#* nfsnobody#* nscd (if not using nscd)#* uucp -->use for a recovery.

{{Admon/important|Time for a new backup!|If you have successfully completed this lab, make a new backup of your virtual machines. Remember to also make a backup of the new second virtual disk drive on }} ''fedora1'Notes:' -- you now have two virtual disks on ''fedora1'', and therefore two image files, and therefore will need two backup files.}}# 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 proof evidence for each of the following these items on the your screen:# Two PVs , then ask your instructor to review them and sign off on the lab's completion:''fedora1'''.# Separate <code>/home</code> filesystem nled installed on the host (on an LVdisk pack - main system f16host) in '''fedora1'''.# Larger <code>/home</code> on '''fedora2''' and '''fedora3'''.

= Preparing for the Quizzes =