=OPS235 Lab 1 GNU/Linux Installation - Fedora 16=
==Objectives==
#To perform a GNU/Linux installation using the Fedora 16 distribution#To perform boot time customization and configuration#To obtain network configuration from a DHCP server#To secure the boot loader by adding password protection#To investigate GRUB boot loader configuration==Introduction==
==Reference==:* [http:/In this lab, you are going to install the Fedora (GNU/linuxmanpagesLinux Distribution) to your removable hard disk from your burned DVD.com/ man pages]** mount** rpm** hostname** uname** ps** ifconfig** netstat** route** nslookup** wc** grub
* Resources on the web** [http://fedora.redhat.com/docs/release-notes/ Fedora Release Notes]** [http://docs.fedoraproject.org/Although this will be a simple install-guide/ , this Fedora Installation Guide]** [http://wwwOperating System will be a platform for other Virtual Machine Fedora installations (in future labs).gnu.org/software/grub/manual/html_node/Security.html#Security Protecting Grub]** [http://opensource.sgi.com/LDP/HOWTO/Kernel-HOWTO/grubconf.html Grub Details Therefore, it is very important that you take the time to carefully read and perform ALL steps, 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/passwordtake time to check your work.php Password Security]
==Required Material==:* After performing the Fedora16 DVD installation, you will collect baseline information about your Fedora GNU/Linux system, and perform some post installation configuration to prepare your system for the remainder of the labs.
* Fedora 16 x_64 Installation DVD - You can burn this onto a DVD-R in the Open Lab* SATA Hard Disk (the same one used for Lab 1)* USB Memory Stick (minimum 64M)==Objectives==
==Prerequisite==#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
* None (First Lab)
==IntroductionRequired Materials (Bring to All Labs)==
In * '''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 lab, onto a DVD-R in the Open Lab (or burn image onto a DVD+R if you are going to install using the Fedora Freedom Toaster).* '''SATA Hard Disk''' (in removable disk tray)* '''USB Memory Stick''' (minimum 64M)* '''Lab Logbook (GNU/Linux DistributionLab1 Reference Sheet) ''' (to your hard disk from DVDmake notes and observations).
You need a number of hard disk partitions/physical volumes for this installation: /dev/sda1 (300M), /dev/sda2 extended partition, /dev/sda5 (300M), all created in Lab 1. You will create 4 new physical volumes during this lab.==Prerequisites==
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, manipulate the GRUB configuration, and start using the system.* '''None''' (First Lab)
==InstructionsLinux Command Online Reference==Each Link below displays online manpages for each command (via [http://linuxmanpages.com/ http://linuxmanpages.com])::* [http://linuxmanpages.com/man8/rpm.8.php 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]
# Insert ==Resources on the web==Additional links to tutorials and secure your SATA hard disk to the removable disk slotHOWTOs::* [http://fedora.redhat.com/docs/release-notes/ Fedora Release Notes]# Power up the computer:* [http://docs.fedoraproject.# Insert the org/en-US/Fedora/16/html/Installation_Guide/ Fedora 16 x86_64 Installation DVD into the DVD drive.# Reboot the system.Guide]
===Investigation Performing Lab 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, 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.}}
{{Admon/note | Installation Time | The installation process will take about 15 minutes ==Investigation 1: How to complete when using Perform a Fedora DVD. Click the Reboot button Install on the screen to reboot the system after the installation is complete. There is a post installation setup after boot.}}Your Removable Hard Drive ==
# Insert your '''removable SATA hard disk''' into the drive tray.
# Set your computer's drive selector switch to '''external''' (a.k.a ''position #4'').
# Power up the computer and insert the '''Fedora 16 Installation DVD''' into the CD/DVD drive.
# Wait until the Fedora DVD boots (could take a few moments).
# 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"#* Set your hostname to - f16host (one word, no space, all lowercase)#* 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!").#* Disk Partition Setup {{Admon/important|Boot- Specify a Custom Layout, and then set up the installation with this configuration:#** Find your existing 300MB partition (/dev/sda1). Edit this entry so that the mountpoint is /boot and is formatted as an ext3 filesystem.#** Don't touch the other existing 300M partition Issues (/dev/sda5Fedora16).#** Create 4 new LVM Physical Volumes that are 25000 MB in size. Set the File System Type to Physical Volume (LVM). Should be /dev/sda6 to /dev/sda9.#** Create an LVM Volume Group. Set the Volume Group Name to Seneca'''vg_main''' and set the Physical Extent size to '''4MB'''.#** Click on the Add button (within the "Make LVM Volume Group" window) to create a logical volume within that volume group:#*** Mount point / (root), filesystem type ext4, logical volume name '''root''', size 90000MB.#* Say yes to continue without a swap partition.#* Say yes to format /dev/sda1.#* Accept Boot Loader defaults.#* Accept Graphical Desktop and repository defaults.# Proceed with the installation. '''Note how long it takes to perform the installation.'''# Reboot using the controls on the screen. When the system starts, it will ask you s Computer labs|If for 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 Protocolreason, 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.Fedora16 Installation DVD does not boot:
Answer :* Restart the Investigation 1 question 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 your lab log bookfuture labs)'''.:* If you have tried this technique, and the Fedora Installation DVD does not boot, you may have to burn a new Fedora Installation DVD.|}}
{{Admon<ol> <li value="5">Note the time at the beginning of your installation.</tip|Forcing li> <li>When the Fedora16 Installation DVD boots, it will prompt the Resolution on user to test the Projector|The podium computers media (i.e. DVD) for integrity. Since time is limited for installation in the lab rooms are connected to a video splitter, select '''SKIP'''. This splitter On the other hand, if the install did not work, then connects to both you can test out the integrity of the DVD in the computer lab during your spare time.</li> <li>Select the default language ('''English''') in the LCD next install screen on , and click '''Next'''.</li> <li>Select the podium default '''keyboard layout''' and '''Basic Storage Devices''' in the projector at following installation screens.</li> <li>Set your hostname (name of the front 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 the roomusing another name...</li> <li>Set your time zone to '''Toronto'''.</li> <li'''>Root Password: enter a password of your own choosing'''. HoweverPick one that is really, really hard to guess to protect your system. (Recommendation: use the splitter prevents first letter and all the computer punctuation from successfully querying the LCD a favorite phrase or song verse. For example, "To be or screen not to find be, that is the question!" could become the supported resolutionspassword "Tbontb, and Fedora therefore selects a very low (safetitq!") resolution. </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 podium systemprevious 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 force the native 1680x1050 resolution cause problems in subsequent labs such as running out of the LCD display using [http://matrixhard disk space.senecac.on.ca/~chris.tyler/fedora-scripts/1680x1050 this script].|}}
===Investigation 2: How many files packages and files are installed on {{Admon/important|Using Entire Hard Disk|You may be "hesitant" 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 other Fedora installs (while your host system called '''f16host''' is also running).|}}
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.
<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 commands used '''Graphical Desktop''' applications, and in the additional repositories section (at the bottom) accept the output generated default settings, then proceed.</li> <li>Add in each your lab logbook a brief description of the following 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.</li> <li>'''Proceed with the installation. This may take some time'''. Record in your lab log-book the <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>
# To find all the mount points, enter the command: <code>mount<{{Admon/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> important|Boot-- It is an ASCII file up Issues (how can you be sure?Fedora16) and can be viewed with the <code>less</code> command. # 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:#* <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 Seneca's Computer labs| 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 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>), Each time you can list all the files that were installed boot 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 commandremovable hard drive: <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 the latest versions of the packages installed in Fedora: Start the Firefox web browser, turn off popup window blocking (select '* 'Edit>Preferences'', then select Press the Content tab function key F10 and uncheck specify the box hard disk device to Block Popups), then login to SeneNET. Open a terminal and type <code>suboot'''<br /code> to start a shell as root(eg. SATA drive). Enter :* If the command <code>yum updateuser is prompted for a password, '''simply press ENTER''' <br /code> 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 (without typing any password) 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)password prompt.}}
<ol> <li value=== "21">When the system starts, set or accept the time and date default.</li> <li>Create a user account for yourself using the same name as your learn account, and create a suitable password (do not forget password!).</li> <li>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'''.</li> <li> Click on '''Do Not Send Hardware Profile'''.</li> <li>Finish the post-installation customization, wait for the login screen to appear, and then login to your computer account and your created (i.e. your name).</li> <li>Proceed to Investigation 3: What is a runlevel? ===2</li> </ol>
After '''Answer the kernel boots, it starts a single program, called <code>init<Investigation 1 observations /code>questions in your lab log book. 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 ==Investigation 2: How many file packages and files are installed on the init system originally developed for Unix System V (called "sysvinit") or a newer version called "upstart".?==
These systems employ '''For the concept rest of the tasks in this lab, you must login to your installed Fedora system using your Learn account, open a terminal and execute the following listed Linux commands to obtain information for your lab-logbook''' (lab1). 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 your password for "runlevelsroot" -- groups of software that can be selected, so that (since you are the main administrator for your Fedora system can be run in various modes). In Fedora systemsOnce the intended command is executed, these runlevels are used:type "exit" to exit from the superuser account and return to your regular Learn account.
{|class="mediawiki" border="1"
!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
|}
{{Admon/noteimportant|Different runlevel systemsUsing Superuser Privilege|Various Linux distributions Throughout this course, you may use need to execute commands using the privileges of the the runlevel numbers differently. For example, on some Debian/Ubuntu systemsadministrative user (username "root", also called the default (standard"superuser") runlevel is 2.}}To switch from your account to the root account, type the command: <code>su</code>
In order to implement runlevels, init uses a configuration file After switching user notice and a number make note of script files:the change in your shell prompt. Also note the difference in output for the <code>whoami</code> and<code>pwd</code> commands.
* <code>/etc/inittab</code> '''Whenever this is the configuration filerequired, which sets the default runlevel.* <code>/etc/rc.d/init.d</code> is make a directory note of scriptsit, and determine why superuser privilege is required.'''
In order When you are finished using the root account type exit to determine which of the startup scripts should be executed in each runlevel, the one directory per runlevel is created (<code>/etc/rcreturn to your previous account.d/rc'''X'''Avoid using the superuser account unless absolutely necessary, because the superuser account has unlimited privilege and a typo can destroy your system.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 value of the runlevel your GNU/Linux system goes into after bootIn some documentation, enter you may see the command: <code>grep initdefault /etc/inittabsu -</code># 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 used in your log book.# A list place of processes that should be running at a given runlevel can be found in the directory <code>su</etc/rccode>.d/rc'''X'''.dThe dash argument causes <code>su</code> where '''X''' is to go through the runlevel. Do a directory listing of steps 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 would normally be performed when the system. Record your observation root user logs in your log book.# Make a backup of , including (1) running the file /etc/inittab with the command: startup scripts (such as<code>cp /etc/inittab /etc/inittab.originalprofile</code># Edit the file and <code>/etcroot/inittab.bash_profile</code> and change the default runlevel (2) changing to 3. Save the change and reboot your system.# 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.# Enter the command: root user's home directory (<code>runlevel/root</code> -- this shows the previous and current runlevel. Record the values in your book).
Note 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, which are typically in <code>/home</code> -- the reason for this is that <code>/home</code> 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.
}}
Answer the Investigation 3 question.
=== Investigation 4Navigate through your Graphical Fedora system, '''locate and run a terminal program (in order to issue Linux commands). Issue and record the commands used and the output generated in each of the following steps: What is the network configuration? ==='''
# To check The name of the 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 <code>less</code> command. # 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 network configuration settings obtained from installation log file::: <code>grep ________________ /root/install.log | wc -l</code><ol> <li value="3">Using the DHCP server, run <code>rpm</code> command: you can also use the following commandsto list all the installed packages, describing and the output in your log booktotal number of packages installed:</li></ol>:: <code>rpm -q -a</code>::<code>rpm -q -a | wc -l</code>#* ifconfig:: <code>rpm -qa | wc -l</code>#* route<ol>#* netstat <li value="4">The <code>-q</code> option means query, and the <code>-rna</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?</li>#* nslookup <li>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 (at from the <code> promptinstall.log</code>), enter you can list all the files that were installed from the package by using the word following command:</li></ol>:: <code>rpm -q -l package_name</code><ol> <li value="server6" >This combines the <code>-q</code> (do not type query) option with the quotes<code>-l</code> (list filenames) option</li> <li>You can pipe the outupt through <code>wc -l</code> to count the number of lines:</li></ol>:: <code>rpm -ql package_name| wc -l</code><ol> <li value="8">Using what you learned in steps 3, 4, and record 8, get a count of the total number of files installed by all of the outputsoftware packages on your system. Type exit </li><li>To find out the name that you have assigned to leave nslookup).your Linux system, enter the command: <code>hostname</code></li># Find <li>To find out the kernel version of your GNU/Linux workstation and the date it was created, enter the following information in command: <code>uname -r</code></li><li>To find out all the output of system processes running on your GNU/Linux workstation, enter the above commandscommand:<code>ps -ef</code></li>#* MAC address (physical or hardware address) <li>To capture the list of all the system processes to a file called <code>ps.lst</code>, enter the ethernet network interfacecommand: <code>ps -ef > ps.lst''</code></li>#* The IP address (logical address) assigned by <li>Copy the installation log file <code>/root/install.log</code> and the DHCP serverfile ps.lst to a USB memory key, or scp to your matrix account as a backup.</li>#* The default route <li>View the section below to learn about and perform an update on your fresh Fedora16 install (gatewayyou 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>#* The DNS nameserver</ol>
Answer {{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 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 <code>su</code> to start a shell as root. Enter the command <code>yum update</code>''' 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 Investigation 4 questioncurrent fedora packages, on a local web server).}}
=== '''Answer the Investigation 5: How do You Secure the Grub Boot Loader? ===2 observations / questions in your lab log book.'''
{{Admon/caution|Duplicate UUIDs|Before proceeding, use the <code>mount</code> command to check to see which filesystem is mounted on the mount point <code>/boot</code>. If it is <code>/dev/sda5</code>, it is the wrong filesystem. This may be caused by a duplication of serial numbers which == Investigation 3: What 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}}network configuration? ==
By default# To check the network configuration settings obtained from the DHCP server, run the Grub boot loader allows anyone with access to following commands, describing the computer output in your log book:#* '''ifconfig'''#* '''route'''#* '''netstat -rn'''#* '''nslookup''' (at boot time to set the runlevel> prompt, or change enter the boot parameters, which can allow them to influence word "server" (do not type the init process quotes) and which kernel image is loadedrecord the output. Anyone with access Type exit to leave nslookup).<br /><br /># Find 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 following information in the output of the user root priveleges without above commands:#* '''MAC address''' (physical or hardware address) of the need for a password! Obviously, giving a non-administrator this much control can be dangerous, and it is wise to protect ethernet network interface#* '''The IP address''' (logical address) assigned by the boot loader with a secure password. DHCP server#* '''The default route''' (gateway)#* '''The DNS nameserver'''
We will need to choose a password, encrypt with '''Answer the grub programs hash utility (called md5crypt), and add the encrypted hash of Investigation 3 observations / questions in your password to the grub configuration file, /etc/grublab log book.conf'''
{{Admon/important|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.}}
# Choose a suitable password.
# Open the grub program by typing the command: <code>grub</code>
# At the grub prompt, type in the command: <code>md5crypt</code>
# 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.
# Type the command: <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.
== Completing the Lab ==
'''Check off the following items before asking your instructor to check your lab:'''
* '''Task 1 ''' - Install GNU/Linux Workstation using Fedora * '''Task 2 ''' - Collect system information after installation.* '''Task 3 ''' - Customize and configure boot time environmentFedora Updated* '''Task 4 ''' - Collect network information* Task 5 - 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:'''
* 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'''
{{Admon/tip|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 ==
# How many packages were installed?
# How many files (correct to the nearest hundred) were installed?
# How many mount points were used?
# How many users were created automatically on your system (do not count your learn account)?
# What is your learn account's UID and GID?
# How do you determine the host name of your GNU/Linux workstation?
# What command can display the NIC's MAC address?
# Which file contains the default "runlevel" value for your GNU/Linux workstation?
{{Admon/important|Unbind your MAC address|Before moving your disk pack to another system, [[Unbinding MAC Addresses on Fedora|unbind your MAC address]].}}
