public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Beau E. Cox" <beau@beaucox.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: marcelo.tosatti@cyclades.com, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.4.23-pre7,pre8,pre9 hang on starting squid
Date: Sat, 8 Nov 2003 00:31:28 -1000	[thread overview]
Message-ID: <200311080031.28457.beau@beaucox.com> (raw)
In-Reply-To: <20031107155147.05671d94.rddunlap@osdl.org>

On Friday 07 November 2003 01:51 pm, Randy.Dunlap wrote:
> On Fri, 7 Nov 2003 06:00:01 -1000 "Beau E. Cox" <beau@beaucox.com> wrote:
> | On Thursday 06 November 2003 04:06 am, Marcelo Tosatti wrote:
> | > On Mon, 3 Nov 2003, Beau E. Cox wrote:
> | > > [1.] summary:
> | > >
> | > > 2.4.23-pre7,pre8,pre9 hang depending on when 'squid' is started.
> | > >
> | > > [snipped]
> | >
> | > Strange.
> | >
> | > Can you find out in which -pre the problem starts?
> |
> | Hi - I want to track down the 'pre' where my problem started (I would
> | need 2.4.23-pre1 thru pre6), but I can't find them anywhere on the
> | kernel archaive site (mirros too). Where can I get these pre patches?
>
> They are in this directory:
>   http://www.kernel.org/pub/linux/kernel/v2.4/testing/
>
> --
> ~Randy
> MOTD:  Always include version info.

Thanks Randy -

I don't know how I missed them...
I'll start from pre1 and test. This will take several days to a week.

Aloha => Beau;


      reply	other threads:[~2003-11-08 10:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03 17:08 PROBLEM: 2.4.23-pre7,pre8,pre9 hang on starting squid Beau E. Cox
2003-11-06 14:06 ` Marcelo Tosatti
2003-11-06 17:49   ` Beau E. Cox
2003-11-07 16:00   ` Beau E. Cox
2003-11-07 23:51     ` Randy.Dunlap
2003-11-08 10:31       ` Beau E. Cox [this message]

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=200311080031.28457.beau@beaucox.com \
    --to=beau@beaucox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=rddunlap@osdl.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