The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: marc.donner@gmail.com, crossd@gmail.com
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: LOC [was Re: Re: Re.: Princeton's "Unix: An Oral History": who was in the team in "The Attic"?
Date: Wed, 09 Nov 2022 01:49:21 -0700	[thread overview]
Message-ID: <202211090849.2A98nLRe006143@freefriends.org> (raw)
In-Reply-To: <CAEoi9W4dz7vvjyaXu26Zv5KXXujQzbh18=9wTrrW24qRS3zxig@mail.gmail.com>

Dan Cross <crossd@gmail.com> wrote:

> To tie this back to TUHS a little bit...when did being a "sysadmin" become
> a thing unto itself? And is it just me, or has that largely been superceded
> by SRE (which I think of as what one used to, perhaps, call a "system
> programmer") and DevOps, which feels like a more traditional Unix-y kind of
> thing?
>
>         - Dan C.

Sys admin was a thing in the mid-80s already; I worked as one at the Emory
U Computing Center for several years, ~ 1985 - 1990.  Around then USENIX
started the LISA (Large Installation System Administratin) workshops.
Clem can undoubtedly tell us exactly when.

And yes, SRE + dev ops seem to have displaced that, with SRE focusing
more on keeping the bazillions of systems up and running, and DevOps on
things like build and CI/CD systems.

Personally, I'm glad to have gained the sys admin experience, but I
don't want to do it for a living; it's much more fun building product
and letting someone else have the headaches. :-)

Arnold

  reply	other threads:[~2022-11-09  8:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 11:15 [TUHS] " Paul Ruizendaal via TUHS
2022-10-11 13:48 ` [TUHS] " Larry McVoy
2022-10-11 13:59   ` Warner Losh
2022-10-11 19:43     ` Marc Donner
2022-10-11 19:54       ` Larry McVoy
2022-10-11 20:02         ` Michael Kjörling
2022-10-11 20:08           ` Rob Pike
2022-10-11 21:07             ` Dan Cross
2022-10-11 21:41               ` Rob Pike
2022-10-12  6:59             ` arnold
2022-10-12  7:03               ` Michael Kjörling
2022-10-12  7:18                 ` Rich Morin
2022-11-29  7:31               ` Joseph Holsten
2022-10-11 20:10           ` Larry McVoy
2022-10-11 20:14             ` Michael Kjörling
2022-10-11 20:33               ` [TUHS] LOC [was " Charles H Sauer (he/him)
2022-11-07 17:50                 ` [TUHS] " Warner Losh
2022-11-07 19:57                   ` Bakul Shah
2022-11-07 20:11                   ` Dan Cross
2022-11-08 18:55                   ` Marc Donner
2022-11-09  8:41                     ` Dan Cross
2022-11-09  8:49                       ` arnold [this message]
2022-11-09 20:17                         ` Dave Horsfall
2022-11-09  9:01                       ` steve jenkin
2022-11-09 10:55                         ` Brad Spencer
2022-11-09 11:56                         ` Stuart Remphrey

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=202211090849.2A98nLRe006143@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=crossd@gmail.com \
    --cc=marc.donner@gmail.com \
    --cc=tuhs@tuhs.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).