Home > Articles

Installing Red Hat Linux 7.2

This chapter is from the book

This chapter is from the book

In This Chapter

  • Choosing How to Install Red Hat Linux 

  • Step-by-Step Installation 

  • Login and Shutdown 

This chapter provides a basic guide to installing Red Hat Linux through a short step-by-step installation. Before installing Red Hat Linux, you should have a basic understanding of your system's hardware. This will help ensure that the process of creating a new Linux system is done quickly and efficiently with a minimum of problems. Arm yourself with information about your system beforehand in order to head off potential problems such as choosing partition sizes that are too small or hardware mis-configuration.

It is your job to properly allocate your system's resources, and create a working, stable install. You should know the type of installation to perform beforehand (such as a workstation, server, firewall, gateway, router, development system, and so on). Servers that are designed for a single purpose, such as serving or managing electronic mail will have software, storage, and system requirements different from a simple gateway. Installing and configuring a workstation or development workstation will have different software and storage requirements, which can either lighten the load of or tax CPU, RAM, and storage resources.

Most new users with standalone Red Hat Linux computers will install all the software included with Red Hat Linux and depend on Red Hat's RPM technology to sort out and handle software dependencies (see Chapter 8, "Managing Software and System Resources" for more details about using RPM). Using Linux isn't like living in a house built with a pack of playing cards where one misplaced or missing piece of software can bring down the computer. But crafting an efficient, stable, and working system will require some consideration about the type of software to use.

Planning Partition Strategies

Part of planning a custom system involves implementing a partitioning strategy based on the knowledge of existing hardware before the install. And in corporate or enterprise-level environments, part of the planning should also take into consideration future expansion or evolution of the system. The idea can be to craft a flexible system that might possibly evolve as it is used. Knowing how to allocate software on your hard drive for Linux involves knowing how Red Hat Linux organizes its file system, or layout of directories on storage media. This knowledge will help you make the most out of hard drive space, and in some instances, such as planning to have user directories mounted via NFS or other means, can help head off data loss, increase security, and accommodate future needs. Create a great system, and you'll be the hero of information services. Create a house of cards, and you'll be looking for a new job.

Some questions you should have the best possible (or correct) answers to before installing Red Hat Linux include "How much disk space is required now or in the future?" "Will the system boot just Red Hat Linux or another operating system?" or "How much data needs to be backed up, and how will it be backed up?"

Choosing a Boot Loader

You will also need to know how the system will be booted. Various software packages and schemes can be used. For example, will you use the Linux Loader, LILO, or the GRand Unified Bootloader, known as GRUB? LILO is a small boot loader usually installed in the Master Boot Record of an IDE hard drive, the root Linux partition, or on a floppy disk. This loader (like others) can be used to pass essential kernel arguments to the Linux kernel for use during the boot process. Some arguments include disk geometry, additional network interfaces, or perhaps installed RAM values. LILO uses a configuration file named /etc/lilo.conf. Other boot loaders, such as GRUB, might support boot read-only memory (ROM) or flashed memory chips containing boot-loading code. Yet other approaches supported by some, but not all, PC hardware BIOS include booting via a network. And Linux can also be booted via removable media or a floppy disk.

Note

Red Hat's mkbootdisk command can be used to create boot media while using Linux by using the Linux kernel release number (returned by using the uname -r command) and a specified device, such as: mkbootdisk --device /dev/ fd0 2.4.7-2

Red Hat Linux can also be booted from a DOS session using the LOADLIN program, a DOS PATH to the Linux kernel, and the location of Linux kernel, such as:

LOADLIN c:\KERNEL\VMLINUZ root=/dev/hda2 ro

In this example, the kernel named VMLINUZ is loaded, and the second primary partition of the first IDE hard drive is specified at the root (\) partition of the Red Hat Linux system.

Note

If you find that LOADLIN fails to boot Linux and complains about a large kernel size, you can either try using make bzimage to build a smaller kernel, or rebuild a kernel that relies less on built-in features and more on loadable modules. See Chapter 23, "Kernel and Module Management," for more information.

A good boot loader will support multiple operating systems, the ability to boot different Linux kernels (in order to change the characteristics of a system or easily accommodate new hardware), password protection, custom boot displays, and sane defaults.

Another consideration in using a system hosting one or more operating systems is that some operating systems "don't play well with others" (such as later versions of Windows from Microsoft), and might wipe out MBR settings or might not use the MBR. If you find yourself in this situation, it might be best to turn to commercial boot loader software. If you run into trouble after installing Red Hat Linux, make sure to read the documentation for your boot loader to acquire any diagnostic information. Most boot loaders will report on any problems and the solution might be commonly fixed.

Choosing How to Install Red Hat Linux

Red Hat Linux can be installed in a variety of ways using different techniques and hardware. You should also know how you plan to install Linux before starting in order to devise a policy or perhaps foil subsequent installs for security. For example, installing via a network onto workstations lacking removable media can help increase security to some degree.

