From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems patching kernel 2.4.19-r9
Date: Sun, 20 Oct 2002 08:20:31 +0000 [thread overview]
Message-ID: <marc-lartc-103510208930177@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103508024922082@msgid-missing>
On Sunday 20 October 2002 04:16, jb@schatz.com wrote:
> A question about the tc binary and diff file that are
> included in htb3.6-020525.tgz. I can't seem to patch tc
> in the source tree, and that has made me hesitate to
> alternatively substitute the native /usr/sbin/tc for
> the binary supplied with the patch materials. I'm
> running kernel 2.4.19-r9, and when I run
>
> xingu:/usr/src/linux #patch -p1 --dry-run <
> ../htb3.6.tc.diff
>
> the result is:
>
> patching file tc/q_htb.c
> can't find file to patch at input line 312
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> ------------------
>
> |--- iproute2/tc/Makefile Tue Jul 6 1999
> |+++ iproute2new/tc/Makefile Thu May 9 2002
>
> ------------------
> File to patch:
>
> Does anyone know what's going on here and how I can
> proceed safely?
You want to patch iproute2. So download the iproute2 source and patch it :)
You are trying to patch the kernel source.
iproute2 source :
ftp://ftp.inr.ac.ru/ip-routing/
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-10-20 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-20 2:16 [LARTC] Problems patching kernel 2.4.19-r9 jb
2002-10-20 8:20 ` Stef Coene [this message]
2002-10-20 14:25 ` jb
2002-10-20 14:59 ` Werner Almesberger
2002-10-20 20:10 ` Don Gould
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-103510208930177@msgid-missing \
--to=stef.coene@docum.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox