Difference between revisions of "OPS235 Lab 4 - Fedora17"
Line 2: | Line 2: | ||
[[Category:OPS235]][[Category:OPS235 Labs]] | [[Category:OPS235]][[Category:OPS235 Labs]] | ||
+ | |||
+ | |||
+ | == Investigation 1: How to Add a PV to an existing VG == | ||
+ | |||
+ | '''Add an additional 2 GB virtual disk to your ''<u>fedora1</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 or other existing storage" is selected. Click on the '''''Browse''''' button, then click on '''''New Volume'''''. | ||
+ | # Give the new virtual disk file a name of <code>'''fedora1b'''</code>, 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;font-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/''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 is designed to encourage the student to research, think, and use some creativity in working around obstacles in order to solve a task. Research methods can include the Internet searches, etc...}} | ||
+ | '''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>}} | ||
+ | |||
+ | '''Answer the Investigation 4 observations / questions in your lab log book.''' | ||
+ | |||
+ | |||
+ | == Investigation 2: How can I use LVM to manage storage on my f16host disk pack? == | ||
+ | '''On your <u>f16host</u> (i.e. "disk pack"), using your choice of the GUI and/or command-line tools:''' | ||
+ | # Create a new logical partition ('''NOT a logical volume!''') - 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. | ||
+ | |||
+ | '''Answer the Investigation 5 observations / questions in your lab log book.''' | ||
= User/Group Management = | = User/Group Management = | ||
− | == Investigation | + | == Investigation 3: The /etc/passwd file == |
# Look at the /etc/passwd file. | # Look at the /etc/passwd file. | ||
Line 16: | Line 59: | ||
# The user IDs of real users (people) are different from the user IDs of system accounts. What is the pattern? | # The user IDs of real users (people) are different from the user IDs of system accounts. What is the pattern? | ||
− | == Investigation | + | == Investigation 4: Adding users == |
{{Admon/note|Use f16host|Perform these steps in the '''f16host''' 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).}} | {{Admon/note|Use f16host|Perform these steps in the '''f16host''' 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).}} | ||
Line 44: | Line 87: | ||
# Add your matrix account user to '''fedora3'''. | # Add your matrix account user to '''fedora3'''. | ||
− | == Investigation | + | == Investigation 5: Managing Groups == |
{{Admon/note|Use fedora1|Perform these steps in the '''fedora1''' virtual machine.}} | {{Admon/note|Use fedora1|Perform these steps in the '''fedora1''' virtual machine.}} | ||
Line 65: | Line 108: | ||
Be sure to record your observations in your lab notes. | Be sure to record your observations in your lab notes. | ||
− | == Investigation | + | == Investigation 6: Deleting users == |
{{Admon/note|Use fedora1|Perform these steps in the '''fedora1''' virtual machine.}} | {{Admon/note|Use fedora1|Perform these steps in the '''fedora1''' virtual machine.}} | ||
Line 79: | Line 122: | ||
− | == Investigation | + | == Investigation 7: Modifying users == |
{{Admon/note|Use fedora1|Perform these steps in the '''fedora1''' virtual machine.}} | {{Admon/note|Use fedora1|Perform these steps in the '''fedora1''' virtual machine.}} | ||
Line 116: | Line 159: | ||
#* nscd (if not using nscd) | #* nscd (if not using nscd) | ||
#* uucp --> | #* uucp --> | ||
− | |||
− | |||
− | |||
Revision as of 15:31, 27 January 2012
Contents
Investigation 1: How to Add a PV to an existing VG
Add an additional 2 GB virtual disk to your fedora1 system, and use it as an additional physical volume:
- Start
virt-manager
. - 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 or other existing storage" is selected. Click on the Browse button, then click on New Volume.
- Give the new virtual disk file a name of
fedora1b
, 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
/dev/vda
and/dev/vdb
. - Record the size of the volume group and the amount of free space led downlight singapore(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
fdisk
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:
pvcreate /dev/vdb1
- Add the new physical volume to the existing volume group:
vgextend nameOfVolumeGroup /dev/vdb1
- Verify that the volume group is larger and has more free space.
Using that additional space, create a separate filesystem for /home
:
- Create the logical volume
lv_home
(1G ext4) - Find a way to move the contents of
/home
onto it. - Change your system configuration so that the new filesystem is mounted on
/home
from now on.
Answer the Investigation 4 observations / questions in your lab log book.
Investigation 2: How can I use LVM to manage storage on my f16host disk pack?
On your f16host (i.e. "disk pack"), using your choice of the GUI and/or command-line tools:
- Create a new logical partition (NOT a logical volume!) - 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.
Answer the Investigation 5 observations / questions in your lab log book.
User/Group Management
Investigation 3: The /etc/passwd file
- 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
- Make sure you know what information each field contains.
- 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?
- What is the numeric user ID (UID) of the root user?
- The user IDs of real users (people) are different from the user IDs of system accounts. What is the pattern?
Investigation 4: Adding users
- 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 ?
- 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/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:
touch foo
- 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.
- Add your matrix account user to fedora3.
Investigation 5: Managing Groups
- 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 not specify it?
- Your anger has subsided. Delete the idiots group.
- Look at /etc/group again and note the change.
Be sure to record your observations in your lab notes.
Investigation 6: Deleting users
- 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
userdel ops235_1
- Delete the user ops235_2 using the same command with the option which removes the home directory of the user.
- Check the contents of the /home directory. What do you notice?
- Check the contents of the /etc/group directory. What do you notice?
Be sure to record your observations in your lab notes.
Investigation 7: Modifying users
- Read the man page for the usermod command. Note which options change the user's full name, primary group, supplementary groups, and shell.
- Add each of your new users to the group ops235 (in other words, add ops235 to each user as a supplementary group).
- Examine
/etc/group
. 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 the
/etc/passwd
file. What has changed? - Be sure to record your observations in your lab notes.
Completing the lab
Arrange proof of the following on the screen:
- Account created on fedora3 matching your Matrix account.
Preparing for the Quizzes
- What is the purpose of
/etc/fstab
? - What did you have to do in order to move the home directories onto a new filesystem? Why?