From: "Martin Teufel" <martin.teufel@tuwien.ac.at>
To: lartc@vger.kernel.org
Subject: AW: [LARTC] Unknown qdisc "htb", hence option "default" is unparsable
Date: Thu, 26 Jun 2003 06:39:47 +0000 [thread overview]
Message-ID: <marc-lartc-105660966715475@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105660880414915@msgid-missing>
you should use the patch
http://luxik.cdi.cz/~devik/qos/htb/v3/htb3.6-020525.tgz from
http://luxik.cdi.cz/~devik/qos/htb/
regards martin
-----Ursprüngliche Nachricht-----
Von: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl] Im
Auftrag von rio@martin.mu
Gesendet: Donnerstag, 26. Juni 2003 08:25
An: lartc@mailman.ds9a.nl
Betreff: [LARTC] Unknown qdisc "htb", hence option "default" is unparsable
Dear all,
I tried to re-compile iproute2 from
ftp://ftp.inr.ac.ru/ip-routing/iproute2-2.4.7-now-ss010824.tar.gz
But still htb is unknown ..
Regards,
Rio Martin.
--------------------------------------------------------------------
mail2web - Check your email from the web at http://mail2web.com/ .
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-06-26 6:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 6:25 [LARTC] Unknown qdisc "htb", hence option "default" is unparsable rio
2003-06-26 6:39 ` Martin Teufel [this message]
2003-06-26 6:48 ` [LARTC] Unknown qdisc "htb", hence option "default" is K S Sreeram
2004-10-06 15:06 ` [LARTC] Unknown qdisc "htb", hence option "default" is unparsable Marcelo Araujo
2004-10-07 2:40 ` gypsy
2004-10-18 12:13 ` Marcelo Araujo
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-105660966715475@msgid-missing \
--to=martin.teufel@tuwien.ac.at \
--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