From: devik <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Announce: Backport QoS from 2.4 to 2.2
Date: Tue, 15 Oct 2002 11:29:45 +0000 [thread overview]
Message-ID: <marc-lartc-103468197032490@msgid-missing> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1254", Size: 2353 bytes --]
Download latest HTB3 TGZ from luxik.cdi.cz/~devik/qos/htb/
and you can use binary from there. Alexey prepared oficial
iproute2 package but he is busy until November ..
devik
On Tue, 15 Oct 2002 lihpc@Legend.com wrote:
>
> Hi,
> HTB3 backport from 2.4 to 2.2
> we have to use new tc tool for htb3 of 2.2
>
> Where can i get the new iproute2 for 2.2 ?
>
>
> thanks for your help
>
> regards,
>
> haipe
>
> -------------------------------------------
>
>
>
> Julian Anastasov
> <ja@ssi.bg> ÊÕ¼þÈË£º lartc <lartc@mailman.ds9a.nl>
> ·¢¼þÈË£º ³ËÍ£º diffserv-general@lists.sourceforge.net,
> lartc-admin@mailm jamal <hadi@cyberus.ca>
> an.ds9a.nl Ö÷Ì⣺ [LARTC] Announce: Backport QoS from 2.4 to
> 2.2
>
> 2002-08-19 02:58
>
>
>
>
>
>
>
> Hello,
>
> I'm happy to announce a QoS Backport from 2.4 to 2.2.
> This is unofficial DiffServ v9 release (a.k.a DS-9).
>
> This beta release includes some bugfixes after the last 2.2
> release, known as DS-8, many files copied from 2.4.19, some definitions
> and functions useful for keeping the interface for schedulers and
> classifiers similar to the 2.4 one.
>
> I'm planning to apply all 2.4/2.5 QoS fixes to this DS-9
> tree, so the result should be fully functional net schedulers
> for 2.2. As there are still some 2.2 specific parts, any kind of
> reports are useful (even the good ones :)).
>
> Any bugfixes and comments can be posted directly to me or
> to the LARTC and/or DiffServ mailing lists.
>
> Have fun!
>
> DS-9 - QoS Backport from 2.4.19 to 2.2.21:
> http://www.ssi.bg/~ja/ds9/
>
> Changes between DS-8 and DS-9:
> http://www.ssi.bg/~ja/ds9/Changelog.ds9
>
> Regards
>
> --
> Julian Anastasov <ja@ssi.bg>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
> ,\x04S
f¢–)à–+-ü°\x11L)šŠYšÛ=jya¶Ú~ÿùšŠYšÛ=jy\x7f™¨¥™©ÿ–+-ŠwèþV«µÁÎY3¾†Ûiûÿåj»\¢¸?
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-10-15 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 11:29 devik [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-18 15:58 [LARTC] Announce: Backport QoS from 2.4 to 2.2 Julian Anastasov
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-103468197032490@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 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.