mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Syed Ahemed <kingkhan@gmail.com>,
	linux-kernel@vger.kernel.org, msnyder@redhat.com,
	jjohnstn@redhat.com
Subject: Re: NPTL patch for linux 2.4.28
Date: Thu, 15 Mar 2007 14:40:02 +0100	[thread overview]
Message-ID: <20070315134002.GB16199@1wt.eu> (raw)
In-Reply-To: <1173945186.25356.23.camel@twins>

On Thu, Mar 15, 2007 at 08:53:06AM +0100, Peter Zijlstra wrote:
> On Thu, 2007-03-15 at 03:14 +0530, Syed Ahemed wrote:
> 
> > Getting RHEL's source ( http://lkml.org/lkml/2005/3/21/380 ) was an
> > idea i thought about but then a download of the RHEL source from the
> > following location was denied .
> > http://download.fedora.redhat.com/pub/fedora/linux/core/1/SRPMS/  and
> > the rpmfind site.
> > (Guess need to be a paid subscriber for that right ?)
> 
> Strangely enough you try to download Fedora Core SRPMs whilst you speak
> of RHEL. Try this one:
> 
> ftp://ftp.redhat.com/pub/redhat/linux/enterprise/3/en/os/i386/SRPMS/kernel-2.4.21-4.EL.src.rpm
> 
> Also, CentOS would have similar sources. Google could have informed you
> on that.
> 
> > I still wonder why there aren't any NPTL patches available in the
> > non-redhat sites for kernels like 2.4.21 or more .
> 
> Because most people, especially the ones on this mailing list have moved
> on to 2.6 quite some time ago. May I suggest you do the same?

... or they stick to 2.4 for specific uses and do not need NPTL at all, which
came late in the development cycle.

Regards,
Willy


  reply	other threads:[~2007-03-15 13:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14  0:19 Syed Ahemed
2007-03-14  5:55 ` Willy Tarreau
2007-03-14 21:44   ` Syed Ahemed
2007-03-15  7:53     ` Peter Zijlstra
2007-03-15 13:40       ` Willy Tarreau [this message]
2007-03-15 17:28         ` Syed Ahemed
2007-03-15 21:31           ` Syed Ahemed

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=20070315134002.GB16199@1wt.eu \
    --to=w@1wt.eu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=jjohnstn@redhat.com \
    --cc=kingkhan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msnyder@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®