The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] History repeating itself (was: Unix v6 problem with /tmp)
Date: Sat, 30 Jul 2016 17:56:41 +1000	[thread overview]
Message-ID: <20160730075641.GT78278@eureka.lemis.com> (raw)
In-Reply-To: <20160728135739.GA14303@mercury.ccil.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]

On Thursday, 28 July 2016 at  9:57:40 -0400, John Cowan wrote:
> Michael Kjörling scripsit:
>>
>> Now all that's really missing is that stationwagon loaded with tapes
>
> Now replaced by the Fedexed hard drive.  Xkcd estimates that if they did
> nothing else, Fedex would be able to transmit 14 petabits per second.
> Companies dealing in big data often use this internally, and IIRC you
> can donate content to the Internet Archive by sending them a disk.

Hard disk drives are yesterday's criterion.  Now it's microSDXC cards.
Physical volume 0.165 ml, up to 200 GB.  I've seen claims that my
station wagon has a cargo volume of 2,752 l, though that seems on the
high side.  That corresponds to about 16,670,000 cards or 3.3 EB.
Take that on a 20 minute drive, and you end up with a link bandwidth
of about 22 Pb/s.

Who needs FedEx?  Of course, the link bandwidth is no longer the
bottleneck.

Greg
--
Sent from my desktop computer.
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160730/4ad628f7/attachment.sig>


  reply	other threads:[~2016-07-30  7:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27 20:28 [TUHS] Unix v6 problem with /tmp Mark Longridge
2016-07-27 20:31 ` William Pechter
2016-07-27 20:57   ` Clem Cole
2016-07-27 21:01     ` Clem Cole
2016-07-27 21:10     ` William Pechter
2016-07-28  0:49       ` Clem cole
2016-07-28  1:03         ` William Pechter
2016-07-28 11:23           ` [TUHS] History repeating itself (was: Unix v6 problem with /tmp) Michael Kjörling
2016-07-28 12:18             ` Tony Finch
2016-07-28 13:57             ` John Cowan
2016-07-30  7:56               ` Greg 'groggy' Lehey [this message]
2016-07-30 11:41                 ` William Cheswick
2016-07-30 23:28                   ` Greg 'groggy' Lehey
2016-07-30 23:50                     ` scj
2016-08-01 11:36                   ` Tony Finch
2016-07-30 14:15                 ` John Cowan
2016-07-30 15:30                   ` [TUHS] History repeating itself Michael Kjörling
2016-07-28  1:03       ` [TUHS] Unix v6 problem with /tmp Clem cole
2016-07-28 23:16     ` [TUHS] environments/universes (was: Unix v6 problem with /tmp) Sven Mascheck
2016-07-29  3:05       ` arnold
2016-07-29 14:14         ` Clem Cole
2016-07-29 13:55       ` Clem Cole
2016-07-31  4:25 [TUHS] History repeating itself " Rudi Blom
2016-08-01  1:08 ` John Cowan
2016-08-01  7:14   ` Rudi Blom
2016-08-01 17:11     ` scj
2016-08-01 18:32       ` Clem Cole
2016-08-02 22:38       ` Dave Horsfall
2016-08-03 11:53 Norman Wilson

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=20160730075641.GT78278@eureka.lemis.com \
    --to=grog@lemis.com \
    /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).