CSC 262

Lab Exercise: Installing Linux

 

In this lab you will install Linux on the second hard drive of one of the lab machines. We will be installing Fedora Core 5, the same Linux distribution used on the classroom machines in the science center. The installation files are available over Smith network, but we will need to boot off a CD initially so you should divide into groups and share the boot CD around. Choose a machine that you like; we will be working with the same computer throughout the semester.

The Linux installation screens are reasonably good at guiding you through the installation process. These notes will provide additional information to get you started, and to help you choose the right options.

Install Checklist

  1. Important! We will be installing on the second hard drive of the B17 lab machines (pushbutton II). Before starting, make sure that the computer is off, and the drive switch on the blue plate is in position II. (Note: Restarting will not work; you have to actually shut down the machine before it will register the new drive.) Please make sure you do not overwrite the regular lab installation on the first hard drive! This makes unnecessary extra work for the computer support staff.
  2. Turn on the computer, and when you see the DELL boot screen hit F2 for setup. If you see a screen asking you to choose an operating system, you have waited too long.
  3. In the setup options, under Boot Order, move the CD drive to the first (top) position. Save and restart.
  4. The computer should now boot off the CD. You will see a screen with some fairly cryptic instructions; because installing off the network is not the usual method, this step is a little less user-friendly. To start the process, type linux askmethod at the prompt.
  5. The install process must first gather some information from you, which will involve a number of screens where you must make one or more choices. In many cases the default is acceptable. The listing below summarizes the recommended choices. You can always go back later if necessary! Items that involve a change from the default are bolded.
    • Language: English
    • Keyboard: US
    • Install from NFS Image
    • Get dynamic IP via DHCP
    • NFS server name: scinix.smith.edu
      Fedora core directory: /usr/local/etc/yum/fedora5/os
    • Partitions: replace all Linux partitions on this machine. You can use the default configuration, but check the box allowing you to review the results.
    • Install the grub bootloader as specified.
    • Leave the network card using DHCP.
    • Time zone is New York.
    • Use the root password supplied in class.
    • Select the software development package, and check the box tune the package selection.
    • Recommended packages to add: KDE, Legacy Software Development, Legacy Software Support, System Tools.
  6. When everything has installed, the system reboots. Choose verbose startup so you can watch what is happening. The operating system is starting up all the services that will be needed during operation. (You can get a similarly detailed view during shutdown, if you like.) You now have a few more choices to make:
    • Accept the license.
    • Make sure the firewall is on, and turn off SSH.
    • SELinux should be set to Enforcing.
    • If you need to set the video parameters, it is a Dell 1703 FP. (Generic 1280x1024 LCD should work also.)
    • Make sure you create an ordinary user account for regular use. You may name it anything you like.
  7. Log in.
  8. Congratulations! You've successfully installed an operating system! If you wish, and you have free space on your hard drive, you can install it on a personal computer as well. The latest distribution can be found online.
  9. Important! When you are finished working on this and all future labs, please restore the machine to drive I so that others can use the labs. (Select drive I, shut down, and power on again.)

Installing and Updating Packages

Once your system is installed, you can still go back and install or update different software packages. Most system software in GNU/Linux is available in packages called RPM files. (RPM used to stand for RedHat Package Manager, but is now used by many other Linux distributions as well.) RPM files are packages that include software, version information, and cryptographic controls to ensure that the contents have not been tampered with (for example, to introduce malicious software as a Trojan horse). There are several tools available for use with RPM files; we will use one called yum.

To install RPM packages, we will need root access. In general it is good policy to log in using a non-root account, and only grab root privileges as required. (Why?) The su -c command provides one way to do this. In the examples below, we will install two packages: the Linux kernel source code, and Qt. Try these out, supplying the root password when prompted. You will periodically be asked for confirmation/permission to continue; unless something seems obviously wrong, you should grant it.

$ su -c 'yum install kernel-devel'
$ su -c 'yum install qt'
$ su -c 'yum install emacs'

Lab Reflections

The lab reflections for this activity don't need to be long; one or two paragraphs will suffice. Read the guidelines and then write prose describing your experience in this lab. (You do not need to enumerate each question; they are intended as guidelines to get you thinking.)