How To Install Software In Linux Redhat

C H A P T Due east R 3

Installing Red Hat Enterprise Linux iii Software

This affiliate describes how to install and update Cherry-red Chapeau Enterprise Linux 3 Software on Sun Fire V20 and Sun Burn down V40z servers. Any differences in procedure between the ii servers are noted.

Note - The arrangement-administration procedures in this affiliate are intended for users with at to the lowest degree basic Linux administration experience.

Notation - You can use the Sunday Installation Banana CD to assistance you install the operating system. The assistant too takes care of upgrading the SCSI and Network drivers for your server.

This chapter is organized into the post-obit sections.

Installing Red Lid Enterprise Linux 3 Software From CDs.
Installing Cerise Hat Enterprise Linux 3 Software From a Network.
Updating the Operating Organisation and Drivers.

Installing Red Hat Enterprise Linux 3 Software From CDs

The tasks for installing Reddish Hat Enterprise Linux three software from CDs consist of the following procedures.

i. Install the Red Hat Enterprise Linux 3 software. See Installing the Software.

two. Update the Red Chapeau Enterprise Linux 3 software. Meet Updating the Operating System and Drivers.

Required Items

The CD installation procedure requires the following items.

A Sun Fire V20z or Sun Fire V40z server equipped with:

A CD-ROM or DVD-ROM drive
A PS/ii keyboard
A PS/2 mouse (optional, non used for installation)

Monitor
Ruby Hat Enterprise Linux 3 Media CD Set (As, ES, or WS version)

Installing the Software

Note - If you are using the Dominicus Installation Assistant CD, you begin at Footstep 5.

Note - This process provides the steps for a text-fashion installation. The GUI mode combines several of these steps into ane screen.

1. Connect the keyboard and monitor to the appropriate connectors on the Sun Burn down V20z or Sun Fire V40z server.

2. Power on the server and insert the Blood-red Hat Enterprise Linux 3 CD 1 into the CD tray.

The server will boot off of the CD and brandish a boot: prompt.

3. At the boot: prompt, type the following command:

boot: linux text

iv. When prompted to test the CD media, select OK to exam the media or select Skip to bypass the media examination.

After the CD media exam (if you choose to run it), the Anaconda installer starts. This takes a few minutes.

five. At the Welcome screen, select OK.

6. Make the following selections when prompted:

a. Select the appropriate language.

b. Select your keyboard type.

c. Select No-mouse if you practise not have a mouse connected, or verify that the mouse you lot have attached has been properly detected.

7. When prompted for disk segmentation, select Autopartition.

A dialog box appears, prompting you to choose whether you want to keep the existing partitions.

8. Select 1 of the following options in the Autopartition dialog box:

Remove all Linux partitions on this server: Select this option if you can dual-kick your server with another OS, and want to replace but the Linux partitions.
Remove all partitions on this server: Select this choice if you want to use the entire disk and remove whatsoever OSs that might be installed.
Go along all partitions and use existing free space: Select this option if y'all accept installed other OSs and would similar to go along them available.

9. If yous chose Remove all partitions on this server, the organisation displays a alarm virtually data beingness removed from the drives. Select Aye.

10. On the Partitioning screen, tab to OK and press Enter.

You at present go on through the configuration screens.

a. To change the boot-loader, select Chow or no kicking-loader. Tab to OK and printing Enter.

b. Specify the kernel options. Tab to OK and press Enter.

c. Add a countersign for the bootloader. Tab to OK and press Enter.

d. If you tin can dual-kick your server, select the Os to boot from your boot-loader. Tab to OK and printing Enter.

east. Select the device from which to boot. Tab to OK and printing Enter.

Annotation - If you are performing a GUI-mode installation, the configuration screens appear in the following club:

i. To alter the kicking-loader, select GRUB or no bootloader. Click Next.
ii. If you can dual-boot your server, select the Os to kicking from your boot-loader, and select the device from which to boot. Click Side by side.
three. Add a password for the bootloader. Click Next.

11. The Network Configuration screen appears.

Y'all can apply network settings to the embedded ethernet port(s).

You tin can have the server obtain its network settings over DHCP or you tin enter the static network-configuration information.

The default choice is DHCP.

Notation - In a text-mode installation, you will see one screen for the network settings and and a second screen for entering a host proper name.

In a GUI-mode installation, these options are combined on one screen.

12. The Firewall Configuration screen appears.

You can enable or disable the firewall function. For greater network security, we recommend that you lot enable the firewall function.

The default setting is enabled.

thirteen. In the Language Back up screen, select any other additional languages you need to install.

fourteen. In the Timezone screen, select the timezone in which the server is located.

15. In the Root Countersign screen, enter the superuser password of your choice.

Note - Ensure that you lot remember the countersign. If you lot forget it, you may accept to re-install the operating organisation.

Y'all volition be prompted to choose whether or non to customize the package selection.

16. In the Workstation Defaults screen, check the box to Customize software selection, then select OK.

Note - In a GUI-mode installation, this screen is labelled as Package Defaults.

17. In the Package Grouping Choice setup screen, select the appropriate packages for your environment.

Employ the arrow keys to move the cursor, and then press the Spacebar to check selections.

eighteen. Read the dialog box virtually the installation log, and so select OK.

This installation of the RPMs will have about 10 minutes, depending on what you lot selected for installation. When you are prompted to switch a CD, the installer automatically ejects the CD.

19. When prompted to change CDs, insert the requested CD and press OK.

You might non need all the CDs, depending on which options you selected for installation.

20. If prompted, perform the following steps:

a. Select the default video interface detected by the installer.

b. Identify the connected monitor and select the best match in the installer.

c. At the 10-Customization screen, select Text Interface.

21. Select OK in the Complete dialog box.

The installation is consummate.

22. Keep to Updating the Operating Organisation and Drivers for information on updating the Cerise Hat Enterprise Linux 3 Software.

Installing Red Hat Enterprise Linux 3 Software From a Network

The tasks for installing Red Hat Enterprise Linux 3 software from a networked PXE server consist of the following procedures.

1. Configure your network to support PXE installation. Meet Preconfiguring Your Network to Back up PXE Installation.

2. Create a PXE install image on a system that will be the PXE server, from which the software is downloaded to other systems (PXE clients). Run into Creating a PXE Install Paradigm on the PXE Server.

three. Install the Red Hat software to the PXE clients from the PXE server. Meet Installing the Software from a PXE Server.

4. Update the Red Hat software. See Updating the Operating Arrangement and Drivers.

Required Items

The PXE installation process requires the following items.

The DHCP server that y'all fix in Preconfiguring Your Network to Support PXE Installation, equipped with:

A CD-ROM or DVD-ROM drive
A PS/two keyboard

Monitor
Red Hat Enterprise Linux 3 Media CD Set up (As, ES, or WS version)
Sun Burn V20z and Sunday Fire V40z Servers Documentation and Support Files CD

Creating a PXE Install Image on the PXE Server

This process describes how to create a PXE install image on the same server that is your DHCP server, and so that it will also human activity as your PXE server. The PXE server provides the operating arrangement files to your PXE customer.

Note - For 32-bit users: The extracted directories described in the following procedure are for setting upwardly a 64-bit network image. If you are setting upwards a 32-fleck network image, some files and directories are slightly different.

For 64-bit, the extracted directory is: rhel3_64-pxefiles/
For 32-bit, the extracted directory is: rhel3_32-pxefiles/

All other directories and directions are the same for both 64-bit and 32-flake.

Note - Earlier you lot offset this procedure, verify that your network has been configured every bit described in Preconfiguring Your Network to Support PXE Installation.

1. Insert Crimson Hat Enterprise Linux 3 CD one into your DHCP/PXE server and copy its contents to your PXE server, by typing the commands listed below:

You tin can utilise a different target directory than the /abode/pxeboot/SunFire_rhel3/ directory shown below. The examples in this process use this directory.

# mkdir -p /dwelling/pxeboot/SunFire_rhel3/

# mount /dev/cdrom /mnt/cdrom

# cp -a /mnt/cdrom/RedHat /dwelling house/pxeboot/SunFire_rhel3/

2. Copy the initial ramdisk and kernel from CD 1 into the base of the PXE image with the post-obit commands:

# cp /mnt/cdrom/images/pxeboot/initrd.img \ /home/pxeboot/SunFire_rhel3/

# cp /mnt/cdrom/images/pxeboot/vmlinuz \ /home/pxeboot/SunFire_rhel3/

3. Unmount CD 1 with the following control and remove it from the server:

# umount /dev/cdrom

4. Insert Red Hat Enterprise Linux 3 CD ii into your server and copy its contents to your PXE server, past typing the following commands:

# mount /dev/cdrom /mnt/cdrom

