All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Davidson <r.davidson@mindspring.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CBQ broken in RedHat 8.0?
Date: Sun, 27 Oct 2002 17:08:46 +0000	[thread overview]
Message-ID: <marc-lartc-103573839527780@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103567646931154@msgid-missing>

On Sunday 27 October 2002 04:09, Stef Coene wrote:

>Why upgrading your SUSE?  You can also download 2.4.19 from ftp.kernel.org
> and patch with the lates htb patch ??

What better way to support the distro I know how to use and avoid hairy 
compiling problems? SuSE has 7.3 kernel rpms available for 2.4.16, but not 
2.4.17, so I decided to go ahead. It is just a test server in any case - no 
worrying about reconfiguring.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-10-27 17:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-26 23:53 [LARTC] CBQ broken in RedHat 8.0? Neil Aggarwal
2002-10-27  3:10 ` Robert Davidson
2002-10-27 10:09 ` Stef Coene
2002-10-27 17:08 ` Robert Davidson [this message]
2002-10-27 17:23 ` David Boreham
2002-10-28 11:40 ` Aigars Mahinovs

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=marc-lartc-103573839527780@msgid-missing \
    --to=r.davidson@mindspring.com \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.