Red Hat Linux is typically installed by booting to the install directly from a CD-ROM. Other options include

  • Booting to an install using a floppy diskette

  • Using a hard drive partition to hold the installation software

  • Booting from a DOS command line

  • Booting to an install and installing software over a network using FTP or HTTP protocols

  • Booting to an install and installing software from an NFS-mounted hard drive

How you choose to install (and use) Red Hat Linux depends on your system's hardware, corporate information service policy, or personal preference.

Installing from CD-ROM

Most PCs' BIOS supports booting directly from a CD-ROM drive, and offers an ordering of devices to search for bootable software. Set your PC's BIOS if required, and then insert the CD-ROM and turn on or reboot the PC to install Red Hat Linux. Problems can arise if the CD-ROM isn't recognized by the Linux kernel, but trouble shouldn't occur unless there is hardware failure. (In the past, some CD-ROM drives required a kernel patch, this should no longer be a problem; see Table 3.1 in this chapter, which lists a driver disk image used to support older drives.)

Booting to an Install from DOS

As previously mentioned, a DOS utility such as LOADLIN (or BOOTLIN) can be used to either boot to an install directly from CD-ROM or to load the Red Hat Linux install kernel. See the dosutils directory on the first Red Hat Linux CD-ROM included with this book, and read the README file under the dosutils directory for an overview of the DOS utilities. The directory contains a one-line DOS batch file (.bat file) that can help boot to an install:

loadlin autoboot\vmlinuz initrd=autoboot\initrd.img

In this example, the LOADLIN command will boot the Red Hat Linux install kernel residing under the dosutils/autoboot directory, and then load the installation software to launch an install.

Making an Installation Boot Diskette

Your Red Hat Linux installation can also be started using a boot floppy. Floppy images (.img files) are contained in the images directory on the first Red Hat Linux CD-ROM. Red Hat, Inc. provides a number of images, as listed in Table 3.1.

Table 3.1 Red Hat Linux Boot Images

Name

Description

boot.img

Enable booting using CD-ROM or hard drive partition

bootnet.img

Install via FTP, HTTP, or NFS

pcmicia.img

Boot install using PCMCIA hardware (requires the pcmciadd.img)

drivers.img

Utility image containing various hardware drivers

oldcdrom.img

Support image for booting using old CD-ROM drives

images/pxeboot

Directory containing a PXE-enabled Linux kernel


Most of the images listed in Table 3.1 support booting to an install using either local hardware or using local hardware to install using a network. The pxeboot directory contains a kernel that supports a remote booting protocol named PXE that enables installation or upgrades of network-only PCs. Use of this software requires a properly configured server and local PCs BIOS settings.

The diskettes images can be created using the DOS RAWRITE command or the Linux dd command to create the floppy. The RAWRITE command is used after starting DOS like this:

D:\dosutils\rawrite

You'll need one or more blank diskettes. Follow the prompts to create the images, entering a source filename and a target drive (such as A or B). To create a boot diskette dd, mount the first Red Hat Linux CD-ROM and use the dd command like so:

# dd if=/mnt/cdrom/images/nameofimage.img of=/dev/fd0

This will create a diskette in the DOS drive A. Use /dev/fd1 if you want to use an installed secondary floppy drive. PC notebook users installing via a network or external CD-ROM drive using a PCMCIA adapter might need the pcmcia.img and pcmciadd.img diskettes.

Hard Drive Partition Installation

A hard partition can be used to either boot the Red Hat Linux install or hold the software required from an install. The partition must be large enough to hold .iso images (binary images of a CD-ROM). Copy the images of the first and second Red Hat Linux CD-ROMs in a directory on the local hard drive. If you use this type of install and don't need the required hard drive space later on, a system can be quickly reinstalled from the partition.

The .iso images can be downloaded from Red Hat, Inc. or a mirror FTP site. Images can also be created using Linux utilities such as mkisofs, dd, and the mount command.

To perform this installation, you will need to know the hard drive's device name (such as /dev/hdb), along with the partition number and the name of directory containing the images (such as /dev/hdb1 and /redhat/images; if you simply copy the images to the formatted DOS or Linux partition, you don't need the directory information).

Installing Using a Network

Red Hat Linux can be installed using a local network (or even over the Internet if you have broadband access). Boot your PC to the install, and then choose the type of installation. Installing Red Hat Linux using the File Transfer Protocol (FTP) will require access to an FTP server. You'll need to know the hostname or IP address of the server, along with the path (directory) holding the Red Hat Linux software. Installing Red Hat Linux using a remotely mounted Network File System (NFS) is similar to a hard drive installation, but requires access to an NFS server. You'll need access permission, a permitted IP address or hostname for your computer, the hostname or IP address of the NFS server, and the path to the Red Hat Linux software.

To install Red Hat Linux using HTTP, you will need the hostname or IP address of the remote Web server, along with the directory containing Red Hat Linux. Other installation methods might be variations on network installation or the installation and subsequent use of an alternative Linux distribution (such as a floppy based distribution) to bootstrap to an install.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020