| Installation Guide23.11. Initializing the Hard DiskIf no readable partition tables are found on existing hard disks, the installation program asks to initialize the hard disk. This operation makes any existing data on the hard disk unreadable. If your system has a brand new hard disk with no operating system installed, or you have removed all partitions on the hard disk, click Re-initialize drive. The installation program presents you with a separate dialog for each disk on which it cannot read a valid partition table. Click the Ignore all button or Re-initialize all button to apply the same answer to all devices. Certain RAID systems or other nonstandard configurations may be unreadable to the installation program and the prompt to initialize the hard disk may appear. The installation program responds to the physical disk structures it is able to detect. To enable automatic initializing of hard disks for which it turns out to be necessary, use the kickstart command clearpart --initlabel (refer to Chapter 32, Kickstart Installations) If you have a nonstandard disk configuration that can be detached during installation and detected and configured afterward, power off the system, detach it, and restart the installation. 23.12. Upgrading an Existing System Red Hat does not support in-place upgrades between any major versions of Red Hat Enterprise Linux. A major version is denoted by a whole number version change. For example, Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6 are both major versions of Red Hat Enterprise Linux. In-place upgrades across major releases do not preserve all system settings, services or custom configurations. Consequently, Red Hat strongly recommends fresh installations when upgrading from one major version to another. The installation system automatically detects any existing installation of Red Hat Enterprise Linux. The upgrade process updates the existing system software with new versions, but does not remove any data from users' home directories. The existing partition structure on your hard drives does not change. Your system configuration changes only if a package upgrade demands it. Most package upgrades do not change system configuration, but rather install an additional configuration file for you to examine later. Note that the installation medium that you are using might not contain all the software packages that you need to upgrade your computer. Software you have installed manually on your existing Red Hat Enterprise Linux system may behave differently after an upgrade. You may need to manually reinstall or recompile this software after an upgrade to ensure it performs correctly on the updated system. 23.12.1. Upgrading Using the Installer In general, Red Hat recommends that you keep user data on a separate /home partition and perform a fresh installation. For more information on partitions and how to set them up, refer to Section 9.13, "Disk Partitioning Setup". If you choose to upgrade your system using the installation program, any software not provided by Red Hat Enterprise Linux that conflicts with Red Hat Enterprise Linux software is overwritten. Before you begin an upgrade this way, make a list of your system's current packages for later reference: rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' > ~/old-pkglist.txt
After installation, consult this list to discover which packages you may need to rebuild or retrieve from sources other than Red Hat. Next, make a backup of any system configuration data: su -c 'tar czf /tmp/etc-`date +%F`.tar.gz /etc' su -c 'mv /tmp/etc-*.tar.gz /home'
Make a complete backup of any important data before performing an upgrade. Important data may include the contents of your entire /home directory as well as content from services such as an Apache, FTP, or SQL server, or a source code management system. Although upgrades are not destructive, if you perform one improperly there is a small possibility of data loss. Note that the above examples store backup materials in a /home directory. If your /home directory is not a separate partition, you should not follow these examples verbatim! Store your backups on another device such as CD or DVD discs or an external hard disk. 23.13. Disk Partitioning SetupIt is always a good idea to back up any data that you have on your systems. For example, if you are upgrading or creating a dual-boot system, you should back up any data you wish to keep on your storage devices. Mistakes do happen and can result in the loss of all your data. If you install Red Hat Enterprise Linux in text mode, you can only use the default partitioning schemes described in this section. You cannot add or remove partitions or file systems beyond those that the installer automatically adds or removes. If you require a customized layout at installation time, you should perform a graphical installation over a VNC connection or a kickstart installation. Furthermore, advanced options such as LVM, encrypted filesystems, and resizable filesystems are available only in graphical mode and kickstart. Partitioning allows you to divide your storage devices into isolated sections, where each section behaves as a separate Linux device. Partitioning is particularly useful if you run multiple operating systems, or wish to enforce a logical or functional distinction between your storage partitions (such as a /home partition that persistently contains user information). On this screen you can choose to create the default partition layout in one of four different ways, or choose to partition storage devices manually to create a custom layout. The first four options allow you to perform an automated installation without having to partition your storage devices yourself. If you do not feel comfortable with partitioning your system, choose one of these options and let the installation program partition the storage devices for you. Depending on the option that you choose, you can still control what data (if any) is removed from the system. To encrypt partitions, you will need to select the option. Partitions created with one of the four automated options cannot be encrypted. Your options are: - Use All Space
Select this option to remove all partitions on your storage drives (this includes partitions created by other operating systems such as z/VM or z/OS). If you select this option, all data on the selected DASD and SCSI storage devices is removed by the installation program. - Replace Existing Linux System(s)
Select this option to remove only Linux partitions (partitions created from a previous Linux installation). This does not remove other partitions you may have on your storage devices (such as z/VM or z/OS partitions). - Shrink Current System
Select this option to resize your current data and partitions manually and install a default Red Hat Enterprise Linux layout in the space that is freed. If you shrink partitions on which other operating systems are installed, you might not be able to use those operating systems. Although this partitioning option does not destroy data, operating systems typically require some free space in their partitions. Before you resize a partition that holds an operating system that you might want to use again, find out how much space you need to leave free. - Use Free Space
Select this option to retain your current data and partitions and install Red Hat Enterprise Linux in the unused space available on the storage drives. Ensure that there is sufficient space available on the storage drives before you select this option - refer to Section 18.1, "Pre-Installation". - Create Custom Layout
Choose your preferred partitioning method by clicking the radio button to the left of its description in the dialog box. Select Encrypt system to encrypt all partitions except the /boot partition. Refer to Appendix C, Disk Encryption for information on encryption. To review and make any necessary changes to the partitions created by automatic partitioning, select the Review option. After selecting Review and clicking Next to move forward, the partitions created for you by anaconda appear. You can make modifications to these partitions if they do not meet your needs. When you install Red Hat Enterprise Linux 6 on a system with multipath and non-multipath storage devices, the automatic partitioning layout in the installer might create volume groups that contain a mix of multipath and non-multipath devices. This defeats the purpose of multipath storage. We advise that you select only multipath or only non-multipath devices on the disk selection screen that appears after selecting automatic partitioning. Alternatively, select custom partitioning. Click Next once you have made your selections to proceed. 23.14. Encrypt Partitions If you selected the Encrypt System option, the installer prompts you for a passphrase with which to encrypt the partitions on the system. Choose a passphrase and type it into each of the two fields in the dialog box. You must provide this passphrase every time that the system boots. If you lose this passphrase, any encrypted partitions and the data on them will become completely inaccessible. There is no way to recover a lost passphrase. 23.15. Creating a Custom Layout or Modifying the Default Layout If you chose to create a custom layout, you must tell the installation program where to install Red Hat Enterprise Linux. This is done by defining mount points for one or more disk partitions in which Red Hat Enterprise Linux is installed. Anaconda can handle the partitioning requirements for a typical installation. The partitioning screen contains two panes. The top pane contains a graphical representation of the DASD, FCP LUN, or logical volume selected in the lower pane. Above the display, you can review the Drive name (such as /dev/dasda), the Geom (which shows the hard disk's geometry and consists of three numbers representing the number of cylinders, heads, and sectors as reported by the hard disk), and the Model of the hard drive as detected by the installation program. Using your mouse, click once to highlight a particular field in the graphical display. Double-click to edit an existing partition or to create a partition out of existing free space. The lower pane contains a list of all DASDs, FCP LUNs, and logical volumes to be used during installation, as specified earlier in the installation process - refer to Section 23.10, " Assign Storage Devices ". Note that if you specified a CMSDASD in your parameter file, DASD names begin at dasdb; dasda was assigned to the CMSDASD and this name is no longer available at this point in the installation process. Devices are grouped by type. Click on the small triangles to the left of each device type to view or hide devices of that type. Anaconda displays several details for each device listed: - Device
the name of the device, logical volume, or partition - Size (MB)
the size of the device, logical volume, or partition (in MB) - Mount Point/RAID/Volume
the mount point (location within a file system) on which a partition is to be mounted, or the name of the RAID or logical volume group of which it is a part - Type
the type of partition. If the partition is a standard partition, this field displays the type of file system on the partition (for example, ext4). Otherwise, it indicates that the partition is a physical volume (LVM), or part of a software RAID - Format
A check mark in this column indicates that the partition will be formatted during installation.
Beneath the lower pane are four buttons: Create, Edit, Delete, and Reset. Select a device or partition by clicking on it in either the graphical representation in the upper pane of in the list in the lower pane, then click one of the four buttons to carry out the following actions: - Create
create a new partition, logical volume, or software RAID - Edit
change an existing partition, logical volume, or software RAID. Note that you can only shrink partitions with the Resize button, not enlarge partitions. - Delete
remove a partition, logical volume, or software RAID - Reset
undo all changes made in this screen
Finally, note which device is associated with /boot. The kernel files and bootloader sector will be associated with this device. The first DASD or SCSI LUN will be used, and the device number will be used when re-IPLing the post-installed system. The screenshots in the following subsections of this manual sometimes show hard disk types and device names that do not appear as such on System z. These screenshots are only intended to illustrate the installation interface itself and apply equally to DASDs and FCP-attached SCSI disks. The Create Storage dialog allows you to create new storage partitions, logical volumes, and software RAIDs. Anaconda presents options as available or unavailable depending on the storage already present on the system or configured to transfer to the system. Options are grouped under Create Partition, Create Software RAID and Create LVM as follows: Create Software RAID On System z, the storage subsystem uses RAID transparently, and you do not need to set it up. RAID Partition - create a partition in unallocated space to form part of a software RAID device. To form a software RAID device, two or more RAID partitions must be available on the system. RAID Device - combine two or more RAID partitions into a software RAID device. When you choose this option, you can specify the type of RAID device to create (the RAID level). This option is only available when two or more RAID partitions are available on the system.
Create LVM Logical Volume LVM Physical Volume - create a physical volume in unallocated space. LVM Volume Group - create a volume group from one or more physical volumes. This option is only available when at least one physical volume is available on the system. LVM Logical Volume - create a logical volume on a volume group. This option is only available when at least one volume group is available on the system.
23.15.2. Adding PartitionsMount Point: Enter the partition's mount point. For example, if this partition should be the root partition, enter /; enter /boot for the /boot partition, and so on. You can also use the pull-down menu to choose the correct mount point for your partition. For a swap partition the mount point should not be set - setting the filesystem type to swap is sufficient. File System Type: Using the pull-down menu, select the appropriate file system type for this partition. For more information on file system types, refer to Section 23.15.2.1, "File System Types". Allowable Drives: This field contains a list of the hard disks installed on your system. If a hard disk's box is highlighted, then a desired partition can be created on that hard disk. If the box is not checked, then the partition will never be created on that hard disk. By using different checkbox settings, you can have anaconda place partitions where you need them, or let anaconda decide where partitions should go. Size (MB): Enter the size (in megabytes) of the partition. Note, this field starts with 200 MB; unless changed, only a 200 MB partition will be created. Additional Size Options: Choose whether to keep this partition at a fixed size, to allow it to "grow" (fill up the available hard drive space) to a certain point, or to allow it to grow to fill any remaining hard drive space available. If you choose Fill all space up to (MB), you must give size constraints in the field to the right of this option. This allows you to keep a certain amount of space free on your hard drive for future use. Encrypt: Choose whether to encrypt the partition so that the data stored on it cannot be accessed without a passphrase, even if the storage device is connected to another system. Refer to Appendix C, Disk Encryption for information on encryption of storage devices. If you select this option, the installer prompts you to provide a passphrase before it writes the partition to the disk. OK: Select OK once you are satisfied with the settings and wish to create the partition. Cancel: Select Cancel if you do not want to create the partition.
23.15.2.1. File System TypesRed Hat Enterprise Linux allows you to create different partition types and file systems. The following is a brief description of the different partition types and file systems available, and how they can be used. Partition types standard partition - A standard partition can contain a file system or swap space, or it can provide a container for software RAID or an LVM physical volume. swap - Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. Refer to the Red Hat Enterprise Linux Deployment Guide for additional information. software RAID - Creating two or more software RAID partitions allows you to create a RAID device. For more information regarding RAID, refer to the chapter RAID (Redundant Array of Independent Disks) in the Red Hat Enterprise Linux Deployment Guide. physical volume (LVM) - Creating one or more physical volume (LVM) partitions allows you to create an LVM logical volume. LVM can improve performance when using physical disks. For more information regarding LVM, refer to the Red Hat Enterprise Linux Deployment Guide.
File systems ext4 - The ext4 file system is based on the ext3 file system and features a number of improvements. These include support for larger file systems and larger files, faster and more efficient allocation of disk space, no limit on the number of subdirectories within a directory, faster file system checking, and more robust journaling. A maximum file system size of 16TB is supported for ext4. The ext4 file system is selected by default and is highly recommended. ext3 - The ext3 file system is based on the ext2 file system and has one main advantage - journaling. Using a journaling file system reduces time spent recovering a file system after a crash as there is no need to fsck the file system. A maximum file system size of 16TB is supported for ext3. ext2 - An ext2 file system supports standard Unix file types (regular files, directories, symbolic links, etc). It provides the ability to assign long file names, up to 255 characters. xfs - XFS is a highly scalable, high-performance file system that supports filesystems up to 16 exabytes (approximately 16 million terabytes), files up to 8 exabytes (approximately 8 million terabytes) and directory structures containing tens of millions of entries. XFS supports metadata journaling, which facilitates quicker crash recovery. The XFS file system can also be defragmented and resized while mounted and active. Red Hat Enterprise Linux 6 does not support XFS on System z. vfat - The VFAT file system is a Linux file system that is compatible with Microsoft Windows long filenames on the FAT file system. Btrfs - Btrfs is under development as a file system capable of addressing and managing more files, larger files, and larger volumes than the ext2, ext3, and ext4 file systems. Btrfs is designed to make the file system tolerant of errors, and to facilitate the detection and repair of errors when they occur. It uses checksums to ensure the validity of data and metadata, and maintains snapshots of the file system that can be used for backup or repair. Because Btrfs is still experimental and under development, the installation program does not offer it by default. If you want to create a Btrfs partition on a drive, you must commence the installation process with the boot option btrfs. Refer to Chapter 28, Boot Options for instructions. Red Hat Enterprise Linux 6 includes Btrfs as a technology preview to allow you to experiment with this file system. You should not choose Btrfs for partitions that will contain valuable data or that are essential for the operation of important systems.
23.15.3. Create Software RAID On System z, the storage subsystem uses RAID transparently. There is no need to set up a software RAID. Redundant arrays of independent disks (RAIDs) are constructed from multiple storage devices that are arranged to provide increased performance and - in some configurations - greater fault tolerance. Refer to the Red Hat Enterprise Linux Deployment Guide for a description of different kinds of RAIDs. To make a RAID device, you must first create software RAID partitions. Once you have created two or more software RAID partitions, select RAID to join the software RAID partitions into a RAID device. - RAID Partition
Choose this option to configure a partition for software RAID. This option is the only choice available if your disk contains no software RAID partitions. This is the same dialog that appears when you add a standard partition - refer to Section 23.15.2, "Adding Partitions" for a description of the available options. Note, however, that File System Type must be set to software RAID
- RAID Device
Choose this option to construct a RAID device from two or more existing software RAID partitions. This option is available if two or more software RAID partitions have been configured.
Select the file system type as for a standard partition. Anaconda automatically suggests a name for the RAID device, but you can manually select names from md0 to md15. Click the checkboxes beside individual storage devices to include or remove them from this RAID. The RAID Level corresponds to a particular type of RAID. Choose from the following options: RAID 0 - distributes data across multiple storage devices. Level 0 RAIDs offer increased performance over standard partitions, and can be used to pool the storage of multiple devices into one large virtual device. Note that Level 0 RAIDS offer no redundancy and that the failure of one device in the array destroys the entire array. RAID 0 requires at least two RAID partitions. RAID 1 - mirrors the data on one storage device onto one or more other storage devices. Additional devices in the array provide increasing levels of redundancy. RAID 1 requires at least two RAID partitions. RAID 4 - distributes data across multiple storage devices, but uses one device in the array to store parity information that safeguards the array in case any device within the array fails. Because all parity information is stored on the one device, access to this device creates a bottleneck in the performance of the array. RAID 4 requires at least three RAID partitions. RAID 5 - distributes data and parity information across multiple storage devices. Level 5 RAIDs therefore offer the performance advantages of distributing data across multiple devices, but do not share the performance bottleneck of level 4 RAIDs because the parity information is also distributed through the array. RAID 5 requires at least three RAID partitions. RAID 6 - level 6 RAIDs are similar to level 5 RAIDs, but instead of storing only one set of parity data, they store two sets. RAID 6 requires at least four RAID partitions. RAID 10 - level 10 RAIDs are nested RAIDs or hybrid RAIDs. Level 10 RAIDs are constructed by distributing data over mirrored sets of storage devices. For example, a level 10 RAID constructed from four RAID partitions consists of two pairs of partitions in which one partition mirrors the other. Data is then distributed across both pairs of storage devices, as in a level 0 RAID. RAID 10 requires at least four RAID partitions.
23.15.4. Create LVM Logical Volume LVM initial set up is not available during text-mode installation. If you need to create an LVM configuration from scratch, establish another SSH connection to the installation image with the root user and run the lvm command. Logical Volume Management (LVM) presents a simple logical view of underlying physical storage space, such as a hard drives or LUNs. Partitions on physical storage are represented as physical volumes that can be grouped together into volume groups. Each volume group can be divided 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. To read more about LVM, refer to the Red Hat Enterprise Linux Deployment Guide. Note, LVM is only available in the graphical installation program. - LVM Physical Volume
Choose this option to configure a partition or device as an LVM physical volume. This option is the only choice available if your storage does not already contain LVM Volume Groups. This is the same dialog that appears when you add a standard partition - refer to Section 23.15.2, "Adding Partitions" for a description of the available options. Note, however, that File System Type must be set to physical volume (LVM)
- Make LVM Volume Group
Choose this option to create LVM volume groups from the available LVM physical volumes, or to add existing logical volumes to a volume group.
To assign one or more physical volumes to a volume group, first name the volume group. Then select the physical volumes to be used in the volume group. Finally, configure logical volumes on any volume groups using the Add, Edit and Delete options. You may not remove a physical volume from a volume group if doing so would leave insufficient space for that group's logical volumes. Take for example a volume group made up of two 5 GB LVM physical volume partitions, which contains an 8 GB logical volume. The installer would not allow you to remove either of the component physical volumes, since that would leave only 5 GB in the group for an 8 GB logical volume. If you reduce the total size of any logical volumes appropriately, you may then remove a physical volume from the volume group. In the example, reducing the size of the logical volume to 4 GB would allow you to remove one of the 5 GB physical volumes. - Make Logical Volume
Choose this option to create an LVM logical volume. Select a mount point, file system type, and size (in MB) just as if it were a standard disk partition. You can also choose a name for the logical volume and specify the volume group to which it will belong.
23.15.5. Recommended Partitioning SchemeConfiguring efficient swap space for Linux on System z is a complex task. It very much depends on the specific environment and should be tuned to the actual system load. Refer to the following resources for more information and to guide your decision: 23.16. Write changes to diskThe installer prompts you to confirm the partitioning options that you selected. Click Write changes to disk to allow the installer to partition your hard drive and install Red Hat Enterprise Linux. If you are certain that you want to proceed, click Write changes to disk. Up to this point in the installation process, the installer has made no lasting changes to your computer. When you click Write changes to disk, the installer will allocate space on your hard drive and start to transfer Red Hat Enterprise Linux into this space. Depending on the partitioning option that you chose, this process might include erasing data that already exists on your computer. To revise any of the choices that you made up to this point, click Go back. To cancel installation completely, switch off your computer. After you click Write changes to disk, allow the installation process to complete. If the process is interrupted (for example, by you switching off or resetting the computer, or by a power outage) you will probably not be able to use your computer until you restart and complete the Red Hat Enterprise Linux installation process, or install a different operating system. 23.17. Package Group SelectionNow that you have made most of the choices for your installation, you are ready to confirm the default package selection or customize packages for your system. The Package Installation Defaults screen appears and details the default package set for your Red Hat Enterprise Linux installation. This screen varies depending on the version of Red Hat Enterprise Linux you are installing. If you install Red Hat Enterprise Linux in text mode, you cannot make package selections. The installer automatically selects packages only from the base and core groups. These packages are sufficient to ensure that the system is operational at the end of the installation process, ready to install updates and new packages. To change the package selection, complete the installation, then use the Add/Remove Software application to make desired changes. By default, the Red Hat Enterprise Linux installation process loads a selection of software that is suitable for a system deployed as a basic server. Note that this installation does not include a graphical environment. To include a selection of software suitable for other roles, click the radio button that corresponds to one of the following options: - Basic Server
This option provides a basic installation of Red Hat Enterprise Linux for use on a server. - Database Server
This option provides the MySQL and PostgreSQL databases. - Web server
This option provides the Apache web server. - Enterprise Identity Server Base
This option provides OpenLDAP and Enterprise Identity Management (IPA) to create an identity and authentication server. - Virtual Host
This option provides the KVM and Virtual Machine Manager tools to create a host for virtual machines. - Desktop
This option provides the OpenOffice.org productivity suite, graphical tools such as the GIMP, and multimedia applications. - Software Development Workstation
This option provides the necessary tools to compile software on your Red Hat Enterprise Linux system. - Minimal
This option provides only the packages essential to run Red Hat Enterprise Linux. A minimal installation provides the basis for a single-purpose server or desktop appliance and maximizes performance and security on such an installation.
To customize your package set further, select the Customize now option on the screen. Clicking Next takes you to the Package Group Selection screen. 23.17.1. Installing from Additional RepositoriesYou can define additional repositories to increase the software available to your system during installation. A repository is a network location that stores software packages along with metadata that describes them. Many of the software packages used in Red Hat Enterprise Linux require other software to be installed. The installer uses the metadata to ensure that these requirements are met for every piece of software you select for installation. The Red Hat Enterprise Linux repository is automatically selected for you. It contains the complete collection of software that was released as Red Hat Enterprise Linux 6, with the various pieces of software in their versions that were current at the time of release. To include software from extra repositories, select Add additional software repositories and provide the location of the repository. To edit an existing software repository location, select the repository in the list and then select Modify repository. If you change the repository information during a non-network installation, such as from a Red Hat Enterprise Linux DVD, the installer prompts you for network configuration information. Select an interface from the drop-down menu. Click OK.
Anaconda activates the interface that you selected, then starts NetworkManager to allow you to configure the interface. If you select Add additional software repositories, the Edit repository dialog appears. Provide a Repository name and the Repository URL for its location. Once you have located a mirror, to determine the URL to use, find the directory on the mirror that contains a directory named repodata. Once you provide information for an additional repository, the installer reads the package metadata over the network. Software that is specially marked is then included in the package group selection system. If you choose Back from the package selection screen, any extra repository data you may have entered is lost. This allows you to effectively cancel extra repositories. Currently there is no way to cancel only a single repository once entered. 23.17.2. Customizing the Software Selection Your Red Hat Enterprise Linux system automatically supports the language that you selected at the start of the installation process. To include support for additional languages, select the package group for those languages from the Languages category. Users of IBM System z who want support for developing or running legacy 31-bit applications are encouraged to select the Compatibility Arch Support and Compatibility Arch Development Support packages to install architecture specific support for their systems. Select Customize now to specify the software packages for your final system in more detail. This option causes the installation process to display an additional customization screen when you select Next. Red Hat Enterprise Linux divides the included software into package groups. For ease of use, the package selection screen displays these groups as categories. You can select package groups, which group components together according to function (for example, X Window System and Editors), individual packages, or a combination of the two. To view the package groups for a category, select the category from the list on the left. The list on the right displays the package groups for the currently selected category. To specify a package group for installation, select the check box next to the group. The box at the bottom of the screen displays the details of the package group that is currently highlighted. None of the packages from a group will be installed unless the check box for that group is selected. If you select a package group, Red Hat Enterprise Linux automatically installs the base and mandatory packages for that group. To change which optional packages within a selected group will be installed, select the Optional Packages button under the description of the group. Then use the check box next to an individual package name to change its selection. In the package selection list on the right, you can use the context menu as a shortcut to select or de-select base and mandatory packages or all optional packages. After you choose the desired packages, select Next to proceed. The installer checks your selection, and automatically adds any extra packages required to use the software you selected. When you have finished selecting packages, click Close to save your optional package selections and return to the main package selection screen. The packages that you select are not permanent. After you boot your system, use the Add/Remove Software tool to either install new software or remove installed packages. To run this tool, from the main menu, select ⤍ ⤍ . The Red Hat Enterprise Linux software management system downloads the latest packages from network servers, rather than using those on the installation discs. 23.17.2.1. Core Network Services All Red Hat Enterprise Linux installations include the following network services: centralized logging through syslog email through SMTP (Simple Mail Transfer Protocol) network file sharing through NFS (Network File System) remote access through SSH (Secure SHell) resource advertising through mDNS (multicast DNS)
The default installation also provides: network file transfer through HTTP (HyperText Transfer Protocol) printing through CUPS (Common UNIX Printing System) remote desktop access through VNC (Virtual Network Computing)
Some automated processes on your Red Hat Enterprise Linux system use the email service to send reports and messages to the system administrator. By default, the email, logging, and printing services do not accept connections from other systems. Red Hat Enterprise Linux installs the NFS sharing, HTTP, and VNC components without enabling those services. You may configure your Red Hat Enterprise Linux system after installation to offer email, file sharing, logging, printing and remote desktop access services. The SSH service is enabled by default. You may use NFS to access files on other systems without enabling the NFS sharing service. 23.18. Installing PackagesAt this point there is nothing left for you to do until all the packages have been installed. How quickly this happens depends on the number of packages you have selected and your computer's speed. Depending on the available resources, you might see the following progress bar while the installer resolves dependencies of the packages you selected for installation: During installation of the selected packages and their dependencies, you see the following progress bar: 23.19. Installation CompleteCongratulations! Your Red Hat Enterprise Linux installation is now complete! The installation program prompts you to prepare your system for reboot. The installation program automatically reboots into the installed system. Should the installation program not reboot, the installation program shows information from which device to do an IPL (boot). Accept the shutdown option and after shutdown, IPL from the DASD or SCSI LUN where the /boot partition for Red Hat Enterprise Linux has been installed. To IPL from a DASD, for example using the DASD device 200 on the 3270 console, issue the command: #cp i 200
In DASD only environments where automatic partitioning (clearing data from all partitions) was used, the first activated DASD is where the /boot partition is typically located. Using /boot on an FCP LUN, you must provide the WWPN and LUN for the FCP-attached device from which to IPL. To IPL from an FCP-attached device: Provide FCP routing information to an FCP-attached device, for example, where 0x50050763050B073D is the WWPN, and 0x4020400100000000 is the FCP LUN: #cp set loaddev portname50050763 050B073D lun 40204001 00000000
IPL the FCP adapter, for example FC00: #cp ipl FC00
To disconnect from the 3270 terminal without stopping the Linux running in your virtual machine, use #cp disconnect instead of #cp logoff. When your virtual machine is re-connected using the usual logon procedure, it might be placed in CP console function mode (CP READ). If so, to resume execution on your virtual machine, enter the BEGIN command. For LPAR-based installations, on the HMC, issue a load command to the LPAR, specifying the particular DASD, or the FCP adapter, WWPN, and FCP LUN where the /boot partition is located. 23.19.3. Continuing after Reboot (re-IPL)Following the automatic reboot or the manual IPL of the installed Red Hat Enterprise Linux operating system, you can log on to the system via ssh. Note that the only place from which you can log in as root is from the 3270 terminal or from other terminal devices listed in /etc/securetty. The first time you start your Red Hat Enterprise Linux system in a graphical environment, you can use FirstBoot to guide you through Red Hat Enterprise Linux configuration. Using this tool, you can set your system time and date, install software, register your machine with Red Hat Network, and more. FirstBoot lets you configure your environment at the beginning, so that you can get started using your Red Hat Enterprise Linux system quickly. |
| |
