All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Boreham" <david_list@boreham.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CBQ broken in RedHat 8.0?
Date: Sun, 27 Oct 2002 17:23:52 +0000	[thread overview]
Message-ID: <marc-lartc-103573940928486@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103567646931154@msgid-missing>

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

I find that inserting a stock kernel into a machine originally
running a distro (RH, Mandrake etc) is often a painful and
unrewarding experience.

My personal preference these days is to get the source RPM
for the kernel for the target distro. Then modify the spec file
to patch the kernel the way I want it (e.g. Mandrake 8.2 you
must _remove_ the HTB2 patches, and add the HTB3 patches
and the IMQ patches). Build the RPM and you now have a
way to upgrade the kernel and modules on any machine running
that distro, guaranteed to work with the user space code, since
the kernel is identical to what was there before, modulo the desired
patches.


_______________________________________________
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:23 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
2002-10-27 17:23 ` David Boreham [this message]
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-103573940928486@msgid-missing \
    --to=david_list@boreham.org \
    --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.