mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Frédéric L. W. Meunier" <1@pervalidus.net>
To: linux-kernel@vger.kernel.org
Subject: Re: FATAL: Kernel too old
Date: Sat, 7 Feb 2004 12:00:15 -0200 (BRST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0402071141580.2139@pervalidus.dyndns.org> (raw)
In-Reply-To: <200402070741.56848.andrew@walrond.org>

On Sat, 7 Feb 2004, Andrew Walrond wrote:

> I have seen this message when trying to use a glibc configured with
>         --enable-kernel=2.4.20
> on a machine running a 2.4.19 kernel.
>
> You haven't either upgraded glibc or started using an older kernel, have you?

I think it also happens if you run a binary compiled on a
machine with such a glibc on another which has an older kernel
or the same glibc, but compiled with no --enable-kernel or an
older version set.

Can't test it, but:

My glibc was compiled with --enable-kernel=2.4.5.

A binary compiled with it:

% file /usr/bin/lsattr
/usr/bin/lsattr: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.4.5, dynamically linked (uses shared libs), stripped

A binary that came with the default glibc:

% file /usr/bin/ansi2knr
/usr/bin/ansi2knr: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.0.0, dynamically linked (uses shared libs), stripped

Yes, the default glibc was compiled without --enable-kernel, so
is compatible with >= 2.0.0.

Anyway, not a kernel problem. I have also seen it when trying
to emulate my binaries on FreeBSD, which has compatibility set
to... 2.4.2.

-- 
http://www.pervalidus.net/contact.html

      reply	other threads:[~2004-02-07 14:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06 21:16 Richard B. Johnson
2004-02-06 21:29 ` Charles Cazabon
2004-02-06 21:52   ` Frédéric L. W. Meunier
2004-02-06 22:20   ` Richard B. Johnson
2004-02-06 23:22     ` Bryan Andersen
2004-02-07  6:27     ` Karl Tatgenhorst
2004-02-07  7:41 ` Andrew Walrond
2004-02-07 14:00   ` Frédéric L. W. Meunier [this message]

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.58.0402071141580.2139@pervalidus.dyndns.org \
    --to=1@pervalidus.net \
    --cc=linux-kernel@vger.kernel.org \
    /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®