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.'''}}=Working with Partitions / User & Group ManagementStorage Setup (prior to starting Lab 4) =
* '''fedora3'''
* Fedora 17 LIVE CD* Fedora 17 x86_64 Installation DVD* SATA Hard Disk '''f17host (in removable i.e. "disk traypack")* USB Memory Stick* Lab Logbook'''
{{Admon/note|Recovering VMs|'''Most of these investigations will take place in you virtual machines.''' If you make a significant mistake, your virtual machine may not boot. Remember that you created backups of your virtual machines in Lab 3, and you can '''restore them if something goes wrong'''.}}
==Linux Command Online ReferenceResources ==Each Link below displays online manpages for each command (via [http://linuxmanpages.com/ http://linuxmanpages.com]):
==Resources on the webInvestigation 1: How are LVMs are managed using Command-Line Tools ==Additional links # You are going to repeat the same LVM management operations (as your did with the ''fedora2'' VM in '''lab3'''), but you will using command-line tools in the '''fedora 3''' VM. Since the fedora3 VM only operates in command-line mode, you will need to tutorials refer to the '''"Logical Volume Management"''' link above.# Write down the exact commands used at each step, and HOWTOsrecord appropriate command output:## 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>)
# 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.# Make certain to remain in In the default section called ''Adding new virtual hardware'' window that appears, select a Hardware Type of ''"Storagestorage"'' and click ''"Forward"''.# Make the following selections in this certain option "StorageManaged or other existing storage" dialog box: [[Image:lab4_inv_1is selected.png|thumb|right|400px|Suggested settings in Click on the ''Browse'Storage'button, then click on '' dialog box to create a 'New Volume''.# Give the new virtual Hard Diskdisk file a name of <code>fedora1b</code>, a format of ''raw'.]] ::* Under ', with a ''Create a disk image on the ComputerMax Capacity's Hard Drive'and '', change the size to Allocation''of 2000 MB. Click '2 GB'Finish''.::* Do not click on # Select the new virtual disk file ''fedora1b.img'' and click 'Select Managed or Other Existing Storage'Choose Volume'' radio button. Since no file pathname is provided, then the system will assign a name in the directory. You<code>/var/lib/libvirt/images/</code>. <!-- CHANGED THIS LINE TO HAVE THE SYSTEM CREATE THE NEW STORAGE FOR THE USER - 2012-02-10 CTyler -->::* # Select Device Type: 'a device type of ''Virtio Disk'''.::* Select Storage Format: # Finish creating the new virtual disk by clicking ''Forward'raw'and then ''::* Click Finish'''FINISH''' to proceed. <ol> <li value="8"># Boot the system. You should now have both <code>/dev/vda</code> and <code>/dev/vdb</code>.</li> <li># Record the size of the volume group and the amount of free space (Hint: use a command that you learned in a previous lab).</li> <li>Use the system-config-lvm tool to add the new virtual disk to the volume group, then extend the size of the root partition using the newly-added space</li><!-- ### SECTION BELOW CHANGED TO LINE ABOVE 2012-02-10 CTyler BECAUSE THE INSTRUCTIONS BELOW ARE NOT GRAPHICAL, AND THE TITLE OF THIS SECTION INDICATES THE USE OF THE GRAPHICAL TOOLS! --><!-- <li>Refer to the following tutorial to use the <code>fdisk</code> command: [http://tldp.org/HOWTO/Partition/fdisk_partitioning.html Partitioning with fdisk]</li> <li>Use the <code>fdisk</code> command to create a primary partition for <code>/dev/vdb</code> with a single partition (number 1) that fills the whole disk.</li> <li># 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.</li> <li># Run this command to format the physical volume: <code>pvcreate /dev/''vdb1''</code></li> <li># Add the new physical volume to the existing volume group: <code>vgextend ''nameOfVolumeGroup'' /dev/vdb1</code></li> <li># Verify that the volume group is larger and has more free space.</li>--></ol> '''Answer the Investigation 1 observations / questions in your lab log book.''' == Investigation 2: How to Add a PV to an existing VG (Command Line Method) == '''The investigation relate to ''<u>fedora3</u>''.''' # Check and record the current state of your storage (use <code>df -h, lvs, vgs, pvs</code>).# Make reference to the following command line resource for assistance: [[Logical Volume Management]]#*'''(Hint:''' First view section on '''Adding a Physical Volume'''. Also, write down the commands first and check prior to issuing them in sequence. This is not looking for the commands necessary to add a physical volume to the virtual machine. It is based on the assumption that the virtual machine already has the physical disk added to the machine via virsh or virt-manager.) # Perform the same operations on ''fedora3'' that you did in the Investigation 1 on ''fedora1'':#* Add a virtual disk to the system.#* Partition the disk (use <code>fdisk</code> - refer to the manpages for details as necessary).#* Make the new partition a physical volume (<code>pvcreate</code>).#* Add the PV to the existing volume group (<code>vgextend</code>).#* Confirm that the VG is now larger (<code>pvs, vgs</code>).#* Extend the root filesystem using the new space (<code>lvextend</code>).#* Confirm that you were successful (<code>lvs, df -h</code>).<!--# You are going to only write in your Lab4 Log-book the Linux commands to perform the same operation that you did graphically in Investigation #1.# You are NOT required to issue these commands on your Fedora3 VM, and it will NOT work since there is no extra room on the VM to create a virtual hard disk --> '''Answer the Investigation 2 observations / questions in your lab log book.''' == Investigation 3: Manually Mounting / Unmounting Filesystems == '''Perform this investigation on the VM named ''<u>fedora2</u>''.''' So far, we have simply assumed that when the Fedora OS boots-up, that its file-system is automatically available. In this investigation, you will learn how file-systems (or portions of file-systems) can be mounted or "connected" to existing file-systems. You will also learn how to unmount (or "disconnect") portions of file-systems from existing file-systems. # Boot-up your '''Fedora2''' VM.# Open a terminal and login as root.# Issue the command called '''mount''' . This command provides information relating to various partitions (logical volumes) and corresponding "mount points" (directories).# Record the information from issuing the <code>mount</code> command for both '''lv_root''' and '''lv_home'''. What commands would issue to quickly obtain this information?# Issue the command '''umount /archive'''. Did anything happen? Issue the '''mount''' command again. Is there any difference with the command output?# View the online man pages for the [http://linuxmanpages.com/man8/mount.8.php mount] command. Issue the <code>mount</code> command with arguments to "re-connect" the device '''/dev/mapper/vg_fedora2-lv_archive''' to the '''/archive''' directory (refer to the section '''Linux Command Online Reference''' above). {{Admon/note|File-System Type Option No Longer Required for Mount Command|When viewing examples online, you may notice that the -t option is used with the mount command to indicate the version or type of file-system to mount.<br />'''The -t option is no longer required for the mount command''', However, it can be used to restrict the mount command so that it only mounts the filesystem ''if'' it of the type listed in the -t option.|}} <ol> <li value="7">Explain how the ''mount'' command would be useful for Linux system administration.</li> <li>Unmount the '''/archive''' directory.</li> <li>Issue a command to verify that he '''/archive''' directory has been unmounted.</li></ol> '''Answer the Investigation 3 observations / questions in your lab log book.'''
= User/Group Management =
== Investigation 54: The /etc/passwd file == '''Perform this investigation on the VM named ''<u>fedora1</u>''.'''
# Look at the /etc/passwd file.
# Make note of the contents of that file.
# Read about the file: http://linux.die.net/man/5/passwd
# Why do you think there are so many users?
# Look at the names of the users. What do you think these user names represent? Are they people?
# The user IDs of real users (people) are different from the user IDs of system accounts. What is the pattern?
{{Admon/note|Use f17host|Perform these steps in the '''f17host''' system. 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).}}
#* What is the home directory of each user?
#* What group is each user in?
#* 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 class="plainlinks">?#* How does the operating system determine which files are created in a new home account? <br />The answer can be found here: http://www.linuxhowtos.org/Tips%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>
#* Create a new user named foobar, with the option to automatically create a home directory.
#* Look at the contents of foobar's home directory. What do you notice?
# Be sure to record your observations in your lab notes.
== Investigation 76: Managing Groups ==
{{Admon/note|Use fedora1|Perform these steps in the '''fedora1''' virtual machine.}}
Be sure to record your observations in your lab notes.
{{Admon/note|Use fedora1|Perform these steps in the '''fedora1''' virtual machine.}}
# Read the man page for the '''userdel''' command. Note which option automatically removes the users home directory when that user is deleted.
# Delete the user ops235_1 using the command <code>userdel ops235_1</code>
# Delete the user <code>ops235_2</code> using the same command with the option which removes the home directory of the user.# Check the contents of the <code>/home</code> directory. What do you notice?# Check the contents of the <code>/etc/group</code> directoryfile. What do you notice?
== Investigation 8: Modifying users ==
# Examine <code>/etc/group</code>. What has changed?
# Be sure to record your observations in your lab notes.
<!-- == Investigation 13: Security Tip: Removing Unnecessary Users and Groups ==
#* nscd (if not using nscd)
#* uucp -->
= Completing the lab =
Arrange proof of the following on the screen:
# Increased volume group size for Two PVs on '''fedora1''' VM.# Correct Linux command sequence to Add a PV to an exiting VG# Separate <code>/etc/fstabhome</code> entry filesystem (on an LV) in '''fedora2fedora1''' VM to automatically mount .<code>/storage</code!-- # Unnecessary accounts and groups have been removed on '''fedora1'''. --># Proof Account created on '''fedora3''' matching your Matrix account.# List contents of ops235 group entry in <code>'''/etc/group</code> in '''fedora1file (ops235 group).# List contents of ''' VM# Proof of pod-mate user account information in <code>/etc/passwd</code> in '''fedora1''' VMfile (created accounts).# Proof Fresh backup of VM backupsthe virtual machines.
= Preparing for the Quizzes =
# What is the reason to extend a Volume GroupVG? PV? LV?# What is the purpose total size of the file called <code>/etc/fstab</code>"main" VG on your system?# How do you ensure that create a file-system is mounted every time that a system is startedLV?# How do you delete an LV?# What are the purposes of How would you add the following files: disk partition <code>/etcdev/passwdsdb7</code>, <code>/etc/shadow</code>, <code>/etc/to your volume group</code>"main"?# How would you increase the size of the root filesystem by 50 MB?# Explain What is the purpose of the <code>/etc/skelfstab</code> directory.?# What do is the terms purpose of <code>UID</code> and <code>GID etc/shadow</code>represent. What is their purpose?# List the steps to create a user account on a system.# List the steps to change user account information on a system.# List the steps in order for users to share file and directory accounts as "same group members".# List the steps to remove a user account. What is required to remove a user account's home directory as well?