Rhel 4 installing services

You will need your enterprise account information to download the updated ISO images. An enterprise account is an account that the customer creates to access Red Hat's support network after purchasing the Red Hat Enterprise Linux media kit. After you obtain the updated. After installing the Red Hat Enterprise Linux software on the server, you might also need to update your system software with patches and packages.

Your Sun server can be equipped with an internal Compact Flash CF card, on which you can install supported Linux or Solaris operating systems. Due to the limited size of the CF card, a full installation might not be possible and some installation modes and functions, such as LVM and swap, are not recommended.

The primary boot device is the device upon which you install and boot the OS. During the boot process, press the F2 key when prompted and navigate to the Boot Device Priority screen to set the internal CF card as the primary boot device. The OS must be installed on one of these device nodes.

To ensure that GRUB gets installed on the boot device, you should perform the following step s :. This process could require approximately 90 clicks. SIA eliminates the need to inventory your system hardware, search out and download Sun-supported drivers, and create a driver CD. Red Hat Enterprise Linux provides both a text mode and an easy-to-use graphical interface for installing and configuring the operating system.

At the boot prompt, you can select the interface that you want to use. Installation from distribution media requires the following items:.

Make a note of the following issues specific to your server:. The server will boot from the CD and display a boot: prompt. Do one of the following at the boot prompt, depending on which type of interface you want to use:. Follow the installation instructions provided with the Red Hat Enterprise Linux Installation Guide to complete the installation of the operating system. You may opt to install this driver after the initial installation of RHEL. If necessary, change the mouse mode to Relative Mouse Mode.

Select Keyboard and Mouse in the Devices menu. When the boot prompt appears, enter:. When prompted for the driver disk, select Yes.

When prompted for the driver disk source, select sda. After the driver is done loading, select No when asked for additional driver. When prompted for testing the CD media before installation, select Skip if you do not want the media test to run. Proceed with Red Hat OS installation, but first take note of the following issues specific to your server:.

Obtaining Updated Media Kits. Preconfiguring your network for PXE installation involves the following procedures:. Continue the basic Red Hat installation setup by following the on-screen instructions and Red Hat documentation. Upon completing the basic Red Hat installation setup, perform the following post-installation tasks:. Configure your system for automatic updates. Refer to Red Hat documentation for more information. If required, download and install the latest errata and bug fixes for RHEL4.

If required, install additional device drivers. After a few seconds, the splash screen for the RHEL5 installation appears. In the Language screen, select the appropriate language, then click OK. In the Keyboard Type screen, select the appropriate keyboard configuration, then click OK. In the CD Found screen, click Skip.

The Red Hat Enterprise Linux 5 screen appears. In the Red Hat Enterprise 5 screen, click Next. In the Disk Partition Setup screen, do the following:. Select the option for Remote Linux partition on selected drives and create default layout or manually partition the disk using the Create custom layout option of Disk Druid.

After completing the basic Red Hat installation setup, perform the following post-installation tasks:. If required, download and install the latest errata and bug fixes for RHEL5. It assumes that you are booting the remote RHEL installation media from one of the following sources:. A message appears prompting you to select the appropriate Ethernet port to perform the network boot.

In the message, select one of the two Ethernet ports listed, then press Enter. After the system boots the RHEL installation program, refer to the following procedures to complete the installation:. A forehead install is one where if you fell asleep and your forehead hit the keyboard, the installation would begin, proceed, and finish without further interaction.

There are a few things you still need to know to optimize your installation. One of those things is your filesystem configuration. How large do you want your base filesystem to be? How many partitions do you want? Do you want separate mount points for certain directories? Are you going to configure a swap space?

Do you want to use LVM vs. Others are static vs. Start by downloading the latest RHEL 8 ISO from the customer portal or from Red Hat Developer , then begin the installation and follow along with the screenshots to explore your options. On the next screen, select your language and click Continue :.

On the Installation Summary screen below , you have your system customization options:. This screen gives you the opportunity to change any or all of the options shown. At a minimum, I suggest that you change the timezone to the one that matches your system's location.

Note: I don't install a GUI on servers because the graphical interface and all of its components are not necessarily something I want on a server system. They take up a lot of space and introduce potential vulnerabilities associated with the extra software.

What you select in the right-hand window depends on your needs. I suggest that you install everything that you want now rather than waiting until the system is installed and online. When installing on an LPAR, the rd. In both cases, the required parameters are the same. All network configuration must now be specified by either by using a parameter file, or at the prompt.

Network configuration must be provided if network access will be required during the installation. If you plan to perform an unattended Kickstart-based installation using only local media such as a hard drive, network configuration can be omitted. Also use the rd. This parameter can be specified multiple times to activate multiple network devices. The bus ID is composed of the channel subsystem ID, subchannel set ID, and device number, separated by dots; the device number is the last part of the bus ID, without leading zeroes and dots.

For example, the interface name will be enca00 for a device with the bus ID 0. At least one storage device must always be configured for text mode installations. The rd. This parameter can be specified multiple times to activate multiple zFCP devices. An example customized generic. Some installation methods also require a file with a mapping of the location of installation data in the file system of the DVD or FTP server and the memory locations where the data is to be copied.

The file is typically named generic. An example generic. A valid generic. Modify this file only if you want to, for example, load a different kernel version than default. When installing in a logical partition LPAR , you can boot from:.

You need to connect to the installation system to continue the installation process. The initial program boot is complete on the IBM Z system, and the command prompt displays:. From a local machine, run the steps below to set up a remote connection with the IBM Z system. Depending on whether or not have you configured the inst.

If you have configured the inst. If you have secured the connection, use the password that you have entered in the previous step or the one that you had set for inst. In the dialog box that follows, select FTP Server , and enter the following information:. If you are running Microsoft Windows operating system, there are several options available, and can be found through an internet search.

A free native Windows port of c called wc also exists. Depending on whether an external security manager, for example RACF, is used, the logon command might vary. Be sure not to use CMS disks such as your A disk often device number as installation targets.

To find out which disks are in use by CMS, use the following query:. Query the available main memory, which is called storage in IBM Z terminology. Your guest should have at least 1 GB of main memory. For example, to query all of the network device types mentioned above, run:. Query available DASDs. Only those that are flagged RW for read-write mode can be used as installation targets:.

Log in and execute the following commands. Use the repl option if you are overwriting existing kernel. Optionally, check whether the files were transferred correctly by using the CMS command filelist to show the received files and their format. It is important that kernel. Customize boot parameters in generic. See Customizing boot parameters for details. Another way to configure storage and network devices is by using a CMS configuration file.

Finally, execute the REXX script redhat. Use a command of the following form:. Select the prepared zipl boot menu entry referring to the Red Hat Enterprise Linux installation program. The digit hexadecimal numbers must be split into two pairs of eight digits each. Boot the FCP device connected with the storage system containing the disk with the following command:.

The digit hexadecimal numbers must be split into two pairs of eight characters each. The IBM Z architecture can use a customized parameter file to pass boot parameters to the kernel and the installation program.

The parameter file can be used to set up networking non-interactively before the installation program Anaconda starts. The kernel parameter file is limited to characters plus an end-of-line character. The parameter file can be variable or fixed record format. Fixed record format increases the file size by padding each line up to the record length. Should you encounter problems with the installation program not recognizing all specified parameters in LPAR environments, you can try to put all parameters in one single line or start and end each line with a space character.

The following example is how to set a DASD online, format it, and make the change persistent. These instructions set a DASD online for the current session, but this is not persistent across reboots. This is only required once for a DASD during its entire lifetime:. When the progress bar reaches the end and the format is complete, dasdfmt prints the following output:. Now, use fdasd to partition the DASD. You can create up to three partitions on a DASD.

In our example here, we create one partition spanning the whole disk:. If you want to use the entire DASD, create one partition spanning the entire drive as in the fdasd example above. The above instructions described how to activate DASDs dynamically in a running system. However, such changes are not persistent and do not survive a reboot. Those DASDs required for the root file system need to be activated very early during the boot process by the initramfs to be able to mount the root file system.

