Hi Troy,

> Now that it's released, if we change it, it will break any scripts 
> looking for it in the way that it currently is.

But if you _don't_ change it, the program lsb_release (from package
redhat-lsb) does not work correctly. This is what is gives on a pristine
SL4 system:

[mok@sebulpa ~]$ lsb_release --all
LSB Version:    1.3
Distributor ID: n/a
Description:    Scientific Linux SL Release 4.0 (Beryllium)
Release:        n/a
Codename:       n/a

When I change "Release" to "release" in /etc/redhat-release, this is 
what I get:

[mok@sebulpa ~ ]$ lsb_release --all
LSB Version:    1.3
Distributor ID: ScientificSL
Description:    Scientific Linux SL release 4.0 (Beryllium)
Release:        4.0
Codename:       Beryllium


IMHO, fixing the "R" -> "r" in /etc/redhat-release is a bug and it 
should be fixed. If peoples scripts rely on that bug, they will have to 
fix them, too.

Sorry to be so anal about it, but I am working on a Python class that
collects information about the distribution it is running on, and SL
breaks it.

Cheers,
Morten


PS: 

According LSB, the release information should be present in the file
/etc/lsb-release, which OUGHT to contain (for SL):

LSB Version: 1.3
Distributor ID: Scientific Linux
Release: 4.0
Codename: Beryllium
Description: Scientific Linux SL release 4.0 (Beryllium)

As a distributor, you are entitled/required to provide this file.



-- 
Morten Kjeldgaard, Asc. professor, Ph.D.
Department of Molecular Biology, Aarhus University
Gustav Wieds Vej 10 C, DK-8000 Aarhus C, Denmark
Lab +45 89425026 * Mobile +45 51860147 * Fax +45 86123178
Home +45 86188180 * ICQ 27224900 * http://www.bioxray.dk/~mok