From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stef Coene Date: Thu, 10 Jun 2004 19:45:37 +0000 Subject: Re: [LARTC] Re: [ANNOUCE] iproute2 update Message-Id: <200406102145.37116.stef.coene@docum.org> List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: lartc@vger.kernel.org On Wednesday 09 June 2004 22:37, Stephen Hemminger wrote: > On Wed, 9 Jun 2004 21:21:52 +0200 > > Stef Coene 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 =3D 1024 and k =3D 1000) or something l= ike > > > 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= =20 version? Depending on the name how the binary is executed, the ritgh versi= on=20 is choosen. So you have tcnew and a link to it called tc. If tc is=20 executed, the old version is used, if tcnew is executed, the new version is= =20 used. I know it sounds messy ... Stef --=20 stef.coene@docum.org =A0"Using Linux as bandwidth manager" =A0 =A0 =A0http://www.docum.org/ _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/