The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: michael@kjorling.se (Michael Kjörling)
Subject: [TUHS] History repeating itself (was: Unix v6 problem with /tmp)
Date: Thu, 28 Jul 2016 11:23:30 +0000	[thread overview]
Message-ID: <20160728112330.GP3375@yeono.kjorling.se> (raw)
In-Reply-To: <579959F6.3050803@gmail.com>

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

On 27 Jul 2016 21:03 -0400, from pechter at gmail.com (William Pechter):
> When I saw the Windows Ready Boost and Intel Turbo memory I really
> flashed (ugh pun not intended) to the day I installed the early
> ML11... Nothing new in the OS business that wasn't done in the old
> days.  Unfortunately, there's very little love for history in the industry.

I remember when this newfangled thing called "the cloud" started
becoming _the_ thing that was being talked about recently, and I kept
asking myself how on Earth that's anything new. Large timeshared
systems fell out of favor basically when local systems with adequate
storage and processing capabilities became affordable, and now large
timeshared systems - under a different name, mind you, because history
does not repeat itself, it rhymes - have become favorable again
(despite the fact that essentially _any_ desktop system today has
processing capabilities not entirely dissimilar to a supercomputer of
twenty years ago). But this time, very often it's _actually_ _someone
else's computer_; it's not just sitting in some other department
within the company. I'll admit, it's awfully convenient at times, but
it's hardly something _new_.

Now all that's really missing is that stationwagon loaded with tapes
for regular large-scale data transfer, and with some of the
discussions going on in the last few years I wouldn't be the least bit
surprised if sneakernet has seen a rebound at least in some places.

-- 
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)


  reply	other threads:[~2016-07-28 11:23 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           ` Michael Kjörling [this message]
2016-07-28 12:18             ` [TUHS] History repeating itself (was: Unix v6 problem with /tmp) 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
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=20160728112330.GP3375@yeono.kjorling.se \
    --to=michael@kjorling.se \
    /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).