The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wobblygong@gmail.com (Wesley Parish)
Subject: [TUHS] Why BSD didn't catch on more, and Linux did
Date: Fri, 9 Feb 2018 15:53:22 +1300	[thread overview]
Message-ID: <CACNPpeZ1B5MoRn9dvrWQOfua+bqmxMW5LujMsicHa4TC92A7qQ@mail.gmail.com> (raw)
In-Reply-To: <CAJfiPzw8-Ty1U75yOSmGarJqy7hzmGLNfu5DhSet+BxS8G04Fg@mail.gmail.com>

On 2/8/18, Nemo <cym224 at gmail.com> wrote:
> On 7 February 2018 at 03:27, Wesley Parish <wobblygong at gmail.com> wrote:
>> OS/2 and Windows (including WinNT 3.x) just
>> added a pretty-pretty interface. OS/2 was more sophisticated than
>> WinNT's because OS/2 expected to share the hard drive with some other
>> OS; Microsoft believed it had the computer to itself and is thus not
>> as sophisticated - but they're still MS/PC/DR DOS  writ large.
>
> I would disagree with this assessment.  NT's VMS heritage has already
> been discussed.  I do not know the heritage of OS/2 but to call it DOS
> is simply not true.  (Among other things, OS/2 did an excellent job of
> virtualizing dosboxes. We were developing PCMCIA drivers with OS/2 in
> dosboxes.  When one crashed, you simply opened up another and
> continued.)
>
> N.
>
I was referring to the installation procedures. IBM OS/2 2.0 to 4.0
installation procedures were more sophisticated than the equivalent in
MS WinNT from 3.x to 5.x because Microsoft did not show any interest
in sharing the disk with anyone.

But it's still true if one refers to single user versus multiuser -
WinNT's got a lot of OS/2 and VMS in its history, and OS/2's got a lot
of IBM's MVS and related mainframe OS knowledge in its background, but
they're not native multiuser. You need to get add-ons to make them
truly multiuser. In that they are still MS/PC/DR DOS writ large.
(Which is ironical considering that there have been at least two
genuine multiuser DOS clones on the market that I know of, DR's
Multiuser DOS - not Concurrent DOS: that was a similar but different
product - and PCMOS.)

Wesley Parish


  reply	other threads:[~2018-02-09  2:53 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
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 [this message]
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=CACNPpeZ1B5MoRn9dvrWQOfua+bqmxMW5LujMsicHa4TC92A7qQ@mail.gmail.com \
    --to=wobblygong@gmail.com \
    /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).