Temp OPS235 Lab 1

This is a draft only!
It is still under construction and content may change. Do not rely on this information.

OPS235 Lab 1 GNU/Linux Installation - Fedora 16

Introduction

In this lab, you are going to install the Fedora (GNU/Linux Distribution) to your hard disk from DVD.

Although this will be a simple install, you will be required to perform other Fedora installations using Virtual Machines. This main install will be very important, since you need to properly install Fedora in order to run other virtual machines to install other Fedora disributions.

After the installation, you will collect baseline information about your Fedora GNU/Linux system, do some post installation configuration to prepare your system for the remainder of the labs.

Objectives

1. To perform a GNU/Linux installation using the Fedora 16 distribution
2. To obtain network configuration from a DHCP server
3. To investigate information during and after the Fedora 16 installation

Required Materials (Bring to All Labs)

• Fedora 16 LIVE CD - You can burn this onto a CD-R in the Open Lab
• Fedora 16 x_64 Installation DVD - You can burn this onto a DVD-R in the Open Lab
• SATA Hard Disk (in removable disk tray)
• USB Memory Stick (minimum 64M)
• Lab Logbook (to make notes and observations).

Prerequisites

• None (First Lab)

Linux Command Online Reference

Each Link below displays online manpages for each command (via http://linuxmanpages.com):

• rpm
• hostname
• uname
• ps
• ifconfig
• netstat
• route
• nslookup
• wc

Resources on the web

Additional links to tutorials and HOWTOs:

• Fedora Release Notes
• Fedora Installation Guide

Performing Lab 1

Investigation 1 - performing Fedora DVD Install on Hard Drive

1. Insert your removable SATA hard disk in the drive tray.
2. Set your computer's drive selector switch to external (also labelled #4) since we will be installing from DVD.
3. Power up the computer and insert the Fedora 16 Installation DVD into the CD/DVD drive.
4. Wait until the Fedora DVD boots (could take a few moments).

Boot-up Issues (Fedora16) in Seneca's Computer labs
If for some reason, the Fedora16 Installation DVD does not boot:

• Restart the computer, and press the function key F10 to specify the device to boot (eg. DVD drive).
• If the user is prompted for a password, simply press ENTER (without typing any password) at the password prompt.
• You will need to perform this technique to ensure that Fedora boots from the hard drive (in future labs).
• If you have tried this technique, and the Fedora Installation DVD does not boot, you may have to reburn another Fedora Installation DVD.

5. Note the time at the beginning of your installation.
6. When the Fedora16 Installation DVD boots, it will prompt the user to test the media (i.e. DVD) for integrity. Since time is limited for installation in the lab, select SKIP. On the other hand, if the install did not work, then you can test out the integrity of the DVD in the computer lab during your spare time.
7. Select the default language (English) in the next install screen, and click Next.
8. Select the default keyboard layout and Basic Storage Devices in the following installation screens.
9. Set your hostname (name of the computer) to - f16host (one word, no space, all lowercase). Record in your lab logbook why you think it is important to set your hostname to this exact name instead of using another name...
10. Set your time zone to Toronto.
11. Root Password: enter a password of your own choosing. Pick one that is really, really hard to guess to protect your system. (Recommendation: use the first letter and all the punctuation from a favorite phrase or song verse. For example, "To be or not to be, that is the question!" could become the password "Tbontb,titq!").
12. Select Use All Space, to have the entire disk for the current Fedora16 OS.

Previous Contents of Hard Drive will be Erased
If are using an existing removable Hard Disk from a previous course, you must allow the Installation DVD to "wipe" all previous contents prior to proceeding with this lab (no exceptions).

Failure to erase existing contents can cause problems in subsequent labs such as running out of hard disk space...

Other Linux Installs
You may be "hestitant" to want to use the entire disk for just one operating system, but we will be using software that will allow us to run virtual machines for installation of other versions of Fedora and allow them to run at the same time as our main (host) Fedora distribution.

8. When prompted, make certain to select Fresh Install in order to erase any previous contents of the hard disk.
13. You will be prompted to confirm the options that you have chosen prior to performing the DVD install. If you are not certain, you can "Go Back". As soon as you are satisfied with your selections, then click "Write Changes to Disk.
14. Record briefly in your lab logbook what activity occurs during this installation process.
15. Select in the next screen the Graphical Desktop applications, and in the additional repositories section (at the bottom) make certain to select the default for the additional repository items. "Fedora 16 -x86_64 - Updates", then proceed.
16. Add in your lab logbook a brief description of the term "software repository" and what its major purpose serves (what you think it does). We will not add any existing repositories since we are not currently connected to the Internet. Therefore, we will customize the repositories later.
17. Proceed with the installation. This may take some time. Record in your lab log-book the general steps in the installation process (displayed in the dialog box).
18. Write in your lab log-book the time it took to perform this DVD Fedora install.

1. Reboot using the controls on the screen. When the system starts, it will ask you some final configuration questions.
   • Check the License Agreement. What license is used for the Fedora distribution? What activities do have restrictions and obligations?
   • Create a user account for yourself using the same name as your learn account.
   • Set date and time. Normally, you would want to enable Network Time Protocol, but since we will be experimenting with the networking turned off in later labs, leave it disabled.
   • Click on Do Not Send Hardware Profile.
   • Finish the post-installation customization, wait for the login screen to appear, and then login to your Learn account.

Using Superuser Privilege
Throughout this course, you may need to execute commands using the privileges of the the administrative user (username "root", also called the "superuser"). To switch from your account to the root account, type the command: su

After switching user notice and make note of the change in your shell prompt. Also note the difference in output for the whoami and pwd commands.

Whenever this is required, make a note of it, and determine why superuser privilege is required.

When you are finished using the root account type exit to return to your previous account. Avoid using the superuser account unless absolutely necessary, because the superuser account has unlimited privilege and a typo can destroy your system.

In some documentation, you may see the command su - used in place of su. The dash argument causes su to go through the steps that would normally be performed when the root user logs in, including (1) running the startup scripts (such as /etc/profile and /root/.bash_profile and (2) changing to the root user's home directory (/root).

Note that the root user's home directory (/root) is not the same as the root directory of the system (/). It is also in a different directory than the rest of the home directories, which are typically in /home -- the reason for this is that /home is sometimes on a network filesystem shared by another server (as is the case on Matrix), and it's important that the system administrator be able to log in to the system even if the network is not operating normally.

1. Enter the command fdisk -l /dev/sda and describe the output in your log book. The output may be similar to the following:

   Disk /dev/sda: 12.0 GB, 12072517632 bytes
   255 heads, 63 sectors/track, 1467 cylinders
   Units = cylinders of 16065 * 512 = 8225280 bytes
   Device Boot Start End Blocks Id System
   ...

2. Read and study this reading about how to use the fdisk command before you go on to the next step.
3. Review the man page for the fdisk command.

Important/warning!
The following operation will erase the contents of your hard disk. If you have any useful data stored on your disk, you must back it up first or use another hard disk that does not contain useful data on it. Do not plan on sharing the hard disk with the Windows course! You will be doing lots of tasks that may cause you to lose your data.

4. Enter the command fdisk /dev/sda to start the hard disk partition program.
5. At the fdisk command prompt, enter the letter p to print out the current partition table of the hard disk. If there are any partitions, use the d option to delete all of them, starting with the highest partition number first.
6. At the fdisk command prompt, use the n and t commands to create these three partitions:

                 /dev/sda1 - 300MB (primary, Linux Native)
                 /dev/sda2 - the rest of the hard disk (extended)
                 /dev/sda5 - 300MB (logical, Linux Native) 

7. * Use the p option the display the new partition and record it in your log book.
8. Remember to use the w option to write the new partitions information instead of the q option to quit without saving.
9. Enter the command fdisk -l /dev/sda again, and view the partition table to confirm that the partitions were properly created.
10. Exit the fdisk prompt.
11. Close all applications, and shutdown the computer. Make certain to remove the Fedora 16 LIVE CD when prompted.

Answer the Investigation 1 question in your lab log book.

Investigation 2: How do you install Fedora?

Logical Volume Management
Fedora uses a type of storage management called Logical Volume Management (LVM). In LVM, disk partitions are called Physical Volumes (PVs) and provide storage to a Volume Group (VG). This storage is then split into various Logical Volumes (LVs). The advantage to this scheme is that you can change LV size and you can add and remove PVs after installation. For example, you can add a new disk to your system and then increase the size of your existing filesystems using that extra disk space. Please be careful to enter all LVM information accurately, including the VG and LV names. We will investigate and manipulate LVM in future labs.

Installation Time
The installation process will take about 15 minutes to complete when using DVD. Click the Reboot button on the screen to reboot the system after the installation is complete. There is a post installation setup after boot.

1. Set your computer's drive selector switch to external (since we will be booting from LIVE CD), then power up the computer.
2. Insert the Fedora 16 x86_64 Installation DVD into the DVD drive.
3. Reboot the system.
4. After booting from the Installation DVD, at the Welcome Screen choose "Install or upgrade an existing system" to launch the Graphical installation program and select the following options (you can use the media test to verify that your DVD burned correctly -- It will take some time -- otherwise, skip it):
   • Language - English
   • Keyboard Configuration - U.S. English
   • Type of devices: Basic Storage Devices
   • There should only be one storage drive listed - select it
   • If you get a warning that the drive may need to be initialized, it is because your drive is new and contains no partitition table. Select "Re-Initialize"

Answer the Investigation 2 questions in your lab log book.

Forcing the Resolution on the Projector
The podium computers in the lab rooms are connected to a video splitter. This splitter then connects to both the LCD screen on the podium and the projector at the front of the room. However, the splitter prevents the computer from successfully querying the LCD or screen to find the supported resolutions, and Fedora therefore selects a very low (safe) resolution. If you are using a podium system, you can force the native 1680x1050 resolution of the LCD display using this script.

Investigation 3: How many files packages and files are installed on the system?

For the rest of the tasks in this lab, you must login to your system using your Learn account and execute all commands under your learn account. If you get a Permission Denied message when trying to execute a command, then switch to the superuser account by running the command su - and type in the password for "root". Once the intended command is executed, type "exit" to exit from the superuser account and return to your regular Learn account.

Record the commands used and the output generated in each of the following steps:

1. To find all the mount points, enter the command: mount
   • Study the output and record all the mount points in your log book.
2. The name of the installation log file is /root/install.log -- It is an ASCII file (how can you be sure?) and can be viewed with the less command.
3. You can make use of this file to determine how many packages have been installed: complete the following command to count the number of packages listed in the installation log file:
   • grep ________________ /root/install.log | wc -l
4. Using the rpm command: you can also use the following commands to list all the installed packages, and the total number of packages installed:
   • rpm -q -a
   • rpm -q -a | wc -l
   • rpm -qa | wc -l
5. The -q option means query, and the -a option means all (in other words, query all installed software packages). Did you get the same number of packages from the above two methods?
6. Some of the files on your system were installed with the software packages, and some were created by system activity (for example, by creating your Learn account and by logging in). If you know the package name (from the install.log), you can list all the files that were installed from the package by using the following command:
   • rpm -q -l package_name
7. This combines the -q (query) option with the -l (list filenames) option.
8. You can pipe the outupt through wc -l to count the number of lines:
   • rpm -ql package_name| wc -l
9. Using what you learned in steps 3, 4, and 8, get a count of the total number of files installed by all of the software packages on your system.
10. To find out the name that you have assigned to your Linux system, enter the command: hostname
11. To find out the kernel version of your GNU/Linux workstation and the date it was created, enter the command: uname -r
12. To find out all the system processes running on your GNU/Linux workstation, enter the command: ps -ef
13. To capture the list of all the system processes to a file called ps.lst, enter the command: ps -ef > ps.lst
14. Copy the installation log file /root/install.log and the file ps.lst to a USB memory key, or scp to your matrix account as a backup.

Updating Fedora
The Fedora 16 software is updated frequently to add features, fix bugs, and upgrade security. Perform a system update to get the latest versions of the packages installed in Fedora: Start the Firefox web browser, turn off popup window blocking (select Edit>Preferences, then select the Content tab and uncheck the box to Block Popups), then login to SeneNET. Open a terminal and type su to start a shell as root. Enter the command yum update This will download and install all of the packages that have been updated since the installation DVD image was created. If you complete this command at Seneca it should run quite fast as Seneca College hosts a Fedora Repository mirror (a copy of all of the current fedora packages, on a local web server).

Investigation 4: What is a runlevel?

After the kernel boots, it starts a single program, called init. A running instance of a program is called a process -- the init process always has a process ID (PID) of 1. All other processes on the system are started by init, or they are started by processes started by init.

Most current Linux systems use some variation of the init system originally developed for Unix System V (called "sysvinit") or a newer version called "upstart".

These systems employ the concept of "runlevels" -- groups of software that can be selected, so that the system can be run in various modes. In Fedora systems, these runlevels are used:

Runlevel	Description
0	Halt (powers off the system)
1	Single-user maintenance mode, network not running, character-mode display
2	Not normally used - originally meant: Multi-user mode, network not running, character-mode display
3	Multi-user mode, network running, character-mode display
4	Not normally used
5	Multi-user mode, network running, graphical user interface
6	Reboot

Different runlevel systems
Various Linux distributions may use the runlevel numbers differently. For example, on some Debian/Ubuntu systems, the default (standard) runlevel is 2.

In order to implement runlevels, init uses a configuration file and a number of script files:

• /etc/inittab is the configuration file, which sets the default runlevel.
• /etc/rc.d/init.d is a directory of scripts.

In order to determine which of the startup scripts should be executed in each runlevel, the one directory per runlevel is created (/etc/rc.d/rcX.d, where X is the runlevel). This directory is filled with symbolic links to the startup scripts in /etc/rc.d/init.d

1. To find out the value of the runlevel your GNU/Linux system goes into after boot, enter the command: grep initdefault /etc/inittab
2. You should get a single line containing ":" as the field delimiter. The second field stores the value of the runlevel the init process will use after a reboot. Record the output in your log book.
3. A list of processes that should be running at a given runlevel can be found in the directory /etc/rc.d/rcX.d where X is the runlevel. Do a directory listing of that directory and study what files are in there. Pay attention to the first three characters of each file name. They have special meaning to the system. Record your observation in your log book.
4. Make a backup of the file /etc/inittab with the command: cp /etc/inittab /etc/inittab.original
5. Edit the file /etc/inittab and change the default runlevel to 3. Save the change and reboot your system.
6. After the reboot, you should get a "Text Login Screen". Login with your Learn account and type startx at the command prompt. Describe what happens in your log book.
7. Enter the command: runlevel -- this shows the previous and current runlevel. Record the values in your book.

Answer the Investigation 4 questions in your lab log book.

Investigation 5: What is the network configuration?

1. To check the network configuration settings obtained from the DHCP server, run the following commands, describing the output in your log book:
   • ifconfig
   • route
   • netstat -rn
   • nslookup (at the > prompt, enter the word "server" (do not type the quotes) and record the output. Type exit to leave nslookup).
2. Find the following information in the output of the above commands:
   • MAC address (physical or hardware address) of the ethernet network interface
   • The IP address (logical address) assigned by the DHCP server
   • The default route (gateway)
   • The DNS nameserver

Answer the Investigation 5 questions in your lab log book.

Investigation 6: How do You Secure the Grub Boot Loader?

Duplicate UUIDs
Before proceeding, use the mount command to check to see which filesystem is mounted on the mount point /boot. If it is /dev/sda5, it is the wrong filesystem. This may be caused by a duplication of serial numbers which is the result of Lab 1; you can fix this problem with this series of commands:

mkdir /media/sda5 /tmp/sda5-files
umount /dev/sda5
mount /dev/sda5 /media/sda5
cp -v -R /media/sda5/* /tmp/sda5-files
umount /dev/sda5
mkfs -t ext3 /dev/sda5
mount /dev/sda5 /media/sda5
cp -v -R /tmp/sda5-files/* /media/sda5
rm -rf /tmp/sda5-files
mount -a

By default, the Grub boot loader allows anyone with access to the computer at boot time to set the runlevel, or change the boot parameters, which can allow them to influence the init process and which kernel image is loaded. Anyone with access to the boot prompt can therefore bypass security controls and control which software is loaded. For example, rebooting to runlevel 1, known as single user mode, gives the user root priveleges without the need for a password! Obviously, giving a non-administrator this much control can be dangerous, and it is wise to protect the boot loader with a secure password.

We will need to choose a password, encrypt with the grub programs hash utility (called md5crypt), and add the encrypted hash of your password to the grub configuration file, /etc/grub.conf

Do not lose the GRUB password
If you lose the GRUB password you will not be able to change boot parameters when you boot the system. If you need to write it down, put it in a safe place, where no one will be able to tell what it is for.

1. Choose a suitable password.
2. Open the grub program by typing the command: grub
3. At the grub prompt, type in the command: md5crypt
4. When prompted for a password, carefully type in your password. The program will display the encrypted hash of your password. Carefully write down that encrypted hash generated by the program.
5. Type the command: quit to exit the grub program.
6. Open the grub configuration file, /etc/grub.conf for editing. (This file is actually linked to /boot/grub/grub.conf).
7. Carefully add the line: password --md5 password-hash (note: password-hash is the hash you generated with md5crypt) Place this line between the splashimage line and the title line. If there are other lines there, there is no need to remove them. Just insert your password line as a new line.
8. Make sure you have not made a mistake. What you type in must match exactly the output from the md5crypt command.
9. While you are editing the file you should also increase the timeout for grub to automatically boot the default OS. Edit the line timeout=0 to timeout=5 to give us more time to interrupt the process.
10. You should also ensure that the grub boot menu is not hidden. Add a hash sign (#) to the start of the line which reads: hiddenmenu
11. Save the file and exit. Your Grub boot loader is now password protected.
12. Find the section of this article that explains how to change the runlevel at boot time, and read it. Reboot your system, trying to change to runlevel 1 from the boot prompt, and see if the password protection worked.
13. From now on, when you want to change boot parameters when you boot, you must type lowercase p at the boot prompt and enter the required password.

Completing the Lab

Check off the following items before asking your instructor to check your lab:

• Task 1 - Created correct partitions in /dev/sda
• Task 2 - Install GNU/Linux Workstation using Fedora
• Task 3 - Collect system information after installation.
• Task 4 - Customize and configure boot time environment
• Task 5 - Collect network information
• Task 6 - Password protect Grub Bootloader

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:

• Issue command fdisk /dev/sda, and use p command to display partitions
• Grub is password protected.
• Can login with your "learn" account name
• Has all the mount points
• Has the package count
• Has edited the default runlevel
• Has the correct IP address and MAC address
• Find out the default route (gateway)
• IP of the DNS name server
• Name and contact information on your disk pack

Runlevel
Feel free to change your default runlevel to 3 or 5 according to your own personal preference. Note that later labs may assume a particular runlevel.

Preparing for the Quizzes

1. How many packages were installed?
2. How many files (correct to the nearest hundred) were installed?
3. How many mount points were used?
4. How many users were created automatically on your system (do not count your learn account)?
5. What is your learn account's UID and GID?
6. What is your learn account's home directory?
7. What is the home directory for the user "root"?
8. How do you determine the host name of your GNU/Linux workstation?
9. What command can display the NIC's MAC address?
10. Which file contains the default "runlevel" value for your GNU/Linux workstation?

Unbind your MAC address
Before moving your disk pack to another system, unbind your MAC address.