Red Hat Enterprise Linux 5.3 Readmes README file Logo Red Hat Enterprise Linux Documentation Don Domingo Engineering Services and Operations Content Services ddomingo@redhat.com Copyright © 2008 Legal Notice Copyright © 2008 . This material may only be distributed subject to the terms and conditions set forth in the Open Publication License, V1.0 or later (the latest version of the OPL is presently available at http://www.opencontent.org/openpub/). Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat, Inc. in the United States and other countries. All other trademarks referenced herein are the property of their respective owners. 1801 Varsity Drive Raleigh, NC 27606-2072 USA Phone: +1 919 754 3700 Phone: 888 733 4281 Fax: +1 919 754 3701 PO Box 13588 Research Triangle Park, NC 27709 USA Abstract This document contains basic installation instructions for Red Hat Enterprise Linux 5.2. ------------------------------------------------------------------ 1. DIRECTORY ORGANIZATION 2. INSTALLING 3. GETTING HELP 4. EXPORT CONTROL 1. DIRECTORY ORGANIZATION Red Hat Enterprise Linux is delivered on multiple ISO images consisting of installation ISO images and source code ISO images. The first installation ISO image can be directly booted into the installation on most modern systems, and contains the following directory structure (where /media/cdrom is the mount point of the ISO image): (x86) (x86_64) /media/cdrom |----> Server -- binary packages of the core server product | `----> repodata -- information on this release of Red Hat | Enterprise Linux used by the installation | process |----> Cluster -- binary packages for the failover clustering and load balancing | option | `----> repodata -- information on Cluster used by the installation | process |----> ClusterStorage -- binary packages for the parallel clustered filesystem and | clustered volume management option | `----> repodata -- information on ClusterStorage used by the installation | process |----> VT -- binary packages for the Virtualization options | `----> repodata -- information on the Virtualization options used by the | installation process |----> images -- boot ISO image image |----> isolinux -- Files used for booting from image |----> README -- this file |----> RELEASE-NOTES -- the latest information about this release | of Red Hat Enterprise Linux `----> RPM-GPG-KEY-redhat-release -- GPG signature for packages from Red Hat /media/cdrom |----> Client -- binary packages of the Core "knowledgeworker" desktop | `----> repodata -- information on this release of Red Hat | Enterprise Linux used by the installation | process |----> Workstation -- binary packages for Development and Engineering | Workstation option | `----> repodata -- information on Workstation used by the installation process |----> VT -- binary packages for the Virtualization options | `----> repodata -- information on Virtualization used by the installation process |----> images -- boot ISO image image |----> isolinux -- Files used for booting from image |----> README -- this file |----> RELEASE-NOTES -- the latest information about this release | of Red Hat Enterprise Linux `----> RPM-GPG-KEY-redhat-release -- GPG signature for packages from Red Hat (ia64) (ppc) (s390x) The directory layout of each source code ISO image is as follows: /media/cdrom |----> SRPMS -- source packages `----> RPM-GPG-KEY-redhat-release -- GPG signature for packages from Red Hat If you are setting up an installation tree for NFS, FTP, or HTTP installations, you must copy the RELEASE-NOTES files and all files from the RedHat directory on all operating systems ISO images. On Linux and UNIX systems, the following process will properly configure the target directory on your server (repeat for each CD-ROM/ISO image):  1. Insert CD-ROM.  2. mount /media/cdrom  3. If you are installing the Server variant, run cp -a /media/cdrom/Server If you are installing the Client variant, run cp -a /media/cdrom/Client  4. cp /media/cdrom/RELEASE-NOTES* (Installation CD 1 only)  5. cp /media/cdrom/images (Installation CD 1 only)  6. umount /media/cdrom (Where represents the path to the directory to contain the installation tree.) Note Do not copy the Supplementary ISO image, or any of the layered product ISO images, as this will overwrite files necessary for Anaconda's proper operation. These ISO images must be installed after Red Hat Enterprise Linux has been installed. 2. INSTALLING Many computers can now automatically boot from ISO images. If you have such a machine (and it is properly configured) you can boot the Red Hat Enterprise Linux Installation ISO image 1 directly. After booting, the Red Hat Enterprise Linux installation program will start, and you will be able to install your system from the ISO image. The images/ directory contains the file boot.iso. This file is an ISO image that can be used to boot the Red Hat Enterprise Linux installation program. It is a handy way to start network-based installations. To use boot.iso, your computer must be able to boot from its ISO image drive, and its BIOS settings must be configured to do so. You must then burn boot.iso onto a recordable/rewriteable ISO image. Another image file contained in the images/ directory is diskboot.img. This file is designed for use with USB pen drives (or other bootable media with a capacity larger than a diskette drive). Use the dd command to write the image. Note The ability to use this image file with a USB pen drive depends on the ability of your system's BIOS to boot from a USB device. 3. GETTING HELP For those that have web access, refer to http://www.redhat.com. In particular, access to our mailing lists can be found at: http://www.redhat.com/mailing-lists If you do not have web access you can still subscribe to the main mailing list. To subscribe, send an email to rhelv5-announce@redhat.com and rhelv5-beta-list@redhat.com with subscribe in the subject line. You can leave the body empty. Some updates on Red Hat Enterprise Linux 5 may not appear in this version of the README. An updated version of the README may also be available at the following URL: 4. EXPORT CONTROL As required by U.S. law, user represents and warrants that it: (a) understands that certain of the software are subject to export controls under the U.S. Commerce Departments Export Administration Regulations (EAR); (b) is not located in a prohibited destination country under the EAR or U.S. sanctions regulations (currently Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria); (c) will not export, re-export, or transfer the software to any prohibited destination, entity, or individual without the necessary export license(s) or authorizations(s) from the U.S. Government; (d) will not use or transfer the software for use in any sensitive nuclear, chemical or biological weapons, or missile technology end-uses unless authorized by the U.S. Government by regulation or specific license; (e) understands and agrees that if it is in the United States and exports or transfers the Software to eligible end users, it will, as required by EAR Section 741.17(e), submit semi-annual reports to the Commerce Departments Bureau of Industry & Security (BIS), which include the name and address (including country) of each transferee; and (f) understands that countries other than the United States may restrict the import, use, or export of encryption products and that it shall be solely responsible for compliance with any such import, use, or export restrictions. References Visible links . mailto:ddomingo@redhat.com . http://www.opencontent.org/openpub/ . http://www.redhat.com/ . http://www.redhat.com/mailing-lists . mailto:rhelv5-announce@redhat.com . mailto:rhelv5-beta-list@redhat.com