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

You need :* Although this will be a number of hard disk partitions/physical volumes simple install, this Fedora Operating System will be a platform for this installation: '''/dev/sda1 other Virtual Machine Fedora installations (300Min future labs)'''. Therefore, '''/dev/sda2 extended partition'''it is very important that you take the time to carefully read and perform ALL steps, '''/dev/sda5 (300M)''', all created in Lab 1. '''You will create 4 new physical volumes during this lab'''and take time to check your work.

:* After performing the Fedora16 DVD installation, you will collect baseline information about your Fedora GNU/Linux system, do and perform some post installation configuration to prepare your system for the remainder of the labs, manipulate the GRUB configuration, and start using the system.

#To perform Perform a GNU/Linux installation using the Fedora 16 distribution#To perform boot time customization Investigate information during and configurationafter the Fedora 16 installation#To obtain network configuration from Perform an upgrade after a DHCP server#To secure the boot loader by adding password protection#To investigate GRUB boot loader configurationrecent 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(or burn image onto a DVD+R if you are using the Freedom Toaster).* '''SATA Hard Disk ''' (the same one used for Lab 1in removable disk tray)* '''USB Memory Stick ''' (minimum 64M)* '''Lab Logbook (Lab1 Reference Sheet)''' (to make notes and observations).

* '''None ''' (First Lab)

