The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: steve jenkin <>
To: TUHS <>
Subject: [TUHS] [OT?] 1993 'Sourceware' paper anniversary. What was right & any surprises?
Date: Thu, 10 Nov 2022 09:01:42 +1100	[thread overview]
Message-ID: <> (raw)

I’ve only recently stumbled across this paper.

It gives the answer to one question I’ve had:

	Why did Linux become more popular than everything that came before it?

There were surprises.
The “Dot Boom” then “Dot Bust” along with Y2K.

Microsoft developed an architecture, Active Directory, designed to support Enterprise scale deployments.

Everything Good in A.D. is Old (LDAP, Kerberos, DNS)
everything badly done is New (replicated DB’s & ???).

Other surprises is the rise of “Internet Scale” datacentres, Social Media and Smartphones & Tablets.
All of which are dominated by Linux or Unix derived solutions.

And Virtual Machines on Intel.
IA-64 was in the far future :(

And ARM CPU’s made a big comeback.


The Sourceware Operating System Proposal
	9 November 1993 
	Revision: 1.8

Steve Jenkin, IT Systems and Design 
0412 786 915 (+61 412 786 915)
PO Box 38, Kippax ACT 2615, AUSTRALIA

             reply	other threads:[~2022-11-09 22:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 22:01 steve jenkin [this message]
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
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

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