From: jb@schatz.com
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems patching kernel 2.4.19-r9
Date: Sun, 20 Oct 2002 14:25:42 +0000 [thread overview]
Message-ID: <marc-lartc-103512400108603@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103508024922082@msgid-missing>
>So download the iproute2 source and patch it :)
:( Background explanation: The HTB on-line manual says
simply: "Also you will have to use patched tc tool." To
my newbie eye, this is vague and incomplete, hence my
query.
Answer: In fact, I have iproute-20010824-r1 in the
sources. No matter, the output is the same:
Upon trying again to "dry-run" patch from within
/usr/src/linux and responding either "iproute2" or
"iproute" to the returned query "File to patch:", both
tests return "No such file or directory".
Please allow me one further question: As I do not wish
to design complicated traffic-shaping rules for now,
could I simply use the earlier version of HTB (HTB2 ?)
which is already in the 2.4.19-9 kernel I have
installed? I understand that the commands may be
different. If using this earlier version is feasible,
please point me to the command reference.
I have learned much in a very short time from reading
the recent postings of Stef Coene and others on the
LARTC. Thank you to you and everyone participating on
the list.
J. B. Schatz
_______________________________________________
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 14:25 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
2002-10-20 14:25 ` jb [this message]
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-103512400108603@msgid-missing \
--to=jb@schatz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox