The race to GCC 3

[jabr at blu.org (John Abreau)]

David Kramer <david at thekramers.net> writes:

> So I guess we won't be able to easily upgrade from 7.3 to 8.0.  I spent way 
> too much time getting my server right to start from e2fsck again.

Historically, Redhat has generally included optional legacy libraries to 
support older binaries. I remember going through this back when the binary 
format changed from COFF to ELF, and again when the libc was changed from 
libc5 to glibc. 

Even now, in Redhat 7.3, I see a bunch of compat RPMs:

    XFree86-compat-libs-4.0.3-2.i386.rpm
    XFree86-compat-modules-3.3.6-44.i386.rpm
    compat-egcs-6.2-1.1.2.16.i386.rpm
    compat-egcs-c++-6.2-1.1.2.16.i386.rpm
    compat-egcs-g77-6.2-1.1.2.16.i386.rpm
    compat-egcs-objc-6.2-1.1.2.16.i386.rpm
    compat-glibc-6.2-2.1.3.2.i386.rpm
    compat-libs-6.2-3.i386.rpm
    compat-libstdc++-6.2-2.9.0.16.i386.rpm
    kde1-compat-1.1.2-11.i386.rpm
    kde1-compat-devel-1.1.2-11.i386.rpm
    kde2-compat-2.2.2-2.i386.rpm
    nss_db-compat-2.2-14.i386.rpm

It's a good idea to test the 8.0 install on a spare box before upgrading 
a production server, of course. But given their past history, I'd be 
surprised if Redhat 8.0 didn't provide for compatibility with 7.x binaries.


-- 
John Abreau / Executive Director, Boston Linux & Unix 
IM: jabr at jabber.blu.org / abreauj at aim / abreauj at yahoo / 28611923 at icq
Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9
PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99

   Some people say, "The enemy of my enemy is my friend."
   I often respond, "When elephants fight, it's the grass
   that gets trampled."



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 344 bytes
Desc: not available
URL: <http://lists.blu.org/pipermail/discuss/attachments/20020928/f62e12fb/attachment.sig>