From: Dave Mason dmason@plg.uwaterloo.ca
Subject: Plan 9 encumbrance
Date: Tue, 11 Apr 1995 20:02:56 -0400 [thread overview]
Message-ID: <19950412000256.h6W7HW2n7kzpmo83fX6eyG0Rz-1VDerV-4ACYUTtoG8@z> (raw)
dmr@plan9.att.com writes:
> The terms of the new Plan 9 distribution will be much more liberal
[... and look completely reasonable ]
> By contrast, Unix source licenses were and are fearsome documents,
> with references to trade-secret "methods and concepts" and
> restrictions on use even for educational purposes.
>
> Fundamentally, USL sued BSDI and then UC Berkeley for producing
> a Unix clone (and lost). BSDI and UCB's CSRG thought this
> was a worthwhile thing to do because the real thing was overpriced
> and hard to get. Plan 9 will be cheap and easy to get.
> Situations change, and we learn.
My question is: If I get and read and enjoy your distribution, and
then decide I want to write a commercial equivalent of some part of
Plan 9 (say my own implementation of Alef to run under Windows-NT --
don't worry, I already went and washed my mouth out), what will AT&T
and/or its lawyers say about it? Or I think I see how to build the
kernel better? As an OS researcher, this is a *very* relevant
question for me. While the USL silliness was going on I was thanking
my lucky stars that I'd never looked at any Unix system code.
What about the authors of vsta (a plan-9 inspired system about to
release version 1.4)? Must they *not* look at the plan-9 code? They
currently don't use exactly the message format that plan-9
does... what if they change to use the right one?
Very much looking forward to the release... if I can look at it.
../Dave
next reply other threads:[~1995-04-12 0:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-04-12 0:02 Dave [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-04-15 2:46 Dave
1995-04-12 12:43 arnold
1995-04-12 12:33 arnold
1995-04-12 8:20 Alistair
1995-04-12 3:00 Andi
1995-04-12 1:57 arnold
1995-04-09 4:23 dmr
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=19950412000256.h6W7HW2n7kzpmo83fX6eyG0Rz-1VDerV-4ACYUTtoG8@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).