There is one boot option to activate DASDs early in the boot process: rd. To do this, add rd. Make sure the length of the kernel command line in the configuration file does not exceed bytes. Otherwise, the boot loader cannot be saved, and the installation fails. Run zipl to apply the changes of the configuration file for the next IPL:. When adding multiple options, use a space or a tab to separate each option.

For example, if the device number is a , run:. For example, if the bus ID is 0. The value is a comma-separated list containing the device bus ID, the WWPN as 16 digit hexadecimal number prefixed with 0x , and the FCP LUN prefixed with 0x and padded with zeroes to the right to have 16 hexadecimal digits.

For simplicity, the example shows a configuration without multipathing. At boot time, all FCP adapters visible to the system are added and trigger udev. For more information on the qeth device driver naming scheme, see Customizing boot parameters.

This section contains information on how to add a qeth device dynamically. Determine whether the qeth device driver modules are loaded. The following example shows loaded qeth modules:. If the output of the lsmod command shows that the qeth modules are not loaded, run the modprobe command to load them:. Use the znetconf utility to sense and list candidate configurations for network devices:.

Select the configuration you want to work with and use znetconf to apply the configuration and to bring the configured group device online as network device. Optionally, you can also pass arguments that are configured on the group device before it is set online:.

Now you can continue to configure the encf network interface. Alternatively, you can use sysfs attributes to set the device online as follows:. Next, verify that the qeth group device was created properly by looking for the read channel:. You can optionally set additional parameters and features, depending on the way you are setting up your system and the features you require, such as:.

Bring the device online by writing 1 to the online sysfs attribute:. A return value of 1 indicates that the device is online, while a return value 0 indicates that the device is offline. The following command from the sutils package shows the most important settings of your qeth device:.

To make your new qeth device persistent, you need to create the configuration file for your new interface. If a configuration file for another device of the same type already exists, the simplest way to add the config file is to copy it to the new name and then edit it:.

To learn IDs of your network devices, use the lsqeth utility:. If you do not have a similar device defined, you must create a new file. The Red Hat Enterprise Linux installation program currently uses this to configure the layer mode layer2 and the relative port number portno of qeth devices.

The qeth device driver default for OSA devices is now layer 2 mode. Alternatively, you can trigger the activation of a ifcfg file for network channels which were previously not active yet, by executing the following commands:.

Verify your changes by using the ping utility to ping the gateway or another host on the subnet of the new device:. To add a network device that is required to access the root file system, you only have to change the boot options. The file that needs to be modified can be located using the following commands:.

Dracut , the mkinitrd successor that provides the functionality in the initramfs that in turn replaces initrd , provides a boot parameter to activate network devices on IBM Z early in the boot process: rd. As input, this parameter takes a comma-separated list of the NETTYPE qeth, lcs, ctc , two lcs, ctc or three qeth device bus IDs, and optional additional parameters consisting of key-value pairs corresponding to network device sysfs attributes.

This parameter configures and activates the IBM Z network hardware. The configuration of IP addresses and other network specifics works the same as for other platforms. See the dracut documentation for more details. This section contains information about the parameters and configuration files on IBM Z. Several parameters are required and must be included in the parameter file.

These parameters are also provided in the file generic. The generic. This setting speeds up boot and device detection on systems with many devices. The installation program transparently handles the activation of ignored devices. The purpose of the CMS configuration file is to save space in the parameter file by moving the parameters that configure the initial network setup, the DASD, and the FCP specification out of the parameter file.

These parameters point the installation program to the configuration file:. This value must be specified in lower case. These parameters can be used to automatically set up the preliminary network, and can be defined in the CMS configuration file. These parameters are the only parameters that can also be used in a CMS configuration file. All other parameters in other sections must be specified in the parameter file. Where type must be one of the following: qeth , lcs , or ctc.

The default is qeth. The IDs must be specified in lowercase. This variable supports OSA devices operating in qdio mode or in non-qdio mode. Where value can be 0 or 1. Where value can be 0 , 1 , or 3. The default is 0. The netmask supports the syntax of a prefix integer from 1 to 32 as specified in IPv4 classless interdomain routing CIDR. For example, you can specify 24 instead of The installation program supports a comma-separated list of device bus IDs, or ranges of device bus IDs with the optional attributes ro , diag , erplog , and failfast.

Optionally, you can abbreviate device bus IDs to device numbers with leading zeros stripped. Any optional attributes should be separated by colons and enclosed in parentheses. Optional attributes follow a device bus ID or a range of device bus IDs. The only supported global option is autodetect.

Other global options such as probeonly , nopav , or nofcx are not supported by the installation program. Only specify those DASDs that need to be installed on your system. All unformatted DASDs specified here must be formatted after a confirmation later on in the installation program. An example value looks similar to the following:. The following parameters can be defined in a parameter file but do not work in a CMS configuration file.

Specifies a path to a tree containing install. Otherwise, follows the same syntax as inst. If inst. However, if Anaconda finds install. If only inst. The boot parameters described here are the most useful for installations and trouble shooting on IBM Z, but only a subset of those that influence the installation program.

To change the parameter file, begin by extending the shipped generic. Example of redhat. UEFI Secure Boot attempts to verify the signature using the corresponding public key, but because the hardware does not recognize the Beta private key, Red Hat Enterprise Linux Beta release system fails to boot. Red Hat works closely with hardware vendors on supported hardware. An installation target is a storage device that stores Red Hat Enterprise Linux and boots the system. For information about support for third-party virtualization technologies, see the Red Hat Hardware Compatibility List.

However, for certain Red Hat Enterprise Linux installation scenarios, it is recommended that you record system specifications for future reference. These scenarios include:. Record: The model numbers, sizes, types, and interfaces of the hard drives attached to the system. Installing RHEL as an additional operating system on an existing system.

Record: Partitions used on the system. This information can include file system types, device node names, file system labels, and sizes, and allows you to identify specific partitions during the partitioning process.

If one of the operating systems is a Unix operating system, Red Hat Enterprise Linux may report the device names differently. If multiple operating systems are installed, the Red Hat Enterprise Linux installation program attempts to automatically detect them, and to configure boot loader to boot them. You can manually configure additional operating systems if they are not detected automatically. See Configuring boot loader in Configuring software settings for more information.

Record: The hard drive and directory that holds the image. Verify that the domain name is supplied by the DHCP server. If it is not, enter the domain name during installation. If several operating systems are installed, it is important that you verify that the allocated disk space is separate from the disk space required by Red Hat Enterprise Linux. You must have a minimum of 10 GiB of available disk space.

To install Red Hat Enterprise Linux, you must have a minimum of 10 GiB of space in either unpartitioned disk space or in partitions that can be deleted.

See Partitioning reference for more information. It is possible to complete the installation with less memory than the recommended minimum requirements. The exact requirements depend on your environment and installation path. It is recommended that you test various configurations to determine the minimum required RAM for your environment.

However, additional RAM may be required if your Kickstart file includes commands that require additional memory, or write data to the RAM disk. For Red Hat Enterprise Linux Beta releases, the kernel is signed with a Red Hat Beta-specific public key, which the system fails to recognize by default.

As a result, the system fails to even boot the installation media. This section describes the file systems available in Red Hat Enterprise Linux. This small boot partition is located on the first partition of the hard drive. RAID stands for Redundant Array of Independent Disks, a technology which allows you to combine multiple physical disks into logical units. Some setups are designed to enhance performance at the cost of reliability, while others improve reliability at the cost of requiring more disks for the same amount of available space.

Red Hat recommends that you create separate file systems at the following mount points. This partition scheme is recommended for bare metal deployments and it does not apply to virtual and cloud deployments. Due to the limitations of most firmwares, creating a small partition to hold these is recommended.

In most scenarios, a 1 GiB boot partition is adequate. The root directory is the top-level of the directory structure. While a 5 GiB root file system allows you to install a minimal installation, it is recommended to allocate at least 10 GiB so that you can install as many package groups as you want.

Swap file systems support virtual memory; data is written to a swap file system when there is not enough RAM to store the data your system is processing.

Swap size is a function of system memory workload, not total system memory and therefore is not equal to the total system memory size. It is important to analyze what applications a system will be running and the load those applications will serve in order to determine the system memory workload. Application providers and developers can provide guidance. When the system runs out of swap space, the kernel terminates processes as the system RAM memory is exhausted.

