From: "Aram Hăvărneanu" <aram.h@mgk.ro>
To: 9fans <9fans@9fans.net>
Subject: [9fans] Closed nix development is an insult
Date: Fri, 6 Sep 2013 01:13:59 +0300 [thread overview]
Message-ID: <CAEAzY3-2cP9pqGFVL_OckXxzJZ7BGE1mhdbJpP-HEanCyi4UbQ@mail.gmail.com> (raw)
Is nix closed source, dead, or vaporware?
The daily generated nix.tgz is either not daily generated or the
tree which it is archiving is dead. Most files are from 2012, most
recent file (nix/sys/log/nixdistr) is from Feb 8 2013, the kernel
is from Jul 10 2012.
The variant posted on sources is even older. Perhaps the 9P service
at sources.lsub.org is newer? Nope, same thing:
--rw-rw-r-- M 0 nemo sys 1964 Jul 10 2012 k8cpu
This blog mentions a lot of new development happening:
http://syssoftware.blogspot.com. Unfortunately, all that development
either is vaporware or under closed doors. The author mentions in
many places that the source will be "published soon". Unfortunately
this has not happened.
Interestingly, the nix source published in 9atom contains newer
files, May 20th to be exact. It's not just new drivers ported from
9atom, the newest non-driver, k10-specific file is stamped May 16th.
I don't know if the timestamps are simply wrong or some priviledged
people do get access to the source.
Considering how little interest is in Plan 9 these days, locking
Plan 9 under closed doors is a disgrace to this community.
--
Aram Hăvărneanu
next reply other threads:[~2013-09-05 22:13 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 22:13 Aram Hăvărneanu [this message]
2013-09-05 22:35 ` erik quanstrom
2013-09-06 8:49 ` Richard Miller
2013-09-06 9:52 ` Francisco J Ballesteros
2013-09-06 10:24 ` hiro
2013-09-05 22:36 ` Francisco J Ballesteros
2013-09-05 23:07 ` Kurt H Maier
2013-09-06 8:27 ` Steve Simon
2013-09-06 22:59 ` BurnZeZ
2013-09-06 23:00 ` Francisco J Ballesteros
2013-09-07 19:15 ` Christopher Nielsen
2013-09-06 23:10 ` Kurt H Maier
2013-09-06 23:35 ` Aram Hăvărneanu
2013-09-06 23:42 ` Nemo
2013-09-07 2:49 ` erik quanstrom
2013-09-07 4:06 ` Devon H. O'Dell
2013-09-07 4:36 ` Bruce Ellis
2013-09-07 6:24 ` pmarin
2013-09-07 13:21 ` Kurt H Maier
2013-09-07 13:28 ` Bruce Ellis
2013-09-07 13:33 ` Kurt H Maier
2013-09-07 13:41 ` Bruce Ellis
2013-09-07 13:56 ` Aram Hăvărneanu
2013-09-07 14:32 ` Bruce Ellis
2013-09-07 14:52 ` Latchesar Ionkov
2013-09-07 16:28 ` erik quanstrom
2013-09-07 17:01 ` Latchesar Ionkov
2013-09-07 17:48 ` Gorka Guardiola
2013-09-07 20:46 ` Charles Forsyth
2013-09-07 23:47 ` Matthew Veety
2013-09-08 0:19 ` Charles Forsyth
2013-09-08 7:00 ` Bruce Ellis
2013-09-07 14:58 ` Anthony Sorace
2013-09-07 15:05 ` Bruce Ellis
2013-09-07 15:14 ` tlaronde
2013-09-07 15:46 ` lucio
2013-09-07 16:06 ` tlaronde
2013-09-07 16:40 ` lucio
2013-09-07 16:56 ` Ethan Grammatikidis
2013-09-07 17:45 ` lucio
2013-09-07 17:50 ` lucio
2013-09-07 16:57 ` tlaronde
2013-09-07 16:35 ` Ethan Grammatikidis
2013-09-06 23:48 Terry Wendt
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=CAEAzY3-2cP9pqGFVL_OckXxzJZ7BGE1mhdbJpP-HEanCyi4UbQ@mail.gmail.com \
--to=aram.h@mgk.ro \
--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).