Read Scientific.Linux.March.pdf text version

Scientific Linux

Troy Dawson

[email protected]

Fermilab

Encompass Linux TAG

March 8, 2005

Scientific Linux

Why What How Continuing Errata Support Where Followup

Why We Made Scientific Linux

Fermi Linux (1998)

­ ­

Various Linux Distributions were appearing Based on Red Hat freely available version

5.0.2, 5.2.1, 6.1.x, 7.1.x, 7.3.x, 9.0.x

­

­ ­

Security Hardening AutoRPM, YUM (Automatic Security Updates) All services turned off by default Workgroups one size doesn't fit all Tweaks configuration modifications

Freely distributable

Why We Made Scientific Linux

RedHat made policy changes

­

End of free RedHat

Discussion at Fermilab and other High Energy Physics Labs about moving to something else

­ ­ ­ ­

At least 3 years support Installer modifiable and usable Freely distributable Easy transition from RedHat based distro RHEL, SUSE, Mandrake, Debian, Fedora Compile our own, from any of the above.

Various Choices

­ ­

Why We Made Scientific Linux

Fermilab had to provide a release before RedHat's support went away. Fermilab created a Fermi Linux rebuilt from RHEL source rpm's.

­ ­ ­ ­

Even if we bought RHEL, we would have to do much of the same work. It is freely distributable Already have large install base We had the expertise

Why We Made Scientific Linux

Why make Scientific Linux?

­

Other HEP Lab's had same Linux issues

Binary compatibility between labs would be advantageous. Email from CERN wishing to collaborate Collaboration would make product better Wouldn't have to 'un-fermi'ize it

­

Non-Fermi users were using Fermi Linux

­

Effort wouldn't be much more than existing effort

Scientific Linux

Follow up

­ ­ ­ ­ ­

S.L. 3.0.1 was created by Fermilab to see what the HEP Community thought. Response to S.L. 3.0.1 was very positive. S.L. 3.0.2 was our first collaboration release, mainly working with CERN S.L. 3.0.3 had the collaboration ironed out Collaboration has expanded since then.

The last version digit is the RHEL Update number

What Is Scientific Linux?

Recompiled Red Hat Enterprise Linux Value Added

­ ­

Changes Additions

packages tweaks

What Is Scientific Linux?

Changes

­ ­

Where we legally must because of RedHat's trademark's Where we morally felt we should.

Bookmarks, Up2date (automated patch updates) Gives facilities choice

­ ­ ­

­

Installation program modified for Sites

What packages are installed Add, delete, modify packages Customize installer program

What Is Scientific Linux?

Additions

­

Packages

Consolidated RHEL suites

­

GFS, Developer Suite, Cluster Suite OpenAFS pine, perl-CPAN, icewm

Commonly used in science

­

That we felt were missing

­

What Is Scientific Linux?

Additions

­

Tweaks

Easily installed Don't have to modify original package Not installed by default Modifies standard configuration's

­ ­ ­ ­

color ls Turns off color ls terminal button on desktop panel security enhancements serial console output

How We Build Scientific Linux

Install the last public RHEL beta release Get the src.rpm's when RHEL is released Compile all the src.rpm's. Install packages just compiled Recompile all src.rpm's again Verify contents against RHEL release Re-Install packages again Use chroot if shortage of hardware

How We Build Scientific Linux

Scripts and Macro's

­

buildrpms.sh

Builds all src.rpm's in the local SRPMS directory

­ ­

Output from build put in status directory Rpm macro's put built rpm's into special directory Output is removed from status directory src.rpm's are moved to the done.SRPMS directory. Failed src.rpm's are left in SRPMS directory Failed output is left in the status directory

If it succeeds

­ ­

If it fails

­ ­

How We Build Scientific Linux

Scripts and Macro's

­

Rpmmacros

%vendor Scientific Linux %_rpmdir /usr/src/redhat/4/RPMS

Keeping Errata Current

Checking and Getting Errata

­

[email protected]

Notifies of security updates for all RHEL releases Check to make sure all the new src.rpm's were announced in the mail list. Download errata src.rpm's.

­

ftp://ftp.redhat.com/ or mirrors

Rebuild errata source rpm's

Keeping Errata Current

Getting Errata published

­ ­

Digitally sign all rpm's Move to version/arch dependent errata area's

We use scripts to decrease errors

­ ­

Copies the errata to the appropriate place(s) Updates Yum and Apt repositories

­

Each night a yum or apt cron script runs on clients and pulls down the new errata

Admins can turn the cron scripts off Clients can point to a local mirror

Where Is Everything

ftp://ftp.scientificlinux.org/linux/scientific/

­

301,302,303...

These are the releases Links pointing to the latest release The unstable, or 'rolling' release

­

30x, 4x, ...

­

30rolling, 40rolling, ...

Where Is Everything

302 (a typical stable release)

­

I386, x86_64, ia64

The release for each architecture The source rpm's for everything The iso's (or CD images) for all architectures.

­

SRPMS

­

Isos

Where Is Everything

SRPMS

­

<package>.src.rpm

S.L. Modified or added rpm's. Original source rpm's from the initial release Source rpm's from errata released from the vendor.

­

vendor/original/

­

vendor/errata/

Where Is Everything

I386 (or any arch)

­

RHupdates

quick customizations to the installer go here Key's that have signed the rpm's Release notes and documentation apt repository for this release/architecture

­

RPM-GPG-KEYs

­

SL.documentation

­

apt-rpm

Where Is Everything

i386 (or any arch)

­

SL/RPMS

RPM's that were released with the release comps.xml, hdlist, and other files that determine what get's installed during installation scripts and files used to build the distribution

­

SL/base

­

SL/build

Where Is Everything

i386 (or any arch)

­

contrib

packages that for one reason or another are not part of the base S.L. utilities that run in dos install images other than the main CD iso images.

­

dosutils

­

images

Where Is Everything

i386 (or any arch)

­

errata/SL

Where the errata packages go Where the various debuginfo packages go Where packages that have been replaced go

­

errata/debuginfo

­

errata/obsolete

Where Is Everything

i386 (or any arch)

­

isolinux

used with full CD images. What the bios points to when booting the CD Can be different for each release Always contains the link to the yum-conf or aptsources for that release

­

misc

Where Is Everything

i386 (or any arch)

­

sites/ (a release within a release)

example

­ ­ ­ ­ ­ ­ ­ ­

RHupdates SRPMS Updates Same functionality as SL/RPMS base build documentation errata images

S.L. and Corporations

Corporations using Scientific Linux

­ ­

Fine and legal If more than 5 computers are using Scientific Linux, the corporation must make it's own mirror and point it's computers at the mirror for updates and/or installation

S.L. and Corporations

Selling Scientific Linux as a product

­ ­

Do not do this. Why?

We ask you not to WE DO NOT WANT TO COMPETE WITH REDHAT The licenses in Scientific Linux might not allow them to be sold.

References

https://www.scientificlinux.org/ ftp://ftp.scientificlinux.org/linux/scientific/ Sites of Scientific Linux

­ ­ ­ ­

http://www-oss.fnal.gov/projects/fermilinux/ http://www-oss.fnal.gov/projects/fermilinux/common/stats/ http://linux.web.cern.ch/linux/scientific3/ http://www-zeuthen.desy.de/linuxsl3

Information

28 pages

Report File (DMCA)

Our content is added by our users. We aim to remove reported files within 1 working day. Please use this link to notify us:

Report this file as copyright or inappropriate

1032192