My job has me working on RHEL 4. You can imagine the frustration. Just saying. Keshan Keshan 2 2 bronze badges. GnuTux95 GnuTux95 29 4 4 bronze badges. The Overflow Blog. Podcast Helping communities build their own LTE networks. Podcast Making Agile work for data science. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Linked Related 2. How to do this will be covered at the end of the guide.
You must specify a root password to be used for the administration of your system. Note, if you supply a weak password, you will be asked to press "Done" twice to confirm you have chosen a weak password! The strength of your password is also indicated.
From this screen you must define the name of a user. In this example I have also chosen the user to be an " Administrator ". Again, if you supply a weak password, you will be asked to confirm this. Once you have supplied the relevant credentials, simply click " Done " to continue with the installation. It is strongly recommended that you use the " default " option of " Require a password to use this account ".
This screen allows you to configure your disk partitioning layout. Two options are available. For this installation of RHEL 8, I am going to choose the option of manually configuring the disk partition layout " I will configure partitioning ". Note, as a rule of thumb, the swap size should be half the size of the physical memory. The size of the disk used in this exercise has a capacity of 20GB.
Once you have selected the option " Custom ", click on the " Done " button in the upper left hand corner of the screen. Available space is indicated in the lower left of the screen. It is from this menu that you can select the " Mount Point " or enter the name of a mount point to create. You also need to specify the " Desired Capacity " to be used with each mount point. Values can be added as " GB " or " MB ". The first partition we are going to create is the boot partition.
The "Mount Point" can be selected from the drop down menu and the desired capacity can by typed into the "Desired Capacity" box. Once the details have been entered, click on " Add Mount Point ". Notice, the Device Type is set to " Standard Partition " for a boot partition.
A size of MB was specified in this example. Enter the appropriate values as per the table above. In this exercise we are going to change the default name of the Volume Group to be " sysVG ".
To change the name of the default Volume Group, click on the " Modify " button. A Volume Group configuration box will appear. Simply change the name from the default to " sysVG ". The Logical Volume name is entered into the box " Name ". At any time, you may press the " Update Settings button to apply any changes made. This file system is created last as we are going to assign all remaining space to this filesystem.
To allocate the remaining space to this filesystem, simply leave the "Desired Capacity" value empty. Once the system is built, we can remove this filesystem and all space will be then available to our system Volume Group "sysVG".
This space can then be given to any of the file systems within the Volume Group "sysVG". Once you have configured all the file systems, you should end up with a layout similar to the one below. If an operating system is already installed, the Red Hat Enterprise Linux installation program attempts to automatically detect and configure the boot loader to start the other operating system. If the boot loader is not detected, you can manually configure any additional operating systems after you finish the installation.
If you are installing a Red Hat Enterprise Linux system with more than one disk, you might want to manually specify the disk where you want to install the boot loader. From the Installation Destination window, click the Full disk summary and bootloader link. The Selected Disks dialog box opens. The boot loader is installed on the device of your choice, or on a UEFI system; the EFI system partition is created on the target device during guided partitioning.
If you choose not to install a boot loader, you cannot boot the system directly and you must use another boot method, such as a standalone commercial boot loader application.
Use this option only if you have another way to boot your system. If you use automatic partitioning, the installation program creates the partition. Kdump is a kernel crash-dumping mechanism. In the event of a system crash, Kdump captures the contents of the system memory at the moment of failure. This captured memory can be analyzed to find the cause of the crash.
This reserved memory is not accessible to the main kernel. Select either the Automatic or Manual memory reservation setting. The amount of memory that you reserve is determined by your system architecture AMD64 and Intel 64 have different requirements than IBM Power as well as the total amount of system memory.
In most cases, automatic reservation is satisfactory. Use the Network and Host name window to configure network interfaces. Options that you select here are available both during the installation for tasks such as downloading packages from a remote location, and on the installed system. Follow the steps in this procedure to configure your network and host name. From the list in the left-hand pane, select an interface.
The details are displayed in the right-hand pane. The installation program automatically detects locally accessible interfaces, and you cannot add or remove them manually. Type a host name for your system in the Host Name field. This procedure describes how to add a virtual network interface. Select the interface type and click Add. An editing interface dialog box opens, allowing you to edit any available settings for your chosen interface type.
For more information see Editing network interface. If you need to change the settings of a virtual interface, select the interface and click Configure. This section contains information about the most important settings for a typical wired connection used during installation.
Configuration of other types of networks is broadly similar, although the specific configuration parameters might be different. On IBM Z, you cannot add a new connection as the network subchannels need to be grouped and set online beforehand, and this is currently done only in the booting phase.
To configure a network connection manually, select the interface from the Network and Host name window and click Configure. The options present depend on the connection type - the available options are slightly different depending on whether the connection type is a physical interface wired or wireless network interface controller or a virtual interface Bond, Bridge, Team, or Vlan that was previously configured in Adding a virtual interface.
The following sections contain information about the three most common and useful options in the editing dialog:. Follow the steps in this procedure to enable or disable an interface connection. Select the Connect automatically with priority check box to enable connection by default. Keep the default priority setting at 0. By default, both IPv4 and IPv6 are set to automatic configuration depending on current network settings. This means that addresses such as the local IP address, DNS address, and other settings are detected automatically when the interface connects to a network.
In many cases, this is sufficient, but you can also provide static configuration in the IPv4 Settings and IPv6 Settings tabs. Complete the following steps to configure IPv4 or IPv6 settings:. To set static network configuration, navigate to one of the IPv Settings tabs and from the Method drop-down menu, select a method other than Automatic , for example, Manual.
The Addresses pane is enabled. Select the Require IPv X addressing for this connection to complete check box. If this option remains disabled for both IPv4 and IPv6, the interface is able to connect if configuration succeeds on either IP protocol.
Select the Use this connection only for resources on its network check box to prevent the connection from becoming the default route. This option can be selected even if you did not configure any static routes. This route is used only to access certain resources, such as intranet pages that require a local or VPN connection.
Another default route is used for publicly available resources. Unlike the additional routes configured, this setting is transferred to the installed system. This option is useful only when you configure more than one interface. You use System Purpose to record the intended use of a Red Hat Enterprise Linux 8 system, and ensure that the entitlement server auto-attaches the most appropriate subscription to your system.
To record the intended purpose of your system, you can configure the following components of System Purpose. The selected values are used by the entitlement server upon registration to attach the most suitable subscription for your system. Service Level Agreement. Optional: Click Activation Key. Select the Set System Purpose check box.
System Purpose enables the entitlement server to determine and automatically attach the most appropriate subscription to satisfy the intended use of Red Hat Enterprise Linux 8 system. Optional: Expand Options. Click Register to register the system. Click Done to return to the Installation Summary window. This section contains information about the Red Hat Enterprise Linux 8 security policy and how to configure it for use on your system.
The packages are automatically installed. However, by default, no policies are enforced and therefore no checks are performed during or after installation unless specifically configured. Applying a security policy is not a mandatory feature of the installation program. If you apply a security policy to the system, it is installed using restrictions and recommendations defined in the profile that you selected.
The openscap-scanner package is added to your package selection, providing a preinstalled tool for compliance and vulnerability scanning. After the installation finishes, the system is automatically scanned to verify compliance.
Profile changes that you must apply before installation appear in the bottom pane. The default profiles do not require changes before installation.
However, loading a custom profile can require pre-installation tasks. Click Change content to use a custom profile. A separate window opens allowing you to enter a URL for valid security content. A network connection must be active before you can load a custom profile. The installation program detects the content type automatically. This section contains information about configuring your installation source and software selection settings, and activating a repository.
Complete the steps in this procedure to configure an installation source from either auto-detected installation media, Red Hat CDN, or the network. When the Installation Summary window first opens, the installation program attempts to configure an installation source based on the type of media that was used to boot the system. From the Installation Summary window, click Installation Source.
The Installation Source window opens. Review the Additional repositories section and note that the AppStream checkbox is selected by default.
Optional: Select the On the network option to download and install packages from a network location instead of local media. Type the server address without the protocol into the address field. This field accepts options listed in the nfs 5 man page. When selecting an NFS installation source, you must specify the address with a colon : character separating the host name from the path. For example:. The following steps are optional and are only required if you use a proxy for network access.
All environments and additional software packages are available for selection when you finish configuring the sources. To activate or deactivate a repository, click the check box in the Enabled column for each entry in the list. You can name and configure your additional repository in the same way as the primary repository on the network. Use the Software Selection window to select the software packages that you require.
The packages are organized by Base Environment and Additional Software. Use a predefined environment and additional software to customize your system. However, in a standard installation, you cannot select individual packages to install. The XML file contains details of the packages installed as part of a base environment. If you are unsure about which packages to install, Red Hat recommends that you select the Minimal Install base environment. Minimal install installs a basic version of Red Hat Enterprise Linux with only a minimal amount of additional software.
After the system finishes installing and you log in for the first time, you can use the YUM package manager to install additional software. For more information about YUM package manager, see the Configuring basic system settings document. From the Base Environment pane, select a base environment. You can select only one base environment.
The Server with GUI base environment is the default base environment and it launches the Initial Setup application after the installation completes and you restart the system.
You can install Red Hat Enterprise Linux on a large variety of storage devices. You can configure basic, locally accessible, storage devices in the Installation Destination window. Basic storage devices directly connected to the local system, such as hard disk drives and solid-state drives, are displayed in the Local Standard Disks section of the window.
These storage devices are available during the installation, but are not immediately accessible after you finish installing and reboot. The storage device selection window lists all storage devices that the installation program can access. Depending on your system and available hardware, some tabs might not be displayed. The devices are grouped under the following tabs:. Storage devices accessible through more than one path, such as through multiple SCSI controllers or Fiber Channel ports on the same system.
The installation program only detects multipath storage devices with serial numbers that are 16 or 32 characters long. Select the check box to enable the device that you require during the installation process. Later in the installation process you can choose to install Red Hat Enterprise Linux on any of the selected devices, and you can choose to mount any of the other selected devices as part of the installed system automatically.
Any storage devices that you do not select are hidden from the installation program entirely. To chain load the boot loader from a different boot loader, select all the devices present. You cannot change the name of the iSCSI initiator after you attempt discovery for the first time. To change the iSCSI initiator name, you must restart the installation. Complete the following steps to discover and start an iSCSI session. A valid IQN entry contains the following information:.
A colon followed by a string that uniquely identifies this particular iSCSI initiator within your domain or subdomain. For example, :diskarrays-sn-a A complete IQN is as follows: iqn. The installation program prepopulates the iSCSI Initiator Name field with a name in this format to help you with the structure. For more information about IQNs, see 3. The following options are available:. The installation program attempts to discover an iSCSI target based on the information provided.
Select the check boxes for the node that you want to use for installation. The Node login authentication type menu contains the same options as the Discovery Authentication Type menu. However, if you need credentials for discovery authentication, use the same credentials to log in to a discovered node. Complete the following steps to configure DASD storage devices. You can enter FCP devices either in the graphical installation, or as a unique parameter entry in the parameter or CMS configuration file.
The values that you enter must be unique to each site that you configure. The newly-added devices are displayed in the System z Devices tab of the Installation Destination window. Enter the sector size that you require and click Start Reconfiguration. Click Done to return to the Installation Destination window. Additionally, if the device meets the requirements for booting, you can set the device as a boot device.
You can use manual partitioning to configure your disk partitions and mount points and define the file system that Red Hat Enterprise Linux is installed on. Before installation, you should consider whether you want to use partitioned or unpartitioned disk devices.
You can also create additional partitions and volumes as you require. To prevent data loss it is recommended that you back up your data before proceeding.
If you are upgrading or creating a dual-boot system, you should back up any data you want to keep on your storage devices. If you selected to encrypt the storage, a dialog box for entering a disk encryption passphrase opens. Type in the LUKS passphrase:. Enter the passphrase in the two text fields. To switch keyboard layout, use the keyboard icon. In the dialog box for entering the passphrase, you cannot change the keyboard layout.
Select the English keyboard layout to enter the passphrase in the installation program. Detected mount points are listed in the left-hand pane. The mount points are organized by detected operating system installations. As a result, some file systems may be displayed multiple times if a partition is shared among several installations. Select the mount points in the left pane; the options that can be customized are displayed in the right pane.
If your system contains existing file systems, ensure that enough space is available for the installation. To remove any partitions, select them in the list and click the - button.
The dialog has a check box that you can use to remove all other partitions used by the system to which the deleted partition belongs. If there are no existing partitions and you want to create the recommended set of partitions as a starting point, select your preferred partitioning scheme from the left pane default for Red Hat Enterprise Linux is LVM and click the Click here to create them automatically link. These are the recommended file systems for a typical installation, but you can add additional file systems and mount points.
Continue with adding mount points , configuring the individual mount points , and configuring the underlying partitions or volumes. Complete the following steps to add multiple mount point file systems.
Enter the size of the file system in to the Desired Capacity field; for example, 2GiB. If you do not specify a value in the Desired Capacity field, or if you specify a size bigger than available space, then all remaining free space is used.
This procedure describes how to set the partitioning scheme for each mount point that was created manually. In the lower left-hand side of the Manual Partitioning window, click the storage device selected link to open the Selected Disks dialog and review disk information. Click the Rescan button circular arrow button to refresh all local disks and partitions; this is only required after performing advanced partition configuration outside the installation program.
Clicking the Rescan Disks button resets all configuration changes made in the installation program. You can customize a partition or volume if you want to set specific settings.
In some situations, such as when these directories are placed on an iSCSI drive or an FCoE location, the system is unable to boot, or hangs with a Device is busy error when powering off or rebooting. RAID is available only if two or more disks are selected for partitioning. Select the appropriate file system type for this partition or volume from the File system drop-down menu.
Type a name in the Name field. Note that standard partitions are named automatically when they are created and you cannot edit the names of standard partitions. Click Update Settings to apply your changes and if required, select another partition to customize. Changes are not applied until you click Begin Installation from the Installation Summary window. Click Done when you have created and customized all file systems and mount points.
If you choose to encrypt a file system, you are prompted to create a passphrase. A Summary of Changes dialog box opens, displaying a summary of all storage actions for the installation program. RAID devices are constructed from multiple storage devices that are arranged to provide increased performance and, in some configurations, greater fault tolerance. A RAID device is created in one step and disks are added or removed as necessary.
You can configure one RAID partition for each physical disk in your system, so the number of disks available to the installation program determines the levels of RAID device available. For example, if your system has two hard drives, you cannot create a RAID 10 device, as it requires a minimum of three separate disks. You do not have to configure software RAID manually. A message is displayed at the bottom of the window if the specified RAID level requires more disks.
Partitions on physical storage are represented as physical volumes that you can group together into volume groups. You can divide each volume group into multiple logical volumes, each of which is analogous to a standard disk partition.
Therefore, LVM logical volumes function as partitions that can span multiple physical disks. During text-mode installation, LVM configuration is not available.
You can run vgcreate and lvm commands in this shell. The Volume Group drop-down menu is displayed with the newly-created volume group name. The size is always set to the default value of 4 MiB. Follow the steps in this procedure to configure a newly-created LVM logical volume. Click Modify to configure the newly-created volume group.
The Configure Volume Group dialog box opens. From the Size policy drop-down menu, select the size policy for the volume group. You must configure a root password to finish the installation process and to log in to the administrator also known as superuser or root account that is used for system administration tasks.
These tasks include installing and updating software packages and changing system-wide configuration such as network and firewall settings, storage options, and adding or modifying users, groups and file permissions. Use one or both of the following ways to gain root privileges to the installed system:. The root account has complete control over the system.
If unauthorized personnel gain access to the account, they can access or delete users' personal files. Type your password in the Root Password field. The requirements and recommendations for creating a strong root password are:. Click Done to confirm your root password and return to the Installation Summary window.
If you proceeded with a weak password, you must click Done twice. It is recommended that you create a user account to finish the installation. If you do not create a user account, you must log in to the system as root directly, which is not recommended.
Type the username in to the User name field, for example: jsmith. The User name is used to log in from a command line; if you install a graphical environment, then your graphical login manager uses the Full name. Select the Make this user administrator check box if the user requires administrative rights the installation program adds the user to the wheel group.
An administrator user can use the sudo command to perform tasks that are only available to root using the user password, instead of the root password. This may be more convenient, but it can also cause a security risk.
Select the Require a password to use this account check box. If you give administrator privileges to a user, verify that the account is password protected. Never give a user administrator privileges without assigning a password to the account. This procedure describes how to edit the default settings for the user account in the Advanced User Configuration dialog box. In the User and Groups IDs section you can:. The default value is GIDs are reserved by the system so they can not be assigned to a user group.
Specify additional groups as a comma-separated list in the Group Membership field. Groups that do not already exist are created; you can specify custom GIDs for additional groups in parentheses. This section describes how to complete the following post-installation tasks:.
Depending on your requirements, there are several methods to register your system. Most of these methods are completed as part of post-installation tasks. This section contains information about how to complete initial setup on a Red Hat Enterprise Linux 8 system.
The information displayed in the Initial Setup window might vary depending on what was configured during installation. At a minimum, the Licensing and Subscription Manager options are displayed. From the Initial Setup window, select Licensing Information. Review the license agreement and select the I accept the license agreement checkbox. You must accept the license agreement. Exiting Initial Setup without completing this step causes a system restart.
When the restart process is complete, you are prompted to accept the license agreement again. Click Done to apply the settings and return to the Initial Setup window.
If you did not configure network settings, you cannot register your system immediately. In this case, click Finish Configuration. Red Hat Enterprise Linux 8 starts and you can login, activate access to the network, and register your system. See Subscription manager post installation for more information. If you configured network settings, as described in Network hostname , you can register your system immediately, as shown in the following steps:.
From the Initial Setup window, select Subscription Manager. This section contains information about how to register your Red Hat Enterprise Linux 8 subscription using the command line. When auto-attaching a system, the subscription service checks if the system is physical or virtual, as well as how many sockets are on the system.
A physical system usually consumes two entitlements, a virtual system usually consumes one. One entitlement is consumed per two sockets on a system. When the system is successfully registered, an output similar to the following is displayed:.
Available roles depend on the subscriptions that have been purchased by the organization and the architecture of the Red Hat Enterprise Linux 8 system. Attach the system to an entitlement that matches the host system architecture:. When a subscription is successfully attached, an output similar to the following is displayed:.
An alternative method for registering your Red Hat Enterprise Linux 8 system is by logging in to the system as a root user and using the Subscription Manager graphical user interface.
This section contains information about how to register your Red Hat Enterprise Linux 8 system using the Subscription Manager User Interface to receive updates and access package repositories. Enter your administrator password in the Authentication Required dialog box. The Register button in the Subscriptions window changes to Unregister and installed products display a green X. You can troubleshoot an unsuccessful registration from a terminal window using the subscription-manager status command.
Registration Assistant is designed to help you choose the most suitable registration option for your Red Hat Enterprise Linux environment. You can use System Purpose to record the intended use of a Red Hat Enterprise Linux 8 system, and ensure that the entitlement server auto-attaches the most appropriate subscription to your system.
The history option gives you an overview of what happened in past transactions. This provides some useful information, like the date when the transaction happened and what command was run. You can undo or redo certain transactions using the history command.
Here is an example of undoing a transaction:. YUM provides many options for package management. For detailed option information, look at man yum and yum —help.
Also, here is a link to YUM documentation. Using RPM , you can install, uninstall, and query individual software packages.
Still, it cannot manage dependency resolution like YUM. RPM does provide you useful output, including a list of required packages. An RPM package consists of an archive of files and metadata. Metadata includes helper scripts, file attributes, and information about packages. RPM maintains a database of installed packages, which enables powerful and fast queries. RPM has some basic modes: query, verify, install, upgrade, erase, show querytags, show configuration.
0コメント