Index of /linux/scientific/5x/x86_64

      Name                    Last modified       Size  Description

[DIR] Parent Directory 24-Apr-2012 15:55 - [TXT] EULA 08-Mar-2012 23:25 5k [TXT] GPL 30-Jun-2006 05:10 18k [TXT] RELEASE-NOTES-C.html 18-Apr-2012 21:38 2k [TXT] RELEASE-NOTES.html 18-Apr-2012 21:38 2k [DIR] RHupdates/ 19-Apr-2012 21:16 - [DIR] RPM-GPG-KEYs/ 19-Apr-2012 21:16 - [DIR] SL.documentation/ 19-Apr-2012 21:16 - [TXT] SL.releasenote 19-Apr-2012 18:28 43k [DIR] SL/ 06-May-2012 14:36 - [DIR] build/ 19-Apr-2012 21:22 - [DIR] contrib/ 19-Apr-2012 21:22 - [DIR] images/ 19-Apr-2012 21:22 - [DIR] isolinux/ 19-Apr-2012 21:22 - [DIR] updates/ 19-Apr-2012 21:16 -

                     Scientific Linux 5.8 (Boron)

   Please see the individual copyright notices in each source package
   for distribution terms. 
   Red Hat and RPM are trademarks of Red Hat, Inc.



   Scientific Linux is delivered on multiple CD or DVD iso images  consisting of
   installation iso images and extra 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 /mnt/cdrom is the mount point of the CD-ROM):

The cd iso images are 
   |----> SL/ 			-- binary packages
   |----> images/               -- boot and driver disk images
   |----> isolinux              -- Files used for booting from CD
   |----> README                -- this file
   |----> SL.documentation/     -- Directory containing release documentation
   |----> SL.releasenote        -- the latest information about this release
   |                               of Scientific Linux
   `----> RPM-GPG-KEYs/  	-- Directory containing GPG signature for packages

The SL-58-*-DVD-disc*.iso image contains the DVD sized installation.  

   |----> SRPMS/                -- SRPMS
   |----> build/                -- build scripts 
   |----> updates/		-- fastbugs and security
   |----> contrib/ 		-- contrib
   |----> sites/                -- Example site 

   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 SL 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):

    1. Insert CD-ROM / DVD

    2. mount /mnt/cdrom

    3. cp -a /mnt/cdrom/ <target-directory>

    5. umount /mnt/cdrom

   (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 Scientific
   Linux Installation CD-ROM 1 directly. After booting, the Scientific
   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 Scientific 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.


   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.


   For those that have web access, refer to In
   particular, access to our mailing lists can be found at:

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

   To subscribe, send mail to
   leave the subject line blank, and enter the following line as your 
   message body

   subscribe scientific-linux-users 

   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