9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rob@plan9.att.com rob@plan9.att.com
Subject: plan 9 and linux
Date: Thu,  6 Apr 1995 00:57:54 -0400	[thread overview]
Message-ID: <19950406045754.xYnqZaJfOKApjJcmfpTu2EVeHjewo5ma_5oMj5aqvD4@z> (raw)

Forsyth missed one important difference.  Plan 9 is not a PC operating
system, although it works on a PC.  As shipped, Plan 9 runs on four
instruction architectures (SPARC, MIPS, 68020, 386), with machines
from many vendors (Sun, SGI, Next, Mips, AT&T, and endless PC's).
The PC is an important platform for the system, but not the only one.
I've been thinking about it and I cannot recall any other system
that is shipped in one piece to run on a wide variety of platforms.
I may be wrong, but every other system I can think of is built for
one system and then ported to another; with Plan 9, the system is
carried along together for all architectures, compiled from one source
tree, etc.  It's really one system that runs on a variety of hardware,
rather than different versions with a common ancestor.

A related property is that it is configurable to run on anything from
a laptop to a network of multiprocessor servers.

So comparing it to Linux makes sense only for a narrow subset of
what the system is capable of.

For the record: in our lab version of the system, somewhat different
from what's going out, the window system compiles from C into
a ready-to-go executable in 4 seconds.  I don't think Linux can do
that.






             reply	other threads:[~1995-04-06  4:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-04-06  4:57 rob [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-04-06 21:49 Charles
1995-04-06  5:42 Greg
1995-04-05 16:18 Dirk
1995-04-05 13:56 Nigel
1995-04-05 10:15 forsyth

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=19950406045754.xYnqZaJfOKApjJcmfpTu2EVeHjewo5ma_5oMj5aqvD4@z \
    --to=rob@plan9.att.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).