From: Jose Luis Domingo Lopez <lartc@24x7linux.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: [ANNOUCE] iproute2 update
Date: Wed, 09 Jun 2004 17:16:26 +0000 [thread overview]
Message-ID: <20040609171626.GA3541@localhost> (raw)
In-Reply-To: <Pine.LNX.4.44.0406081826450.20838-100000@bawx.pilosoft.com>
On Tuesday, 08 June 2004, at 18:42:46 -0400,
alex@pilosoft.com wrote:
> That does makes sense for entering data, however, for display of results,
> they need to be in one format.
>
That of units, their use and meaning is a common topic at some places,
including linux-kernel. There seems to be several international
standards with respect to units, both base-2 (2^n) an base-10 (10^n).
Maybe you have around units(7), a man page that gives a bit of
information on the subject. In my opinion, data should always be shown
correct, that is, 1048576 will be eiher 1024 kibi (1024 Ki), or
1048.576 kilo (1048.576 k), but not anything else.
The possible change in suffixes could break existing scripts in a
(hopefully) minor way, but changing rate specification in "tc" should be
thought for longer, the breakage here can be important.
Just my two euro cents ;-)
--
Jose Luis Domingo Lopez
Linux Registered User #189436 Debian Linux Sid (Linux 2.6.7-rc1)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-06-09 17:16 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 [this message]
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
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=20040609171626.GA3541@localhost \
--to=lartc@24x7linux.com \
--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.