The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: rudi.j.blom@gmail.com (Rudi Blom)
Subject: [TUHS] History repeating itself (was: Unix v6 problem with /tmp)
Date: Sun, 31 Jul 2016 11:25:05 +0700	[thread overview]
Message-ID: <CAMYpm87L17V5bOhHbQKKQ=QMbhv8t_x4+D252F=2gCY8GrwLpQ@mail.gmail.com> (raw)

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

> Date: Sat, 30 Jul 2016 15:30:36 +0000
> From: Michael Kjörling <michael at kjorling.se>
> To: tuhs at tuhs.org
> Subject: Re: [TUHS] History repeating itself
> Message-ID: <20160730153036.GI3375 at yeono.kjorling.se>
> Content-Type: text/plain; charset=utf-8
>
> On 30 Jul 2016 10:15 -0400, from cowan at mercury.ccil.org (John Cowan):
>>> Who needs FedEx?
>>
>> Well, latency counts for something too, as does radius: if I want to
>> send bulk data from New York to London (a very normal thing to do),
>> your station wagon isn't going to count for much.
>
> You could, however, get an economy class flight ticket and load up
> your suitcase with either HDDs or SDXCs (I suspect SDXCs would be
> better per amount of data from the perspective of both volume and
> weight, and would take better to handling). Given FedEx's prices,
> _once you have the infrastructure set up_ (which you'll need whether
> you have someone travel with the media, by air or by stationwagon, or
> FedEx it), that _might_ even compare favorably in terms of bytes
> transferred per second per dollar. (Now that's a measurement of
> throughput I don't think I've seen before; B/s/$.) Of course, you'd
> need someone who can babysit the suitcase, which potentially adds to
> the cost, but the stationwagon traditionally hasn't been self-driving
> either, and most of a transatlantic flight isn't active time on part
> of the person travelling with the suitcase so you could go with an
> overnight flight and allow the person to sleep.
>
> If you want to reduce the risk of the bag getting handled roughly or
> lost in handling, reduce the above to carry-on luggage; it will still
> provide a quite respectable throughput.
>
> ... ...
>
> It might not be the absolute cheapest approach, but it seems rather
> hard to beat in terms of throughput per dollar for bulk data transfer,
> especially if you already have someone who would travel anyway and can
> be convinced to take a company-approved suitcase in return for having
> their ticket paid for.
>
> --
> Michael Kjörling • https://michael.kjorling.se • michael at kjorling.se
>                  “People who think they know everything really annoy
>                  those of us who know we don’t.” (Bjarne Stroustrup)
>

To setup the 'infrastructure might be the tricky part. Many years ago
I flew from Montreal to Amsterdam and had two stacks of 5-1/4"
diskettes with me. No papers, confiscated in Amsterdam.

Cheers,
Rudi


             reply	other threads:[~2016-07-31  4:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-31  4:25 Rudi Blom [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2016-08-03 11:53 Norman Wilson
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: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
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

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='CAMYpm87L17V5bOhHbQKKQ=QMbhv8t_x4+D252F=2gCY8GrwLpQ@mail.gmail.com' \
    --to=rudi.j.blom@gmail.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).