# cp -a /mnt/cdrom/RedHat /dwelling/pxeboot/SunFire_rhel3/

If y'all are prompted whether to overwrite any existing files, type y to overwrite the files.

v. Unmount CD 2 with the following control and remove information technology from the server:

# umount /dev/cdrom

6. Insert Scarlet Hat Enterprise Linux 3 CD 3 into your server and re-create its contents to your PXE server, past typing the following commands:

# mount /dev/cdrom /mnt/cdrom

# cp -a /mnt/cdrom/RedHat /home/pxeboot/SunFire_rhel3/

If you are prompted whether to overwrite whatever existing files, type y to overwrite the files.

seven. Unmount CD three with the following command and remove it from the server: :

# umount /dev/cdrom

8. Insert Red Chapeau Enterprise Linux 3 CD 4 into your server and copy its contents to your PXE server, by typing the post-obit commands:

# mount /dev/cdrom /mnt/cdrom

# cp -a /mnt/cdrom/RedHat /home/pxeboot/SunFire_rhel3/

If you are prompted whether to overwrite whatsoever existing files, blazon y to overwrite the files.

9. Unmount CD 4 with the following command and remove it from the server:

# umount /dev/cdrom

ten. Copy the kickstart file ks.cfg to your PXE server by typing the post-obit command:

# cp /tmp/rhel3_64-pxefiles/ks.cfg /home/pxeboot/SunFire_rhel3/

11. Re-create the SCSI and network drivers from the temporary directory to the directory shown below:

# cp /tmp/rhel3_64-pxefiles/bcm* /home/pxeboot/SunFire_rhel3/ # cp /tmp/rhel3_64-pxefiles/lsi* /home/pxeboot/SunFire_rhel3/

12. On your PXE server, edit and salvage the kickstart file /dwelling house/pxeboot/SunFire_rhel3/ks.cfg so that the nfs line is as follows:

nfs --server n.northward.n.due north --dir /habitation/pxeboot/SunFire_rhel3/

Where north.n.n.due north is the IP address of your PXE server. Double check that the location indicated later --dir is pointing to the acme level of your image.

thirteen. On your PXE server, change and relieve the file /home/pxeboot/pxelinux.cfg/default to add the following entry to information technology:

Note that you lot should type the text block from append ksdevice through ks.cfg as one continuous cord with no returns.

default SunFire_rhel3 label SunFire_rhel3 kernel SunFire_rhel3/vmlinuz

append ksdevice=eth0 console=tty0 load_ramdisk=1 initrd=SunFire_rhel3/initrd.img network ks=nfs: n.due north.northward.n :/home/pxeboot/SunFire_rhel3/ks.cfg

Where n.n.n.n is the IP address of your PXE server.

Notation - For console-based installations, add console=ttyS0,19200 to the append line.

Installing the Software from a PXE Server

This procedure describes how to initiate the request from the target Sun Fire V20z or Sun Fire V40z server to download the boot image file from the PXE/DHCP server and to install the Red Hat Enterprise Linux 3 software onto the target server.

Note - This procedure assumes that you have already preconfigured your network and PXE server install image as described in Preconfiguring Your Network to Support PXE Installation and Creating a PXE Install Epitome on the PXE Server.

1. Connect the PXE client to the same network as the PXE server and power on the PXE client.

The PXE client is the target Sun Fire V20z or Dominicus Fire V40z server to which you are installing Ruddy Lid Enterprise Linux 3 software.

2. When the PXE client prompts you for a network boot, printing the F12 key.

The PXE client connects to the PXE server and attempts to obtain an IP address from the DHCP server.

3. Press the F8 central to begin the downloading of the PXE kick paradigm.

4. If yous are prompted at the kick: prompt, type in the label you gave the epitome in Step thirteen of Creating a PXE Install Image on the PXE Server.

The Red Hat Enterprise Linux iii install prototype downloads onto the target Lord's day Fire V20z or Sun Fire V40z server.

5. To configure the Linux operating system for your server, refer to the transmission that is shipped with your Blood-red Hat Enterprise Linux 3 media kit.

vi. Proceed to Updating the Operating System and Drivers.

Updating the Operating System and Drivers

The CD media may not incorporate the almost up-to-engagement versions of the software. Since the media has been released, at that place take been many updates to the software.

See the following sections for instructions on updating the Crimson Hat Enterprise Linux three software.

