9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Victor Yodaiken yodaiken@sphinx.cs.nmt.edu
Subject: plan 9 and other operating systems
Date: Fri,  7 Apr 1995 13:24:15 -0400	[thread overview]
Message-ID: <19950407172415.zbRubcnNtQ2hYlTUdgMgdfIoPSrNv_hKwFe5sTS33R8@z> (raw)

On Apr 7,  5:43am, forsyth@plan9.cs.york.ac.uk wrote:
 Subject: plan 9 and other operating systems
>i recently replied to a question about how plan 9 compared to Linux.
>this prompted an important addition from rob, and comments from several
>others.  whilst i was considering the question further last night,

I have one serious comment. Linux is a mess, but A) it works, and
B) it is totally unencumbered, and C) it has a large and active
distributed free support system. While I am happy to have access
to Plan9 and look forward to the new release, I am reluctant to 
rely on it in for educational purposes because of the sorry history
of access to UNIX. Suppose we organized an ongoing o.s. research
group and developed new facilities (say real-time or fault recovery)
starting from the ATT code. Would we find ourselves in the same
situation as Berkeley -- without the extensive legal staff of the
UC system? This is not a complaint -- I realize that the folks
at ATT research have little control over coporate legal policy.
But, I did want to explain why some of us litigation-shy folks are
tempted by Linux despite the poor coding and sloppy design.








             reply	other threads:[~1995-04-07 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-04-07 17:24 Victor [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-04-07 22:13 Bill
1995-04-07 21:31 Charles
1995-04-07  9:43 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=19950407172415.zbRubcnNtQ2hYlTUdgMgdfIoPSrNv_hKwFe5sTS33R8@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).