All of lore.kernel.org
 help / color / mirror / Atom feed
From: LuisMi <luismi@adpsoft.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Compiling HTB2 on RH7.2
Date: Wed, 01 May 2002 00:59:45 +0000	[thread overview]
Message-ID: <marc-lartc-102021483304563@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102019515221083@msgid-missing>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Maybe it is the best way, always try to avoid the redhat kernel sources if 
you want to apply any patch.

- -- 
+-------------------------------------------------------------------+
| Luis Miguel Cruz.                                                 |
|                                                                   |
|  [ADPSOFT] http://www.adpsoft.com                                 |
|  "Connecting your business"                                       |
|                                                                   |
|  irc.irc-hispano.org -> #redhat                                   |
|  http://www.flcnet.es/tbe/luismi                                  |
|  Canal IRC para usuarios RedHat Linux                             |
|								    |
|  Public Key: http://www.flcnet.es/tbe/luismi/nadie/luismi_adp.asc |
+-------------------------------------------------------------------+

On Tue, 30 Apr 2002, Nils Lichtenfeld wrote:

> Hello!
> 
> Thanks for the quick answer.
> 
> > I usually patch my kernel into RH 7.2 with some differents patches.
> > From my experience: never user the kernel sources from redhat.
> > It is too complicated, or impossible, to patch that sources in the
> > most cases.
> >
> > I patch HTB (not HTB2) over a 2.4.17 without problems, and, of
> > course, I use RH 7.2 :-)
> 
> I don not want to change the kernel, even if it is the better choice.
> Would it be possible to get 2.4.7 from kernel.org, compile the
> HTB-module and use that one with the current kernel from RH7.2?
> 
> Greetings, Nils
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjzPPgMACgkQvQHLTzrFJldKXgCdEyfceHsE7V4xieIeC2+s7AER
mlgAoItMhNKB/urYS3Uig6f5zq7Yaibt
=buiU
-----END PGP SIGNATURE-----

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-05-01  0:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-30 19:32 [LARTC] Compiling HTB2 on RH7.2 Nils Lichtenfeld
2002-04-30 19:59 ` LuisMi
2002-04-30 20:13 ` Nils Lichtenfeld
2002-05-01  0:59 ` LuisMi [this message]
2002-05-01  1:11 ` Patrick McHardy
2002-05-01 10:59 ` Nils Lichtenfeld
2002-05-01 11:24 ` Nils Lichtenfeld
2002-05-01 12:31 ` LuisMi

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-102021483304563@msgid-missing \
    --to=luismi@adpsoft.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.