The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ggm@algebras.org (George Michaelson)
Subject: [TUHS] Why BSD didn't catch on more, and Linux did
Date: Wed, 7 Feb 2018 13:47:33 +1000	[thread overview]
Message-ID: <CAKr6gn19mY2SeSOui3PWx3SNXAvVFOET5EZX-TbgysOegC+2+g@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1802071049010.1684@sirius.opentrend.net>

hah! you ran a damn sight further with your acquired knowledge than I
did I hasten to add. I now lean on the knowledge of my betters almost
all the time, to do my job. I'm suffering almost 100% continuous
imposter syndrome.

I remember we were a bit heavy handed with downloads because of
paranoia bout funding the data in the AARNet model. Most other
international academic nets wound up paying for bandwidth as a capex
with no cost recovery because physics and bombs wanted it to exist.

(physicists who feel offended, consider yourself astronomers, and then
stars are just giant fusion bombs)

Australia decided to drive to an economic rationalist model where the
money raised paid the cost to increase the bandwidth when the core net
was on 65% utilisation all the time, which usefully was the observed
rate when TCP clagged up with the window/backoff/RTT of the day. So it
was a self-perpetuating perpetual motion mache for making money to buy
bandwidth. You (in a very perverse sense) were driving it north to 65%
quicker than the UQ people wanted to pay for it, hence our heavy
handed back pressure not to do that (tm).

We did the mirrors, because squid caches hadn't been invented. If we'd
had caches we might not have done the mirrors. By the time squid
caches existed we had the mirrors so we kinda had both. Mirrors made
life better.

I don't think it was this time, but one of the times I was heavy
handed with people like you, who used the damn thing, I got carpeted
by the computer center director for "not being nice to the users"
which was hugely embarrassing and he was kind enough to let me off
with a warning instead of a career limiting boot out the door.

Now, we just let the floodgates open. I think I throw away .ISO files
on my macbook drive, because its easier to refresh off the distro
core, or I'm running Docker images and they load way more crap anyway.


  reply	other threads:[~2018-02-07  3:47 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06 22:13 Dan Stromberg
2018-02-06 22:38 ` Clem Cole
2018-02-06 22:44 ` Warner Losh
2018-02-06 22:59   ` Pete Wright
2018-02-06 22:59 ` Derek Fawcus
2018-02-07  1:14   ` Dave Horsfall
2018-02-06 23:02 ` Theodore Ts'o
2018-02-07  0:22   ` Andy Kosela
2018-02-07  1:02     ` Robert Brockway
2018-02-07  3:47       ` George Michaelson [this message]
2018-02-07  1:29   ` Clem Cole
2018-02-07 15:13     ` Theodore Ts'o
2018-02-07 16:59       ` Jon Forrest
2018-02-07 17:27       ` Clem Cole
2018-02-07 19:21         ` Dan Cross
2018-02-07 21:24           ` Clem Cole
2018-02-07 19:31         ` Nemo
2018-02-07 19:49         ` Theodore Ts'o
2018-02-07 19:53           ` Dan Cross
2018-02-07 20:26             ` Theodore Ts'o
2018-02-07 21:06               ` Clem Cole
2018-02-07 21:31               ` Clem Cole
2018-02-07 17:52       ` Tom Ivar Helbekkmo
2018-02-07  8:04   ` Tom Ivar Helbekkmo
2018-02-07  8:51   ` Arrigo Triulzi
2018-02-07  8:27 ` Wesley Parish
2018-02-07  8:39   ` emanuel stiebler
2018-02-07 10:44     ` Arrigo Triulzi
2018-02-07 13:14   ` Chet Ramey
2018-02-07 14:42   ` Nemo
2018-02-09  2:53     ` Wesley Parish
2018-02-11 20:22       ` Derek Fawcus
2018-02-12  0:31         ` Robert Brockway

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=CAKr6gn19mY2SeSOui3PWx3SNXAvVFOET5EZX-TbgysOegC+2+g@mail.gmail.com \
    --to=ggm@algebras.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 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).