The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Arthur Krewat <krewat@kilonet.net>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] If not Linux, then what?
Date: Mon, 26 Aug 2019 21:17:38 -0400	[thread overview]
Message-ID: <CAEoi9W5xRsb1Fc4=4kBTcgaGOrk1RLa+B97cU_dhTGv-rA9cog@mail.gmail.com> (raw)
In-Reply-To: <13c5c36e-c84d-e020-d09e-51c8c502dc6d@kilonet.net>

[-- Attachment #1: Type: text/plain, Size: 2571 bytes --]

On Mon, Aug 26, 2019, 7:14 PM Arthur Krewat <krewat@kilonet.net> wrote:

>
> https://linux.slashdot.org/story/19/08/26/0051234/celebrating-the-28th-anniversary-of-the-linux-kernel
>
> Leaving licensing and copyright issues out of this mental exercise, what
> would we have now if it wasn't for Linux? Not what you'd WANT it to be,
> although that can add to the discussion, but what WOULD it be?
>
> I'm not asking as a proponent of Linux. If anything, I was dragged
> kicking and screaming into the current day and have begrudgingly ceded
> my server space to Linux.
>
> But if not for Linux, would it be BSD? A System V variant? Or (the
> horror) Windows NT?
>
> I do understand that this has been discussed on the list before. I
> think, however, it would make a good late-summer exercise. Or late
> winter depending on where you are :)
>

This is an interesting question, though of course impossible to actually
answer in a meaningful way, as hypotheticals always are. But assuming one
could hold all else constant and just erase Linux from the picture, it
seems pretty obvious that some kind of BSD variant would have been "it."

I think a more interesting question, however, might be: had Linux not
happened, would that have opened the space for serious consideration of
alternative system architectures, either along Unix derivative lines, or
completely different? For example, perhaps something like plan 9 would have
had greater penetration into the market.

I saw a talk a couple of months ago that attributed the diversity of
systems in the 60s and 70s to the idea that people were trying so many
different things because no one knew _how_ to build systems. That may be at
least partially true, but I was wondering thinking about that very thing
this morning and realized that we're certainly swirling around the toilet
bowl converging on some central set of things we think work pretty well
(files! processes! threads!). But as time marches on and we see the
environment changing around us, we don't often go back and revisit these
sorts of fundamental assumptions. More's the shame, I'm afraid.

One wonders what's next. People now talk about Linux with the sort of
reverent tones they once discussed Windows and before that the mainframe.
Too big to fail, the Last System, etc. But there are cracks there: Fuchsia
is a different architecture, because that Unix model isn't going to
accommodate all contemporary use cases: the security model seems to be a
big driver here. Will they succeed? It'll be at least interesting to watch
and see.

        - Dan C.

