From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] questions about 9atom and 9legacy; and their updates
Date: Thu, 18 Dec 2014 16:06:51 +0100 [thread overview]
Message-ID: <CAOEdRO36CL2GtEVoLiXxEtvkqRA9eXiWNusCoC3qMG6ApU=AKQ@mail.gmail.com> (raw)
Hello,
I've been recently reconsidering employment of
plan9. And (probably like many others) I find myself
indecisive about whom to follow. It seems that the
most conservative option is Bell Labs (BL). Then, still in
sync, there is 9legacy. Slightly separate there is 9atom,
and finally there is 9front. The latter two probably
live on their own. The questions that arise:
1) How often does Bell Lab's version change? How often/well
do patches from 9legacy enter BL's version? Some numbers?
2) How do 9atom and 9legacy notice that there has been
a change in BL? (I'd guess that 9legacy could notice
immediately, but ...) How is it with 9atom?
3) How is updating supposed to work in case of 9atom
and 9legacy (as compared to BL's replica) I.e., when
I decide to use either 9atom or 9legacy and at some
point there is some change in them, will I / can I
easily notice and follow?
4) Is there any good reason not to follow 9atom, but
BL instead?
5) I am puzzled about licences. At one point I almost
thought that the software is actually BSD-like
(i.e. you can do almost whatever, no copyleft,
Lucent Public License Version 1.02). Now I read:
In February 2014 the University of California, Berkeley, has been
authorised by the current Plan 9 copyright holder – Alcatel-Lucent
– to release all Plan 9 software previously governed by the Lucent
Public License, Version 1.02 under the GNU General Public License,
Version 2
so the mentioned univesity will offer it under GPL, which is viral
(is copyleft). That surprises me...
Thanks for your comments!
Ruda
next reply other threads:[~2014-12-18 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 15:06 Rudolf Sykora [this message]
2014-12-18 15:46 ` David du Colombier
2014-12-19 3:11 ` da Tyga
2014-12-19 10:02 ` Rudolf Sykora
2014-12-19 10:10 ` David du Colombier
2014-12-19 10:48 ` Rudolf Sykora
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='CAOEdRO36CL2GtEVoLiXxEtvkqRA9eXiWNusCoC3qMG6ApU=AKQ@mail.gmail.com' \
--to=rudolf.sykora@gmail.com \
--cc=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).