CentOS 3.4

CentOS is delivered on six CD-ROMs consisting of installation CD-ROMs and source code CD-ROMs.

The first Installation CD-ROM can be directly booted into the installation on most modern systems, and contains the following directory structure (where /mnt/cdrom is the mount point of the CD-ROM):

      

/mnt/cdrom
  |----> RedHat
  |        |----> RPMS         -- binary packages
  |        `----> base         -- information on this release of CentOS
  |                               used by the installation process
  |----> dosutils              -- installation utilities for DOS
  |----> images                -- boot and driver disk images
  |----> isolinux              -- Files used for booting from CD
  |----> README                -- this file
  |----> RELEASE-NOTES         -- the latest information about this release
  |                               of CentOS
  `----> RPM-GPG-KEY-CentOS-3  -- GPG signature for packages

    

The remaining Installation CD-ROMs are similar to Installation CD-ROM 1, except that only the RedHat subdirectory is present.

The directory layout of all Source Code CD-ROMs are as follows:

/mnt/cdrom
  `----> SRPMS                 -- source packages

    

In addition the addons repository is stored on the fourth CD (Source 1) in /addons/ and the docs are stored on the third CD (Binary 3) in /docs/

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 Installation CD-ROMs. On Linux and UNIX systems, the following process will properly configure the /target/directory on your server (repeat for each disc):

Many computers can now automatically boot from CD-ROMs. If you have such a machine (and it is properly configured) you can boot the CentOS Installation CD-ROM 1 directly without using any boot diskettes. After booting, the CentOS installation program will start, and you will be able to install your system from the CD-ROM.

If your computer must use a boot diskette to start the CentOS installation process, you must use one or more image files to create the necessary diskettes. You can find the necessary image files in the images/ directory. This directory contains the following image files:

A diskette created from the the bootdisk.img file is used to boot all installations, no matter what installation method you select.

In addition, if you are performing anything other than a CD-ROM or hard disk installation using only IDE/ATAPI devices, you must also create one or more driver diskettes using one or more of the driver diskette image files.

A diskette created from the drvblock.img file is required when the system contains any non-IDE mass storage devices (such as SCSI disk or CD-ROM drives) that are to be used during the installation.

A diskette created from the drvnet.img file is required when a network-based installation method is to be used.

A diskette created from the pcmciadd.img file is required when PCMCIA devices (such as a PCMCIA-based CD-ROM drive or network adapter) are to be used during the installation.

To write any of these image files to a diskette, use either the rawrite program in the dosutils/ directory, or dd under any Linux-like system. These programs will transfer the contents of the image file to a diskette. Once the necessary diskettes have been created, insert the boot diskette and boot your machine.

The images/ directory contains the file boot.iso. This file is an ISO image that can be used to boot the CentOS installation program. It is a handy way to start network-based installations without having to use multiple diskettes. To use boot.iso, your computer must be able to boot from its CD-ROM drive, and its BIOS settings must be configured to do so. You must then burn boot.iso onto a recordable/rewriteable CD-ROM.

For those that have web access, refer to http://www.centos.org. In particular, access to our mailing lists can be found at:

http://lists.caosity.org/mailman/listinfo

If you do not have web access you can still subscribe to the main mailing list.

To subscribe, send mail to [email protected] with subscribe in the subject line. You can leave the body empty.

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.