Configuring too much swap space results in storage devices being allocated but idle and is a poor use of resources. Too much swap space can also hide memory leaks. The maximum size for a swap partition and other additional information can be found in the mkswap 8 manual page. The following table provides the recommended size of a swap partition depending on the amount of RAM in your system and if you want sufficient memory for your system to hibernate. If you let the installation program partition your system automatically, the swap partition size is established using these guidelines.

Automatic partitioning setup assumes hibernation is not in use. The maximum size of the swap partition is limited to 10 percent of the total size of the hard drive, and the installation program cannot create swap partitions more than 1TiB. At the border between each range, for example, a system with 2 GB, 8 GB, or 64 GB of system RAM, discretion can be exercised with regard to chosen swap space and hibernation support.

If your system resources allow for it, increasing the swap space can lead to better performance. Distributing swap space over multiple storage devices - particularly on systems with fast drives, controllers and interfaces - also improves swap space performance. Many systems have more partitions and volumes than the minimum required. Choose partitions based on your particular system needs. There is no best way to partition every system; the optimal setup depends on how you plan to use the system being installed.

However, the following tips may help you find the optimal layout for your needs:. When kdump is enabled in system it will take approximately another 40MB another initrd with 33MB. However, it is recommended that you increase the size of this partition if you are planning on retaining multiple kernel releases or errata kernels.

In some situations, such as when these directories are placed on an iSCSI drive or an FCoE location, the system may either be unable to boot, or it may hang with a Device is busy error when powering off or rebooting.

It is important to understand how storage technologies are configured and how support for them may have changed between major versions of Red Hat Enterprise Linux. Any RAID functions provided by the mainboard of your computer, or attached controller cards, need to be configured before you begin the installation process. On systems with more than one hard drive, you can use the Red Hat Enterprise Linux installation program to operate several of the drives as a Linux software RAID array.

You can connect and configure external USB storage after installation. Most devices are recognized by the kernel, but some devices may not be recognized. If it is not a requirement to configure these disks during installation, disconnect them to avoid potential problems.

These sets are automatically detected during the boot process and their device node paths can change across several booting processes. You can find the file system labels and device UUIDs using the blkid command. This section contains information about some of the boot options that you can use to modify the default behavior of the installation program. This section contains information about the various installation source boot options.

The inst. The target of the inst. Use the inst. The following table contains details of the inst. Installation DVD as a physical disk. Image file of the installation DVD, or an installation tree, which is a complete copy of the directories and files on the installation DVD. Installation tree, which is a complete copy of the directories and files on the installation DVD. You can use the inst. These repositories are only used during the installation process; they are not installed on the installed system.

Looks for the installable tree at a given NFS path. A colon is required after the host. Looks for the installable tree at the given location in the installation environment. To use this option, the repository must be mounted before the installation program attempts to load the available software groups.

The benefit of this option is that you can have multiple repositories on one bootable ISO, and you can install both the main repository and additional repositories from the ISO. This installation method requires an ISO with a valid installable tree. This option expects the path to a directory that contains a valid. If the.

When the inst. Use this option when you want to manually specify the installation source in the installation program at a later time. If you want to specify an installation source, use the inst. If you modify the default label of the file system that contains the runtime image, or if you use a customized procedure to boot the installation system, verify that the inst.

For example, if your remote installation source is using self-signed SSL certificates, the inst. Example when specifying the source using inst. Disables the ability to save the output Kickstart results generated by the installation program. This section contains information about commonly used network boot options. Initial network initialization is handled by dracut. For a complete list, see the dracut. To configure multiple interfaces, you can use the ip option multiple times, once for each interface; to do so, you must use the rd.

Alternatively, you can use the ip option once, and then use Kickstart to set up further interfaces. This option accepts several different formats. The following tables contain information about the most common options. The method automatic configuration of a specific interface with an override brings up the interface using the specified method of automatic configuration, such as dhcp , but overrides the automatically-obtained IP address, gateway, netmask, host name or other specified parameters.

All parameters are optional, so specify only the parameters that you want to override. The method parameter can be any of the following:. You can use this option multiple times.