Updating Scarlet Hat Enterprise Linux 3 Software
Upgrading SCSI and Network Drivers

Updating Red Hat Enterprise Linux 3 Software

The CD media does not contain the nigh upwardly-to-date versions of the software. Since the media has been released, there take been many updates to the Red Hat Enterprise Linux software. To go on your system protected against security threats and increase stability, you should run the up2date program when the system is fully installed.

Refer to the Ruddy Lid manual included with your Ruby-red Lid Enterprise Linux iii media kit for data about setting upwards the up2date programme. When running up2date, select the kernel packages on the available bundle updates department. After up2date has completed, reboot the server.

Upgrading SCSI and Network Drivers

The kernel that is installed on the organization might not incorporate the optimal drivers that Dominicus Microsystems recommends. Updating the drivers ensures proper system operation.

The instructions below describe how to re-create the latest drivers from the Sun Fire V20z and Sun Fire V40z Servers Documentation and Back up Files CD. Y'all can as well download the commuter RPMs from the product pages for the Dominicus Burn down V20z and Sun Burn down V40z servers. The post-obit URL is valid for both servers:

http://world wide web.dominicus.com/servers/entry/v20z/downloads.html

1. Determine which kernel is currently installed on the system by running the post-obit control:

# rpm -qa | grep ^kernel

The post-obit is an example of the output you might get:

kernel-two.4.21-iv.EL.x86_64 kernel-smp-ii.4.21-four.EL.x86_64 kernel-source-2.iv.21-4.EL.x86_64

In this case, you are running the 2.4.21-4.EL.x86_64 kernel.

2. Insert the Documentation and Support Files CD into the server.

3. Mount the CD and locate the Ethernet and SCSI drivers by typing the following commands:

# mount /dev/cdrom /mnt/cdrom # cd /mnt/cdrom/back up/drivers/rhel3/64/

Note - If you are using the 32-bit version of Red Lid Enterprise Linux, the directory to alter to is:
/mnt/cdrom/support/drivers/rhel3/32/

4. Determine which commuter RPMs correspond to the kernel version, as determined in Step 1.

The filenames of the RPMs contain the kernel version and blazon. Using the example kernel versions shown in Step 1, the Ethernet (bcm5700) and SCSI (lsi) drivers would exist:

bcm5700-7.ane.22_2.4.21_4.EL-rhel3_1.x86_64.rpm bcm5700-smp-7.1.22_2.iv.21_4.EL-rhel3_1.x86_64.rpm lsi-2.05.11_2.4.21_4.EL-rhel3_1.x86_64.rpm lsi-smp-2.05.11_2.iv.21_4.EL-rhel3_1.x86_64.rpm

5. Run the following command to install the RPM files:

# rpm -Uvh /mnt/cdrom/support/drivers/rhel3/64/ bcm5700-drivers .rpm # rpm -Uvh /mnt/cdrom/back up/drivers/rhel3/64/ lsi-drivers .rpm

Where bcm5700-drivers and lsi-drivers refer to the appropriate Ethernet and SCSI driver RPM files, as determined in Step 4.

Notation - Be certain to pick the right compages of the driver for the kernel you lot are running. For case, if you are running the i686 kernel, exist sure to choose the right driver rpm that ends with .i686.rpm.

Note - The post-obit steps are for installing NPS drivers, which include JNET and auto check kernel drivers, too as POCI, a monitoring daemon. This software is required in club to enable hardware monitoring, Os-state reporting and SNMP proxy service to the server'due south service processor.

half-dozen. Locate the NPS RPM on the Documentation and Support Files CD that corresponds to your operating system version and architecture.

The NPS RPM files are located in Os-specific directories within this top level path on the CD: /support/sysmgmt/

7. Install the NPS RPM by typing the following command:

# rpm -Uvh /mnt/cdrom/support/sysmgmt/redhat/rhel3/ nps-V2 .rpm

Where nps-V2 represents the version and compages of the NPS RPM file.

Alternatively, the NPS RPM can be compiled and installed from source past typing the post-obit commands:

# cd /usr/src/redhat

# tar -xvf /mnt/cdrom/support/sysmgmt/src/nps-V2*.tar.gz

# rpm -bb SPECS/nps.spec

# rpm -ivh `find ./RPMS | grep nps`

Notation - Some Linux variants might require the rpmbuild control instead of the rpm command. Cheque with the documentation for your version of Linux.

viii. After successful installation, reboot the system by running the following control:

# reboot