From: G. David Butler gdb@dbSystems.com
Subject: Commercial Use of Plan 9
Date: Mon, 2 Jun 1997 08:05:09 -0500 [thread overview]
Message-ID: <19970602130509.3FPpq9sh27-GPrBwZ_1it5-yCyQDo7kqW4DfQPP-qQs@z> (raw)
I wrote:
>OK, so now you have "researched" Plan 9 from Bell Labs, er, Lucent
>Technologies and have decided that it would make a reasonable platform
>for some application. Now what?
Well I have waited long enough to post the results of my query. These
are the number of commitments:
Appliances: 0
Clients: 4
Servers: 0
And the number of maybes:
Appliances: 0
Clients: 7
Servers: 2
The message is, there is *no* opportuity for this business.
I know there are companies that have licensed Plan 9. Are there any
interested in selling commercial use licenses to holders of the source
license?
Thanks for the feedback.
David Butler
gdb@dbSystems.com
next reply other threads:[~1997-06-02 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-06-02 13:05 G.David [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-05-16 22:52 Bengt
1997-05-15 4:46 G.David
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=19970602130509.3FPpq9sh27-GPrBwZ_1it5-yCyQDo7kqW4DfQPP-qQs@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).