From: Greg Hudson ghudson@MIT.EDU
Subject: plan 9 and linux
Date: Thu, 6 Apr 1995 01:42:03 -0400 [thread overview]
Message-ID: <19950406054203.x3UEsGC5EbGUYCfrzhkJmXRL0Od0G2ThVwp1YtmYYAs@z> (raw)
Rob Pike wrote:
> 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.
BSD 4.4 (and, more practically, NetBSD) has the same properties--a
single source tree which compiles for seven or so different platforms.
There are still pieces that need to be made more architecture-
independent (e.g. the console driver), butbut it's still one system that
runs on a variety of different architectures. I'm afraid Xwindows
won't compile for BSD 4.4 in four seconds, though.
Just a note. There may be Mach-based operating systems with this
property as well, depending on your definitions.
next reply other threads:[~1995-04-06 5:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-04-06 5:42 Greg [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-04-06 21:49 Charles
1995-04-06 4:57 rob
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=19950406054203.x3UEsGC5EbGUYCfrzhkJmXRL0Od0G2ThVwp1YtmYYAs@z \
--to=9fans@9fans.net \
/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).