The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: segaloco <segaloco@protonmail.com>,
	Joseph Holsten <joseph@josephholsten.com>,
	segaloco <tuhs@tuhs.org>
Subject: [TUHS] Re: [OT?] 1993 'Sourceware' paper anniversary. What was right & any surprises?
Date: Thu, 10 Nov 2022 10:33:13 -0500	[thread overview]
Message-ID: <CAC20D2Pw224fiy1x3j2QoDLoyVy4QjCEAt36pueaA-MnU3t3xw@mail.gmail.com> (raw)
In-Reply-To: <Y2yWy8BYFxFiIy4D@mit.edu>

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

On Thu, Nov 10, 2022 at 1:14 AM Theodore Ts'o <tytso@mit.edu> wrote:

> I'd also argue that (a) the differences between the Linuxes aren't as big
> some people would make it out to be
>
It's all a matter of degree and what things bite you.   This is why we had
to develop the cluster checker because Linux is all over the place
>>still<< -- one famous ISV had 144 possible differences between 'standard'
Linux cluster configurations they needed to test.   BTW:  that had been a
developer during the UNIX wars and pure Fortran on VMS/IBM etc days.   I
suspect they would claim it was not much better for them.

Is it better in some areas? Sure, in another no.  It depends if it's
something that bites you and you care about.  Things like the "systemd
wars" did not help which I would contend was not much less glorious that
the Unix wars -- just different players.   In the end, it's all about who
is making the call of what is different/what is changing.  I'm too old to
get too religious about this.

The 'sameness' is because of UNIX not because of Linux.   Ken and Dennis's
core ideas created an industry and set of systems that are all 'close
enough that we all can get work done.   In the end, at any given time, one
group or any other will have the incentive to have their way lead the
market - and the hard part for many of us to accept is that the incentive
is most often *economic not technical*.

Larry's old paper nailed the basic issue.   It was use the core ideas of
Ken and Dennis - (call it anything you want) - and make it freely available
to remove the economic barriers.   This is what Linux exploited, and that
is what made it successful.   I'm pleased to say, that Larry's 'Sourceware'
came about --> today its in the form of Linux.  But the ideas (the core IP)
is called UNIX.  And yes there are specific differences.  But in general;
they are close enough.

ᐧ

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

  parent reply	other threads:[~2022-11-10 15:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 22:01 [TUHS] " steve jenkin
2022-11-09 22:16 ` [TUHS] " Larry McVoy
2022-11-09 22:24   ` Clem Cole
2022-11-09 22:51   ` Joseph Holsten
2022-11-10  0:47     ` segaloco via TUHS
2022-11-10  0:54       ` Joseph Holsten
2022-11-10  1:28       ` David Arnold
2022-11-10  6:14         ` Theodore Ts'o
2022-11-10  9:12           ` David Arnold
2022-11-10 13:27             ` Tom Ivar Helbekkmo via TUHS
2022-11-10 15:33           ` Clem Cole [this message]
2022-11-10  1:42       ` Larry McVoy

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=CAC20D2Pw224fiy1x3j2QoDLoyVy4QjCEAt36pueaA-MnU3t3xw@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=joseph@josephholsten.com \
    --cc=segaloco@protonmail.com \
    --cc=tuhs@tuhs.org \
    --cc=tytso@mit.edu \
    /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).