9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: not just toasters
Date: Fri,  6 Oct 1995 03:44:07 -0400	[thread overview]
Message-ID: <19951006074407.Jqynl8Oh-WKM9SPlLI3LBfd73WlfZ38PtONCoiREFsg@z> (raw)

pc PRO (``Computing in the Real World'') is A Dennis Publication [no relation]
in Britain.  it's more thoughtful and interesting than the usual pulp of PC mags.

it has a regular UNIX column by David Evnull; in the latest, November 1995 issue, it begins:
	Plan 9 from outa AT&T

   You've seen the B-movie, probably bought the T-shirt,
   now try the operating system courtesy of David Evnull

   Instead of a Unix Installathon this month ... I've decided to install
   something that isn't Unix onto the Gateway P5/90, the Installathon's
   victim machine.  No, I haven't gone crazy and switched to NT, I've
   decided to look at Plan 9.  Now, Plan 9 is steeped in Unix culture
   and it shares a lot of commands with Unix, but it isn't in any way Unix.

it continues for 2-1/3 pages with a discussion of the history, aspects of
the design, name spaces, file servers, his own installation of the 4 diskette system,
and favourable one-paragraph discussions of some of the novelties of 8½, rc, and sam.  He mentions the Unix ports/clones of sam, rc, and 8½.
The most significant omission is acme.  Unlike some other mentions i've seen in the press
this article is not obviously a condensation of the press release,
although inevitably it covers similar ground.

there's a picture of an 8½ screen showing games/catclock, rc, mothra, games/swar,
and sam open on /lib/vgadb.






                 reply	other threads:[~1995-10-06  7:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=19951006074407.Jqynl8Oh-WKM9SPlLI3LBfd73WlfZ38PtONCoiREFsg@z \
    --to=forsyth@plan9.cs.york.ac.uk \
    /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).