9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] commercial deployment
Date: Thu, 19 Jul 2001 15:28:15 -0400	[thread overview]
Message-ID: <20010719192828.47A611998A@mail.cse.psu.edu> (raw)

//Is there or will there ever be commercial/industrial deployment of plan9?

short answer: yes, sort of.
long answer: that depends, what does that mean to you?

there are a number of people who use Plan 9 in their "day jobs", in industry or
commercial environments, even though those jobs likely have nothing to do
with plan 9. i did that when i admined Unix boxes, for example.

as mentioned a few times here, plan 9's been used in several projects in the
labs, like the VPN brick, that may someday see the light of day (hey, i'd buy
one of those if i could).

i believe somebody outside the labs was using Plan 9 in a hardware mpeg
encoder.  is that still going on? which edition?

and, of cource, the Plan 9 and Inferno development are done using it.

while Plan 9 still tends to think of itself as a research operating system, it's
certainly usable in production/commercial environments, and is quite stable -
perhaps moreso than many OSs that _do_ explicitly consider themselves
production quality.

nicely packaged Plan 9 sets - with the manuals and papers printed and nicely
bound and a CD with the distribution and various add-ons - are sold by Vita
Nuova, commercially.

the current license is much friendlier to commercial use than the 2nd edition
on (that is, it allows it at all). i can't figure out how to compare Plan 9's Open
Source license to the other Open Source licenses (cough*GPL*cough) in terms
of suitability for commercial use without risking a flame war.

there is not, however, industry support for Plan 9 the way there is for other
OSs, either in terms of hardware vendors explicitly supporting Plan 9 drivers
or providing such themselves, or in terms of commercial software vendors
writing for Plan 9. nor can you get Plan 9 pre-installed on a new PC (AFAIK).
-α.



             reply	other threads:[~2001-07-19 19:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-19 19:28 anothy [this message]
2001-07-19 20:36 ` Mike Haertel
2001-07-19 22:34   ` Fariborz 'Skip' Tavakkolian
2001-07-20  8:59   ` Alberto Nava
2001-07-20 16:47   ` Ozan Yigit
2001-07-20 21:52     ` Rick Hohensee
2001-07-24 11:34       ` Ozan Yigit
2001-07-25  1:40         ` Rick Hohensee
2001-07-25  3:52           ` Boyd Roberts
2001-07-25  8:10             ` [9fans] more lucent bad news - another 15,000 to 20,000 jobs to go Matt
2001-07-26  8:48           ` [9fans] commercial deployment Ozan Yigit
2001-07-20 21:56     ` Boyd Roberts
  -- strict thread matches above, loose matches on Subject: below --
2001-07-26 11:55 rob pike
2001-07-26 13:23 ` Boyd Roberts
2001-07-26 14:01 ` Rick Hohensee
2001-07-26 15:38 ` Ozan Yigit
2001-07-21 17:32 bwc
2001-07-20 14:20 bwc
2001-07-21  9:53 ` Steve Kilbane
2001-07-19  8:24 Stephen King

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=20010719192828.47A611998A@mail.cse.psu.edu \
    --to=anothy@cosym.net \
    --cc=9fans@cse.psu.edu \
    /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).