* Each Link below displays online manpages for each command (via [http://linuxmanpages.com/ man pageshttp://linuxmanpages.com]):*:* [http://linuxmanpages.com/man2man8/mountrpm.28.php mountrpm]:** rpm** [http://linuxmanpages.com/man1/hostname.1.php hostname]:** [http://linuxmanpages.com/man1/uname.1.php uname]:** [http://linuxmanpages.com/man1/ps.1.php ps]:** [http://linuxmanpages.com/man8/ifconfig.8.php ifconfig]:** [http://linuxmanpages.com/man8/netstat.8.php netstat]:** [http://linuxmanpages.com/man8/route.8.php route]:** [http://linuxmanpages.com/man1/nslookup.1.php nslookup]:** [http://linuxmanpages.com/man1/wc.1.php wc** grub]

*Additional links to tutorials and HOWTOs::* [http://fedora.redhat.com/docs/release-notes/ Fedora Release Notes]*:* [http://docs.fedoraproject.org/installen-guideUS/ Fedora Installation Guide]** [http://www.gnu.org/software/grub16/manual/html_node/Security.html#Security Protecting Grub]** [http:/Installation_Guide/opensource.sgi.com/LDP/HOWTO/Kernel-HOWTO/grubconf.html Grub Details and Sample Config]** [http://www.aspencrypt.com/crypto101_hash.html One-way Hash Function]** [http://www.dedoimedo.com/computers/grub.html GRUB Tutorial]** [http://www.securitystats.com/tools/password.php Password Security Fedora 16 Installation Guide]

# Insert and secure your SATA hard disk to the removable disk slot.# Power {{Admon/important|Boot-up Issues (Fedora16) in Seneca's Computer labs|If for some reason, the computer.# Insert the Fedora 16 x86_64 Fedora16 Installation DVD into the DVD drive.# Reboot the system.does not boot:

===Investigation 1: How do you install Fedora?==={{Admon/important | Logical Volume Management | Fedora uses a type of storage management called Logical Volume Management (LVM). In LVM* Restart the computer, disk partitions are called Physical Volumes (PVs) and provide storage '''press the function key F10 to a Volume Group specify the device to boot''' (VGeg. DVD drive). This storage :* If the user is then split into various Logical Volumes prompted for a password, '''simply press ENTER''' (LVswithout typing any password)at the password prompt. The advantage :* '''You will need to perform this scheme is technique to ensure that Fedora boots from the hard drive (in future labs)'''.:* If you can change LV size have tried this technique, and you can add and remove PVs after installation. For examplethe Fedora Installation DVD does not boot, you can add may have to burn 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 labsFedora Installation DVD.|}}

{{Admon<ol> <li value="5">Note the time at the beginning of your installation.</note | li> <li>When the Fedora16 Installation Time | The installation process DVD boots, it will take about 15 minutes prompt the user to complete when using 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 DVDin the computer lab during your spare time. Click </li> <li>Select the Reboot button on default language ('''English''') in the next install screen to reboot , and click '''Next'''.</li> <li>Select the system after default '''keyboard layout''' and '''Basic Storage Devices''' in the following installation screens.</li> <li>Set your hostname (name of the computer) to <big>'''f16host'''</big> (one word, no space, all lowercase).<br />Record in your lab logbook why you think it is important to set your hostname to this exact name instead of using another name...</li> <li>Set your time zone to '''Toronto'''.</li> <li'''>Root Password: enter a password of your own choosing'''. Pick one that is completereally, really hard to guess to protect your system. There (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!").</li> <li>Select '''Use All Space''', to have the entire disk for the current Fedora16 OS.</li> </ol>{{Admon/important|Previous Contents of Hard Drive will be Erased|If you are using an existing removable Hard Disk from a post installation setup after bootprevious 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...|}}

Answer <ol> <li value="13">When prompted, make certain to select '''Fresh Install''' in order to erase any previous contents of the hard disk.</li> <li>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'''.</li> <li>Record briefly in your lab logbook what activity occurs during this installation process.</li> <li>Select in the next screen the '''Graphical Desktop''' applications, and in the additional repositories section (at the bottom) accept the default settings, then proceed.</li> <li>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 Investigation 1 question repositories later.</li> <li>'''Proceed with the installation. This may take some time'''. Record in your lab log -bookthe <u>general</u> steps in the installation process (displayed in the dialog box).</li> <li>When installation is complete, a screen will confirm completion, and ask the user to remove the DVD, and reboot the computer. Write in your lab log-book the time it took to perform this DVD Fedora install.</li> <li>Remove the Fedora Installation DVD, and click '''Reboot'''.</li></ol>

{{Admon/tipimportant|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 Boot-up Issues (safeFedora16) resolution. If in Seneca's Computer labs|Each time you are using a podium system, you can force the native 1680x1050 resolution of the LCD display using [httpboot from your removable hard drive://matrix.senecac.on.ca/~chris.tyler/fedora-scripts/1680x1050 this script].}}

===Investigation 2: How many files packages * '''Press the function key F10 and files are installed on specify the hard disk device to boot'''<br />(eg. SATA drive). :* If the user is prompted for a password, '''simply press ENTER''' <br />(without typing any password) at the system?===password prompt.}}

For <ol> <li value="21">When the rest of system starts, set or accept the tasks in this lab, you must login to your system time and date default.</li> <li>Create a user account for yourself using the same name as your Learn learn account , and execute all commands under your learn accountcreate a suitable password (do not forget password!). If </li> <li>Normally, you get a Permission Denied message when trying would want to execute a commandenable '''Network Time Protocol''', then switch to but since we will be experimenting with the superuser account by running networking turned off in later labs, '''leave it disabled'''.</li> <li> Click on '''Do Not Send Hardware Profile'''.</li> <li>Finish the command su post- and type in the password installation customization, wait for "root". Once the intended command is executedlogin screen to appear, type "exit" and then login to exit from the superuser your computer account and return to your regular Learn accountcreated (i.e. your name).</li> <li>Proceed to Investigation 2</li> </ol>

Record '''Answer the commands used and the output generated Investigation 1 observations / questions in each of the following steps:your lab log book.'''

# To find all the mount points, enter the command==Investigation 2: <code>mount</code>#* Study the output and record all the mount points in your log book.# The name of the installation log file is <code>/root/install.log</code> -- It is an ASCII file (how can you be sure?) and can be viewed with the <code>less</code> command. # You can make use of this file to determine how How many packages have been installed: complete the following command to count the number of packages listed in the installation log file:#* <code>grep ________________ /root/install.log | wc -l</code># Using the <code>rpm</code> command: you can also use the following commands to list all the installed packages, and the total number of packages installed:#* <code>rpm -q -a</code>#* <code>rpm -q -a | wc -l</code>#* <code>rpm -qa | wc -l</code># The <code>-q</code> option means query, and the <code>-a</code> option means all (in other words, query all installed software packages). Did you get the same number of packages from the above two methods?# Some of the files on your system were are 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 <code>install.log</code>), you can list all the files that were installed from the package by using the following command:#* <code>rpm -q -l package_name</code># This combines the <code>-q</code> (query) option with the <code>-l</code> (list filenames) option.# You can pipe the outupt through <code>wc -l</code> to count the number of lines:#* <code>rpm -ql package_name| wc -l</code># 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.# To find out the name that you have assigned to your Linux system, enter the command: <code>hostname</code># To find out the kernel version of your GNU/Linux workstation and the date it was created, enter the command: <code>uname -r</code># To find out all the system processes running on your GNU/Linux workstation, enter the command: <code>ps -ef</code># To capture the list of all the system processes to a file called <code>ps.lst</code>, enter the command: <code>ps -ef > ps.lst''</code># Copy the installation log file <code>/root/install.log</code> and the file ps.lst to a USB memory key, or scp to your matrix account as a backup.?==

{{Admon/tip |Updating Fedora|The Fedora 16 software is updated frequently to add features, fix bugs, and upgrade security. Perform a system update to get '''For the latest versions rest of the packages tasks in this lab, you must login to your installed in Fedora: Start system using your Learn account, open a terminal and execute the Firefox web browser, turn off popup window blocking (select following listed Linux commands to obtain information for your lab-logbook''Edit>Preferences'', then select the Content tab and uncheck the box to Block Popups(lab1), then login to SeneNET. Open If you get a terminal and type <code>su</code> Permission Denied message when trying to start execute a shell as root. Enter command, then switch to the '''superuser''' account by running the command <code>yum update</code> This will download '''su -''' and install all of the packages that have been updated type in your password for "root" (since you are the installation DVD image was createdmain administrator for your Fedora system). If you complete this Once the intended command at Seneca it should run quite fast as Seneca College hosts a Fedora Repository mirror (a copy of all of is executed, type "exit" to exit from the current fedora packages, on a local web server)superuser account and return to your regular Learn account.}}

After {{Admon/important|Using Superuser Privilege|Throughout this course, you may need to execute commands using the privileges of the kernel bootsthe administrative user (username "root", it starts a single programalso called the "superuser"). To switch from your account to the root account, called type the command: <code>initsu</code>. 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 After switching user notice and make note of the init system originally developed change in your shell prompt. Also note the difference in output for Unix System V (called "sysvinit") or a newer version called "upstart"the <code>whoami</code> and<code>pwd</code> commands.

These systems employ the concept '''Whenever this is required, make a note of "runlevels" -- groups of software that can be selectedit, so that the system can be run in various modesand determine why superuser privilege is required. In Fedora systems, these runlevels are used:'''

{|class="mediawiki" border="1"!Runlevel!Description|-|0|Halt (powers off When you are finished using the system)|-|1|Single-user maintenance mode, network not running, character-mode display|-|2|root account type exit to return to your previous account. ''Not normally used - originally meant: Multi-user mode, network not running, character-mode display''|-|3|Multi-user modeAvoid using the superuser account unless absolutely necessary, network running, character-mode display|-|4|'because the superuser account has unlimited privilege and a typo can destroy your system.'Not normally used''|-|5|Multi-user mode, network running, graphical user interface|-|6|Reboot|}

{{Admon/note|Different runlevel systems|Various Linux distributions In some documentation, you may use see the runlevel numbers differentlycommand <code>su -</code> used in place of <code>su</code>. For exampleThe dash argument causes <code>su</code> to go through the steps that would normally be performed when the root user logs in, on some Debianincluding (1) running the startup scripts (such as<code>/etc/profile</code> and <code>/root/.bash_profile</Ubuntu systems, code> and (2) changing to the default root user's home directory (standard<code>/root</code>) runlevel is 2.}}

In order to implement runlevelsNote that the root user's home directory (<code>/root</code>) is ''not'' the same as the root directory of the system (<code>/</code>). It is also in a different directory than the rest of the home directories, init uses which are typically in <code>/home</code> -- the reason for this is that <code>/home</code> is sometimes on a configuration file network filesystem shared by another server (as is the case on Matrix), and a number of script files:it's important that the system administrator be able to log in to the system even if the network is not operating normally.}}

In Navigate through your Graphical Fedora system, '''locate and run a terminal program (in order to determine which of issue Linux commands). Issue and record the commands used and the startup scripts should be executed output generated in each runlevel, of the one directory per runlevel is created (<code>/etc/rc.d/rc''following steps:'X'''.d</code>, where '''X''' is the runlevel). This directory is filled with symbolic links to the startup scripts in <code>/etc/rc.d/init.d</code>

# To find out The name of the value of installation log file is <code>/root/install.log</code> -- It is an ASCII file (how can you be sure?) which can be viewed with the runlevel your GNU<code>less</Linux system goes into after boot, enter code> command. # You can make use of this file to determine how many packages have been installed: complete the following commandto count the number of packages listed in the installation log file::: <code>grep initdefault ________________ /etcroot/inittabinstall.log | wc -l</code># You should get a single line containing <ol> <li value=":3" as >Using the field delimiter. The second field stores <code>rpm</code> command: you can also use the value of following commands to list all the runlevel installed packages, and the init process will use after total number of packages installed:</li></ol>:: <code>rpm -q -a reboot. Record the output in your log book.</code># A list of processes that should be running at :: <code>rpm -q -a given runlevel can be found in the directory | wc -l</code>:: <code>rpm -qa | wc -l</etc/rc.d/rc'''X'''.dcode><ol> <li value="4">The <code>-q</code> where '''X''' is option means query, and the runlevel. Do <code>-a directory listing of that directory and study what files are </code> option means all (in thereother words, query all installed software packages). Pay attention to Did you get the same number of packages from the first three characters above two methods?</li> <li>Some of each file name. They have special meaning to the files on your system were installed with the software packages, and some were created by system. Record activity (for example, by creating your observation Learn account and by logging in your log book).# Make a backup of If you know the package name (from the file <code>install.log</etc/inittab with code>), you can list all the files that were installed from the package by using the following command: </li></ol>:: <code>rpm -q -l package_name</code><ol> <li value="6">This combines the <code>cp -q</etccode> (query) option with the <code>-l</inittab /etc/inittab.originalcode> (list filenames) option</codeli># Edit <li>You can pipe the file outupt through <code>wc -l</code>to count the number of lines:</etcli></inittabol>:: <code>rpm -ql package_name| wc -l</code> <ol> <li value="8">Using what you learned in steps 3, 4, and change 8, get a count of the default runlevel to 3. Save total number of files installed by all of the change and reboot software packages on your system.</li># After <li>To find out the rebootname that you have assigned to your Linux system, you should get a "Text Login Screen". Login with enter the command: <code>hostname</code></li><li>To find out the kernel version of your Learn account GNU/Linux workstation and type startx at the date it was created, enter the command prompt. Describe what happens in : <code>uname -r</code></li><li>To find out all the system processes running on your log bookGNU/Linux workstation, enter the command: <code>ps -ef</code></li><li>To capture the list of all the system processes to a file called <code>ps.# Enter lst</code>, enter the command: <code>runlevelps -ef > ps.lst''</code> -- this shows </li><li>Copy the previous installation log file <code>/root/install.log</code> and current runlevelthe file ps.lst to a USB memory key, or scp to your matrix account as a backup. Record </li><li>View the values in section below to learn about and perform an update on your bookfresh Fedora16 install (you may have to find spare time to perform this install if you are running short on lab time). '''Do <u>not</u> proceed to Investigation 3 without performing an update'''.</li></ol>

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

=== Investigation 43: What is the network configuration? ===

#* '''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).<br /><br />

#* '''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 4 question. === Investigation 5: How do You Secure the Grub Boot Loader? ==='''

{{Admon/caution|Duplicate UUIDs|Before proceeding, use '''Answer the <code>mount</code> command to check to see which filesystem is mounted on the mount point <code>/boot</code>. If it is <code>Investigation 3 observations /dev/sda5</code>, it is the wrong filesystemquestions in your lab log book. 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}}'''

{{Admon/important|Do not lose = Completing 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.}}Lab =

# Choose a suitable password. # Open the grub program by typing the command: <code>grub</code># At the grub prompt, type in '''Check off the command: <code>md5crypt</code># When prompted for a password, carefully type in following items before asking your password. The program will display the encrypted hash of instructor to check your password. Carefully write down that encrypted hash generated by the program.# Type the commandlab: <code>quit</code> to exit the grub program.# Open the grub configuration file, <code>/etc/grub.conf</code> for editing. (This file is actually linked to /boot/grub/grub.conf).# Carefully add the line: <code>password --md5 ''password-hash''</code> (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.# Make sure you have not made a mistake. What you type in must match exactly the output from the md5crypt command.# While you are editing the file you should also increase the timeout for grub to automatically boot the default OS. Edit the line <code>timeout=0</code> to <code>timeout=5</code> to give us more time to interrupt the process.# You should also ensure that the grub boot menu is not hidden. Add a hash sign (<code>#</code>) to the start of the line which reads: <code>hiddenmenu</code># Save the file and exit. Your Grub boot loader is now password protected.# Find the section of [http://fedorasolved.org/post-install-solutions/runlevel 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.# From now on, when you want to change boot parameters when you boot, you must type lowercase <code>p</code> at the boot prompt and enter the required password.

Check off the following '''Arrange evidence for each of these items before asking on your screen, then ask your instructor to check your review them and sign off on the lab's completion:'''

* '''Name and contact information on your disk pack''' 

== Preparing for the Quizzes ==