From: "Mike Frysinger" <vapier.adi@gmail.com>
To: Rick Brown <rick.brown.3@gmail.com>
Cc: kernelnewbies <kernelnewbies@nl.linux.org>, linux-newbie@vger.kernel.org
Subject: Re: Threading in linux
Date: Tue, 24 Apr 2007 06:51:47 -0400 [thread overview]
Message-ID: <8bd0f97a0704240351o6015dc5fp95b18cb288267887@mail.gmail.com> (raw)
In-Reply-To: <7783925d0704240336i49e918dcm4d38e9bbc0310a39@mail.gmail.com>
On 4/24/07, Rick Brown <rick.brown.3@gmail.com> wrote:
> > > NPTL on 2.4?
> >
> > this can be done only if you backport the features from 2.6 that were
> > added in order to make NPTL possible ... redhat has done this, but
> > really it's just a waste of time ... 2.4 is dead :P
>
> Could you hint upon the kernel features required for NPTL? May be a link?
i couldnt really guess. your only safe bet is to go get a redhat
kernel. i think it's a waste either way, but that's me.
> > > pthreads on 2.6?
> >
> > i really have no idea what you mean by this ... "pthreads" is short
> > for "POSIX threads" and there's no such thing as "pthreads" with
> > respect to a specific code base. NPTL is one implementation of the
> > POSIX threads specification while LinuxThreads is another.
>
> Sorry ... I meant LinuxThreads.
linuxthreads works fine on 2.6 ... linux has forward binary
compatibility, thus things that work in 2.4 (like linuxthreads)
continue to work in 2.6
-mike
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2007-04-24 10:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 6:38 Threading in linux Rick Brown
2007-04-24 7:03 ` pradeep singh
2007-04-24 7:17 ` Amol Lad
2007-04-24 8:29 ` Rick Brown
2007-04-24 9:54 ` Erik Mouw
2007-04-24 10:08 ` Mike Frysinger
2007-04-24 10:36 ` Rick Brown
2007-04-24 10:51 ` Mike Frysinger [this message]
2007-04-25 0:48 ` John Aspinall
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=8bd0f97a0704240351o6015dc5fp95b18cb288267887@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-newbie@vger.kernel.org \
--cc=rick.brown.3@gmail.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