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: Tue, 17 Nov 1998 06:29:31 -0600
Reply-to: aclug-L@xxxxxxxxxxxx

John Goerzen wrote:

> libc is a higher level than the kernel.  The kernel doesn't care which libc
> you're using, as long as it's 5 or greater (4 was for a different executable
> format).

hmmmm...

Apparently I have much to learn regarding the relationship between the
kernel and the C library.  My assumption (mistake?) is that since the
kernel is written mostly in C that it must use the services of whatever
library /lib/libc.so points to.  Does it not, or does it simply
statically link all the relavant libc code?  Logically, I can see where
the kernel cannot rely on a dynamically linked library as it does many
things before the file systems are mounted.  Also, I can see that if the
kernel uses statically linked code in its C routines, that would allow
it to run on a glibc based system even if compiled on a libc5 based
system.  Have I guessed right?

- 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]