Scientific Linux 5.3 (Boron)

  Please see the individual copyright notices in each source package
  for distribution terms.

  Red Hat and RPM are trademarks of Red Hat, Inc.

  ---------------------------------------------------------------------------

DIRECTORY ORGANIZATION

  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.53.*.disc1.iso
       SL.53.*.disc2.iso
       SL.53.*.disc3.iso
       SL.53.*.disc4.iso
       SL.53.*.disc5.iso
       SL.53.*.disc6.iso
       SL.53.*.disc7.iso
       SL.53.*.disc8.iso

/mnt/cdrom
  |----> 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-53-*-DVD-disc*.iso image contains the DVD sized installation.


/mnt/cdrom
  |----> 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.)


INSTALLING

  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.

 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.

GETTING HELP

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

  http://www.scientificlinux.org/maillists/

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

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

  subscribe scientific-linux-users

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.

You are viewing proxied material from ftp.icm.edu.pl. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.