From: Lee Revell <rlrevell@joe-job.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Alon Bar-Lev <alon.barlev@gmail.com>,
David Wagner <daw@cs.berkeley.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Question] LinuxThreads, setuid - Is there user mode hook?
Date: Fri, 23 Dec 2005 15:36:37 -0500 [thread overview]
Message-ID: <1135370197.22177.40.camel@mindpipe> (raw)
In-Reply-To: <20051223202105.GA32321@nevyn.them.org>
On Fri, 2005-12-23 at 15:21 -0500, Daniel Jacobowitz wrote:
> On Fri, Dec 23, 2005 at 02:08:58PM -0500, Lee Revell wrote:
> > Why on earth would you use LinuxThreads rather than NPTL? LinuxThreads
> > is obsolete and was never remotely POSIX compliant.
>
> You have the strangest ideas of obsolete. NPTL has only been usable
> for two years. Software lifecycles can be a lot longer than that.
>
I'm not telling you to stop supporting legacy apps, I'm just saying it's
insane to start a project now and target LinuxThreads rather than NPTL
which is what it sounded like the OP was doing.
Lee
next prev parent reply other threads:[~2005-12-23 20:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200512222312.jBMNCj96018554@taverner.CS.Berkeley.EDU>
2005-12-23 9:51 ` [Question] LinuxThreads, setuid - Is there user mode hook? Alon Bar-Lev
2005-12-23 19:08 ` Lee Revell
2005-12-23 20:21 ` Daniel Jacobowitz
2005-12-23 20:36 ` Lee Revell [this message]
2005-12-23 20:33 ` Daniel Jacobowitz
2005-12-24 16:16 ` Alon Bar-Lev
2005-12-25 1:31 ` Luke-Jr
2005-12-25 8:05 ` Alon Bar-Lev
[not found] <5mRSA-6ss-15@gated-at.bofh.it>
[not found] ` <5n1S5-9P-21@gated-at.bofh.it>
[not found] ` <5n1S5-9P-19@gated-at.bofh.it>
[not found] ` <5nt1F-5aZ-1@gated-at.bofh.it>
2005-12-27 2:33 ` Robert Hancock
[not found] <200512231927.jBNJR2uG019083@taverner.CS.Berkeley.EDU>
2005-12-24 16:18 ` Alon Bar-Lev
2005-12-22 15:47 Alon Bar-Lev
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=1135370197.22177.40.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alon.barlev@gmail.com \
--cc=dan@debian.org \
--cc=daw@cs.berkeley.edu \
--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