From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Lev Lvovsky <lists1@sonous.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: older kernels + new glibc?
Date: Mon, 29 Mar 2004 16:17:32 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0403291602340.2893@chaos> (raw)
In-Reply-To: <5516F046-81C1-11D8-A0A8-000A959DCC8C@sonous.com>
On Mon, 29 Mar 2004, Lev Lvovsky wrote:
> Hello,
>
> I'm not sure what, if any interrelations there are between the various
> versions of glibc, and the kernel.
>
> Specifically, a piece of telecom hardware that we use out in the field
> requires a 2.2.x kernel to compile the drivers, however, after choosing
> an arbitrary "new" release of a linux distro, and downgrading the
> kernel, we are able to compile and install the drivers, and
> subsequently use the hardware.
>
> Are there any URLs/Docs that I could look at to understand what, if any
> relationships glibc, and the kernel have?
>
> thank you!
> -lev
For glibc compatibility you need to get rid of the sym-link(s)
/usr/include/asm and /usr/include/linux in older distributions.
You need to replace those with headers copied from the kernel
in use when the C runtime library was compiled. If you can't find
those, you can either upgrade your C runtime library, or copy
headers from some older kernel that was known to work.
In any event, you need to remove the sym-link that ends up
pointing to your 'latest and greatest' kernel.
If you do this, you should find no incompatibilities between
user-mode code and any (within reason, 0.99 might not work)
kernel version.
Drivers are a different problem. There is no possibility
of just compiling old drivers and having them work. Drivers
need to be modified for each kernel version major version
number and, sometimes, even minor version numbers.
Sometimes you are lucky, usually not. Modules written for
2.4.x will not compile on 2.6.x and there is no compatibility
layer to accommodate. You need to look at how new modules are
written for a new version and modify your module code
accordingly. One can usually just compile and then 'fix' the
resulting errors. However, this might not produce a working
driver because some functions you count on might not exist
anymore. It compiles fine, but won't install.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-03-29 21:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 20:40 Lev Lvovsky
2004-03-29 21:00 ` Arjan van de Ven
2004-03-29 21:09 ` Lev Lvovsky
2004-03-29 21:22 ` Arjan van de Ven
2004-03-29 21:26 ` Lev Lvovsky
2004-03-29 21:28 ` Arjan van de Ven
2004-03-29 21:34 ` Lev Lvovsky
2004-03-29 21:36 ` Arjan van de Ven
2004-03-29 21:45 ` Chris Meadors
2004-03-29 23:03 ` David T Hollis
2004-03-30 15:07 ` Adrian Bunk
2004-03-31 0:54 ` GOTO Masanori
2004-03-29 21:17 ` Richard B. Johnson [this message]
2004-03-29 21:36 ` Lev Lvovsky
2004-03-29 21:50 ` Richard B. Johnson
2004-03-29 21:55 ` Lev Lvovsky
2004-03-29 22:10 ` Richard B. Johnson
2004-03-29 22:55 ` Lev Lvovsky
2004-03-30 12:19 ` Richard B. Johnson
2004-03-29 22:27 ` DervishD
2004-03-29 23:55 ` Matthew Reppert
2004-03-30 0:09 ` Lev Lvovsky
2004-03-30 14:50 ` DervishD
2004-03-30 15:15 ` Richard B. Johnson
2004-03-30 17:10 ` DervishD
2004-03-30 12:16 ` Richard B. Johnson
2004-03-30 15:20 ` DervishD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.53.0403291602340.2893@chaos \
--to=root@chaos.analogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists1@sonous.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®