The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: doug@cs.dartmouth.edu (Doug McIlroy)
Subject: [TUHS} Running V8 ...
Date: Mon, 16 Oct 2017 07:58:40 -0400	[thread overview]
Message-ID: <201710161158.v9GBweD4005539@coolidge.cs.Dartmouth.EDU> (raw)

> How realistic would the experience be to actually running the system
> described in the Unix Programming Environment [v8] if it's actually
running > BSD 4.1... Thanks for any insights y'all might have on this.

This question bears on a recent thread about favorite flavors of Unix. My
favorite flavor is Universal Unix, namely the stuff that just works
everywhere. That's essentially what K&P is about.

That's also what allowed me to use a giant Cray with no instruction
whatsoever. And to do everyday "programmering" on the previously
inscrutable Macintosh, thanks to OS X.

The advent of non-typewriter input put a damper on Universal Unix. One has
to learn something to get started with a novel device. I am impressed,
though, by the breadth of Universal Unix that survives behind those
disparate facades.


             reply	other threads:[~2017-10-16 11:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 11:58 Doug McIlroy [this message]
2017-10-16 15:41 ` Don Hopkins
2017-10-17 11:47   ` Tony Finch
2017-10-17 14:30     ` Larry McVoy
2017-10-17 14:50     ` Don Hopkins
2017-10-16 16:28 ` Clem Cole
2017-10-16 16:39   ` [TUHS} Running V8 ... [ really basic tools ] Jon Steinhart
2017-10-16 19:16     ` Ian Zimmerman
2017-10-16 19:28       ` Jon Steinhart
2017-10-17  1:15         ` Ian Zimmerman
2017-10-17  4:20           ` UNIX version 2*pi Don Hopkins
2017-10-17  6:08             ` Dave Horsfall
2017-10-17 18:23               ` Ron Natalie
2017-10-18  2:46                 ` Dave Horsfall
2017-10-18 10:15                   ` Ron Natalie
2017-10-16 16:38 ` [TUHS} Running V8 Will Senn

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=201710161158.v9GBweD4005539@coolidge.cs.Dartmouth.EDU \
    --to=doug@cs.dartmouth.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).