Skip to content.

Scientific Linux

Sections
Personal tools
You are here: Home » Distributions » 30x » Release Notes » README x86_64

README x86_64

Scientific Linux 3.0.4

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 seven 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
|----> SL
| |----> RPMS -- binary packages
| `----> base -- information on this release of Scientific
| Linux used by the installation
| process
|----> dosutils -- installation utilities for DOS
|----> images -- boot CD-ROM image
|----> isolinux -- Files used for booting from CD
|----> README -- this file
|----> RELEASE-NOTES -- the latest information about this release
| of Scientific Linux
`----> RPM-GPG-KEY -- GPG signature for packages from Red Hat


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

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

/mnt/cdrom
|----> SRPMS -- source packages
`----> RPM-GPG-KEY -- 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 SL 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):

1. Insert CD-ROM

2. mount /mnt/cdrom

3. cp -a /mnt/cdrom/SL /target/directory

4. cp /mnt/cdrom/RELEASE-NOTES* /target/directory (Installation CD 1
only)

5. umount /mnt/cdrom

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 without using any boot
diskettes. 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 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.

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 listserv@fnal.gov
leave the subject line blank, and enter the following line as your
message body

subscribe scientific-linux-users

As of this writting, subscriptions to scientific-linux-users is done by hand.
When you request to subscribe you will be asked what your interest in
Scientific Linux is. Do not be alarmed, we are just finding out what is
bringing people to Scientific Linux.

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.
Created by dawson
Contributors :
Last modified 2006-03-29 10:27 AM
 

Powered by Plone

This site conforms to the following standards: