mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Frank Cusack <fcusack@fcusack.com>
Cc: lkml <linux-kernel@vger.kernel.org>, phil-list@redhat.com
Subject: Re: NPTL v userland v LT (RH9+custom kernel problem)
Date: Thu, 07 Aug 2003 10:49:37 +0200	[thread overview]
Message-ID: <1060246177.5142.1.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20030807013930.A26426@google.com>

[-- Attachment #1: Type: text/plain, Size: 571 bytes --]


> So, finally getting to my question, should I even *expect* a non-NPTL
> kernel to work with the RH9 userland?  

Yes, absolutely. It's a design goal of RHL to work with unpatched
kernel.org kernels.

>
> If not, is there a simple fix
> without going to NPTL, say just rebuilding glibc?  hmm... now that I
> ask it I feel dumb, I do think I would need to rebuild glibc so it
> knows the kernel has LinuxThreads, not NPTL. 

no need. RHL9 ships with BOTH LinuxThreads and NPTL and will switch
dynamically at runtime depending on your kernel capabilities.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-08-07  8:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07  8:39 Frank Cusack
2003-08-07  8:49 ` Arjan van de Ven [this message]
2003-08-07 14:42 ` Jerry Cooperstein
2003-08-07 13:06   ` Mathias Fröhlich
2003-08-08  5:45     ` Frank Cusack
2003-08-08  6:02       ` Valdis.Kletnieks
2003-08-08  6:53       ` Peter Svensson
2003-08-08  7:10         ` Pau Aliagas
2003-08-08 10:32         ` Henning P. Schmiedehausen
2003-08-08 17:37 ` Frank Cusack
2003-08-08 19:05   ` Ulrich Drepper
2003-08-07 13:20 Luke Howard

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=1060246177.5142.1.camel@laptop.fenrus.com \
    --to=arjanv@redhat.com \
    --cc=fcusack@fcusack.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil-list@redhat.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®