From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB3 question
Date: Thu, 16 May 2002 10:26:56 +0000 [thread overview]
Message-ID: <marc-lartc-102154484608006@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102139485323956@msgid-missing>
It will not. Header files changed a bit (versioning added).
I have to do some cleanups to comply with objections of
kernel maintainers ..
devik
On 14 May 2002, Rens Houben wrote:
> Will tc patched for htb3 work correctly with a HTB2 kernel? (Work, not
> compile -- I already compiled it with the correct header files). It
> appears to take its commands properly but without the ability to take
> any of our gateways offline I can't check for sure.
>
> If it can, I can file a wishlist bug in b.d.o on iproute to get
> htb3-enabled tc into woody.
>
> Thanks in advance,
> Shad.
>
> --
> Rens Houben
> Systemec Internet Services
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-05-16 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 16:47 [LARTC] HTB3 question Rens Houben
2002-05-16 10:26 ` Martin Devera [this message]
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-102154484608006@msgid-missing \
--to=devik@cdi.cz \
--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