From: "rob pike, esq." <rob@mightycheese.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] seek() in fossil?
Date: Sun, 26 Jan 2003 11:18:55 -0800 [thread overview]
Message-ID: <56bdfd682af03e2cf62bd4473efc7599@mightycheese.com> (raw)
In-Reply-To: <3d1b4126560a1275cfc5b04714fafe12@plan9.bell-labs.com>
This reminds me of the IPv6 fools, who seemed to think that
if 2^48 wasn't quite enough, they should go for 2^64 but just
to be sure, double it to 2^128.
Do you know how big 2^64 is? It's not twice as big as a gigabyte.
Let's say we had a gigabit ethernet and we wanted to write a 2^64
byte file. It would take more than a thousand years.
-rob
next prev parent reply other threads:[~2003-01-26 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-26 17:43 andrey mirtchovski
2003-01-26 19:01 ` Russ Cox
2003-01-26 19:10 ` David Presotto
2003-01-26 20:03 ` Russ Cox
2003-01-26 19:18 ` rob pike, esq. [this message]
2003-01-26 21:25 ` Mike Haertel
2003-01-27 10:29 ` Douglas A. Gwyn
2003-01-27 15:18 ` Russ Cox
2003-01-27 15:21 ` Russ Cox
2003-01-27 15:18 ` Russ Cox
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=56bdfd682af03e2cf62bd4473efc7599@mightycheese.com \
--to=rob@mightycheese.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).