[-- Attachment #2: Type: text/html, Size: 3534 bytes --]

  parent reply	other threads:[~2019-08-27  1:18 UTC|newest]

Thread overview: 96+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26 23:13 Arthur Krewat
2019-08-26 23:27 ` Warner Losh
2019-08-26 23:37   ` Larry McVoy
2019-08-26 23:56   ` William Pechter
2019-08-27  0:19     ` Arthur Krewat
2019-08-27  0:30       ` Larry McVoy
2019-08-27  0:58         ` Rob Pike
2019-08-27  1:06           ` Clem Cole
2019-08-27  2:53           ` Larry McVoy
2019-08-27  9:47             ` Rob Pike
2019-08-27  7:47           ` arnold
2019-08-27 16:05           ` [TUHS] Running v10 Angelo Papenhoff
2019-08-27 16:27             ` Henry Bent
2019-08-28  4:22               ` Jason Stevens
2019-08-28  7:34                 ` Angelo Papenhoff
2019-08-28 16:46                   ` Henry Bent
2019-08-27  0:59         ` [TUHS] If not Linux, then what? Arthur Krewat
2019-08-27  1:26           ` Dan Cross
2019-08-27  2:45             ` Larry McVoy
2019-08-27  3:14               ` Arthur Krewat
2019-08-27 14:55                 ` Larry McVoy
2019-08-27 22:30                   ` George Michaelson
2019-08-27 22:40                     ` Larry McVoy
2019-08-27 22:46                       ` George Michaelson
2019-08-27 22:59                         ` [TUHS] [SPAM] " Larry McVoy
2019-08-27 23:10                           ` [TUHS] " Clem Cole
2019-08-28  0:07                             ` George Michaelson
2019-08-28  3:22                           ` [TUHS] [SPAM] " Rob Pike
2019-08-28  3:25                             ` Rob Pike
2019-08-28  4:05                             ` Larry McVoy
2019-08-28 13:52                               ` Clem Cole
2019-08-28 14:31                                 ` [TUHS] " Larry McVoy
2019-08-28 14:57                                   ` Clem Cole
2019-08-28  6:19                         ` Wesley Parish
2019-08-28  6:30                           ` Peter Jeremy
2019-08-28 11:05                             ` Jason Stevens
2019-08-28 11:11                               ` Arrigo Triulzi
2019-08-28 14:04                               ` Clem Cole
2019-08-28 16:34                                 ` Henry Bent
2019-08-28 17:32                                   ` Larry McVoy
2019-08-28 17:51                                     ` Jon Forrest
2019-08-28 18:56                                     ` Clem Cole
2019-08-28 20:23                                       ` Arrigo Triulzi
2019-08-29  3:24                                       ` Lawrence Stewart
2019-08-29 10:55                                         ` Tony Finch
2019-08-28 13:57                             ` Clem Cole
2019-08-28 12:46                           ` Warner Losh
2019-08-27 23:16                       ` Bakul Shah
2019-08-27 23:33                         ` Larry McVoy
2019-08-28  0:21                           ` Bakul Shah
2019-08-28  1:21                             ` Arthur Krewat
2019-08-28  1:46                               ` Larry McVoy
2019-08-27  0:48   ` Clem Cole
2019-08-27  1:25     ` Gregg Levine
2019-08-27  2:16   ` Theodore Y. Ts'o
2019-08-27  2:39     ` Larry McVoy
2019-08-27  5:54       ` Adam Thornton
2019-08-27  6:05         ` Gregg Levine
2019-08-27  1:17 ` Dan Cross [this message]
2019-08-28  3:53 ` Charles H. Sauer
2019-08-28  4:30 ` Jason Stevens
2019-08-28  9:36 ` Angus Robinson
2019-08-28  9:50   ` Michael Kjörling
2019-08-28 10:48     ` arnold
2019-08-28 14:10   ` Earl Baugh
2019-08-28 14:55     ` Clem Cole
2019-08-28 14:22   ` Charles H Sauer
2019-08-28 15:00     ` Steve Nickolas
2019-08-28 15:37       ` Richard Salz
2019-08-28 19:54         ` Peter Jeremy
2019-08-28 20:05           ` Christopher Browne
2019-08-28 20:07 ` Christopher Browne
2019-08-28 20:27   ` Adam Thornton
2019-08-28 20:56     ` William Pechter
2019-08-28 22:24       ` Clem cole
2019-08-28 22:27     ` William Pechter
2019-08-28 22:53       ` Arthur Krewat
2019-08-29 18:40       ` Nemo Nusquam
2019-08-29 19:18         ` Steffen Nurpmeso
2019-08-28 22:28     ` Clem cole
2019-08-28 22:48       ` Adam Thornton
2019-08-28 23:01         ` William Pechter
2019-08-28 23:09           ` Adam Thornton
2019-08-29  6:37           ` Wesley Parish
2019-08-28 23:04       ` Gregg Levine
2019-08-29 11:12     ` Tony Finch
2019-08-28 23:19   ` Theodore Y. Ts'o
2019-08-29 13:31     ` A. P. Garcia
2019-08-29 13:55       ` Arthur Krewat
2019-08-29 15:54         ` Thomas Paulsen
2019-08-29 19:19           ` Steffen Nurpmeso
2019-08-31  1:35             ` Dave Horsfall
2019-08-31 15:14               ` Steffen Nurpmeso
2019-08-31 16:58     ` Christopher Browne
2019-08-31 21:20       ` Theodore Y. Ts'o
2019-08-28 21:02 ` Thomas Paulsen

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='CAEoi9W5xRsb1Fc4=4kBTcgaGOrk1RLa+B97cU_dhTGv-rA9cog@mail.gmail.com' \
    --to=crossd@gmail.com \
    --cc=krewat@kilonet.net \
    --cc=tuhs@minnie.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).