From: GOTO Masanori <gotom@debian.or.jp>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: older kernels + new glibc?
Date: Wed, 31 Mar 2004 09:54:22 +0900 [thread overview]
Message-ID: <81isglx2dd.wl@omega.webmasters.gr.jp> (raw)
In-Reply-To: <20040330150719.GK22291@fs.tum.de>
At Tue, 30 Mar 2004 17:07:20 +0200,
Adrian Bunk wrote:
> On Mon, Mar 29, 2004 at 11:22:24PM +0200, Arjan van de Ven wrote:
> >...
> > supplied there if it'll work or not. if you tell glibc that at minimum
> > you do 2.4.1 for example, then no a 2.2 kernel won't work. I think most
> > distros do this (or an even later version) since a few years now.
>
> In Debian 3.0, it's set to kernel 2.2.
FYI, it's set to 2.2 except for i386 and m68k (they are 2.0.30).
> And it currently seems even the next stable release of Debian will have
> it set to 2.2 on all architectures except sparc64 and s390x.
Plus i686.
Regards,
-- gotom
next prev parent reply other threads:[~2004-03-31 0:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 20:40 older kernels + new glibc? 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 [this message]
2004-03-29 21:17 ` Richard B. Johnson
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=81isglx2dd.wl@omega.webmasters.gr.jp \
--to=gotom@debian.or.jp \
--cc=bunk@fs.tum.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.