From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: [ANNOUCE] iproute2 update
Date: Thu, 10 Jun 2004 19:45:37 +0000 [thread overview]
Message-ID: <200406102145.37116.stef.coene@docum.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0406081826450.20838-100000@bawx.pilosoft.com>
On Wednesday 09 June 2004 22:37, Stephen Hemminger wrote:
> On Wed, 9 Jun 2004 21:21:52 +0200
>
> Stef Coene <stef.coene@docum.org> wrote:
> > On Wednesday 09 June 2004 01:31, Stephen Hemminger wrote:
> > > But should we break existing scripts?? One possibility would be to
> > > make things case dependant (K = 1024 and k = 1000) or something like
> > > that.
> >
> > I vote for yes.
> > What we can do, is use an other name so the difference is clear that it's
> > not tc, but the new tc. Mhh, why don't call this newtc? Or tcnew? Or
> > tc2? So people can use tc and not change the scripts, or use tcnew and
> > change all scripts accordingly.
>
> I don't want to fork or make the iproute2 utilities explicitly different
> from earlier versions. Do we really want to repeat the mess of proc tools.
>
> But, in this case the change is actually small and contained, I haven't
> heard one person who would be upset by switching.
>
> So the next snapshot will use 1000's for rates and 1024 for sizes as per
> the standard usage.
Isn't there a way to create 1 binary that can work like the old and the new
version? Depending on the name how the binary is executed, the ritgh version
is choosen. So you have tcnew and a link to it called tc. If tc is
executed, the old version is used, if tcnew is executed, the new version is
used.
I know it sounds messy ...
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-06-10 19:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 22:32 [LARTC] Re: [ANNOUCE] iproute2 update alex
2004-06-08 22:42 ` alex
2004-06-08 23:31 ` Stephen Hemminger
2004-06-09 0:31 ` Andreas Klauer
2004-06-09 5:00 ` Michael Renzmann
2004-06-09 16:38 ` Federico Figueroa C.
2004-06-09 17:16 ` Jose Luis Domingo Lopez
2004-06-09 17:48 ` ThE LinuX_KiD
2004-06-09 19:21 ` Stef Coene
2004-06-09 19:56 ` pf.vd.vlugt
2004-06-09 20:37 ` Stephen Hemminger
2004-06-09 23:09 ` Ed Wildgoose
2004-06-10 19:45 ` Stef Coene [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=200406102145.37116.stef.coene@docum.org \
--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