From: Larry McVoy <lm@mcvoy.com>
To: Dan Cross <crossd@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Interesting commentary on Unix from Multicians.
Date: Fri, 8 Apr 2022 08:28:34 -0700 [thread overview]
Message-ID: <20220408152834.GE29186@mcvoy.com> (raw)
In-Reply-To: <CAEoi9W5DCi=FZsMCqm9tZdtFvRBfcT7SZbFWukfTJ8p8dkc=CQ@mail.gmail.com>
On Fri, Apr 08, 2022 at 09:59:26AM -0400, Dan Cross wrote:
> Of course, by 1976, Unix was at 6th Edition and I can see why no one would
> want to go back to Multics (or being tied to a machine costing an order of
> magnitude more than a PDP-11). But one wonders what would have happened had
> Multics started accepting timesharing, say, 9 months earlier than it did.
Do we have any people around who actively used Multics long enough to
develop a feel for it? My only experience is the printout that Rob
Gingell had on his office door which was a description of Multics
paging in library after library before it actually ran the program.
I have no idea if it was that bad.
I guess what I'm trying to ask is if Multics had modern hardware
under it, performed well, would we want to be running it?
next prev parent reply other threads:[~2022-04-08 15:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 16:32 Dan Cross
2022-04-08 5:30 ` Lars Brinkhoff
2022-04-08 13:34 ` Clem Cole
2022-04-08 14:14 ` Dan Cross
2022-04-08 13:59 ` Dan Cross
2022-04-08 15:28 ` Larry McVoy [this message]
2022-04-08 15:35 ` Dan Cross
2022-04-08 19:36 ` Rich Morin
2022-04-08 21:02 ` Greg A. Woods
2022-04-08 23:34 ` Andrew Warkentin
2022-04-09 19:28 ` Greg A. Woods
2022-04-09 3:33 ` Adam Thornton
2022-04-09 12:10 ` tytso
2022-04-09 13:09 ` Dan Cross
2022-04-09 19:14 ` Greg A. Woods
2022-04-08 15:45 ` Jon Steinhart
2022-04-08 16:07 Noel Chiappa
2022-04-10 17:14 Noel Chiappa
2022-04-10 17:31 ` Larry McVoy
2022-04-10 20:41 ` John Cowan
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=20220408152834.GE29186@mcvoy.com \
--to=lm@mcvoy.com \
--cc=crossd@gmail.com \
--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).