Complete.Org: Mailing Lists: Archives: discussion: November 1998:
Re: [aclug-L] Kernel transportability
Home

Re: [aclug-L] Kernel transportability

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: aclug-L@xxxxxxxxxxxx
Subject: Re: [aclug-L] Kernel transportability
From: Nate Bargmann <ka0rny@xxxxxxxxxx>
Date: Mon, 16 Nov 1998 06:37:21 -0600
Reply-to: aclug-L@xxxxxxxxxxxx

Nate Bargmann wrote:

> Since all Slackware releases up to and including 3.6 are libc5.x.x based
> and Red Hat since 5.0 uses glibc2.0.x.  Or, is glibc2.0.x backward
> compatible with libc5.x.x, but not vice versa?  I have no first hand
> knowledge trying to do this, but I've seen much discussion on libc5 vs.
> glibc2, so that's why I ask the questions!

Proof that one should not type/proofread before coffee :)

I was trying to say that since Slackware builds and links apps against
libc5.x.x libraries by default, even though Slackware 3.6 includes
glibc2.0.x as a runtime library, and Red hat 5.x builds/links against
glibc2.0.x, would a kernel built on a Slackware system then be usable on
a Red Hat 5.x system?  Again, I don't know.

There, is that comprehensible?

- Nate >>

-- 

 Packet   | KA0RNY @ WF0A.#SCKS.KS.USA.NOAM     | "Depression is
 Internet | ka0rny@xxxxxxxxxx                   | merely anger
 Location | Valley Center, Kansas USA EM17hs    | without
        Visit my Linux + Ham Radio pages        | enthusiasm."
   http://homepage.netspaceonline.com/~ka0rny/  |
---
This is the Air Capitol Linux Users Group discussion list.  If you
want to unsubscribe, send the word "unsubscribe" to
aclug-L-request@xxxxxxxxxxxx.  If you want to post to the list, send your
message to aclug-L@xxxxxxxxxxxx.



[Prev in Thread] Current Thread [Next in Thread]