From: DervishD <lartc@dervishd.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] About "b" meaning "byte" and bit
Date: Fri, 07 Sep 2007 07:34:47 +0000 [thread overview]
Message-ID: <20070907073447.GC17688@DervishD> (raw)
In-Reply-To: <20070831162624.GA6133@DervishD>
Hi Andy :)
* Andy Furniss <lists@andyfurniss.entadsl.com> dixit:
> DervishD wrote:
> > Yes, I already knew that, what I was asking is why SI units are not
> >used and "shortcuts" are used instead: see my original message, I was
> >not sure if kilobit was being used correctly (meaning 1000 bits) or if
> >it was being used mistakenly for kibibit (1024 bits), and on top of
> >that, why "b" was being used as byte when the SI prefix for byte is "B".
>
> It got changed so kbit means 1000 when S.Hemminger took over maintenance
> IIRC.
Ok, thanks :))
> > I mean, tc doesn't seem to follow any standard except maybe in
> >kilobit (which should be then used as kb, not kbit).
>
> I think changing kb and kbit would break too many existing scripts.
That's the problem with scripts that insist blindly on parsing
command output, specially with commands whose output may (and should)
change regularly when improvements are made. I supposed this was the
reason. Does "tc" have another interface, preferably in "sys" or "proc"
or the only way of getting the information is asking the kernel directly
(through "tc", for example).
Thanks a lot for your answer :)
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
We are waiting for 13 Feb 2009 23:31:30 +0000 ...
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-09-07 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 16:26 [LARTC] About "b" meaning "byte" and bit DervishD
2007-09-03 4:33 ` Indunil Jayasooriya
2007-09-03 9:17 ` DervishD
2007-09-06 21:14 ` Andy Furniss
2007-09-07 7:34 ` DervishD [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=20070907073447.GC17688@DervishD \
--to=lartc@dervishd.net \
--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.