PU_IAS Linux is delivered on multiple 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 /media/cdrom is the mount point of the CD-ROM):

      

/media/cdrom
  |----> Client		  -- binary packages of the Core "knowledgeworker" desktop
  |        `----> repodata     -- information on this release of PU_IAS
  |                               Linux used by the installation process
  |----> Workstation  	  -- binary packages for Development and Engineering
  |                               Workstation option
  |        `----> repodata     -- information on Workstation used by the installation process
  |----> Server                -- binary packages of the core server product
  |        `----> repodata     -- information on this release of PU_IAS
  |                               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 and driver disk images
  |----> isolinux              -- Files used for booting from CD
  |----> README                -- this file
  |----> RELEASE-NOTES         -- the latest information about this release
  |                               of PU_IAS Linux
  `----> RPM-GPG-KEY-pu_ias
			       -- GPG signature for packages from PU_IAS


    

The directory layout of each source code CD-ROM is as follows:

/media/cdrom
  |----> SRPMS                 -- source packages
  `----> RPM-GPG-KEY-pu_ias
			       -- GPG signature for packages from PU_IAS

    

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

(Where <target-directory> represents the path to the directory to contain the installation tree.)

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

The images/ directory contains the file boot.iso. This file is an ISO image that can be used to boot the PU_IAS 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 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.

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.

http://www.elders.princeton.edu

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.