9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: aram.h@mgk.ro, 9fans@9fans.net
Subject: Re: [9fans] Closed nix development is an insult
Date: Thu,  5 Sep 2013 18:35:11 -0400	[thread overview]
Message-ID: <dc8d8530dc40ca5498f855def98843f1@ladd.quanstro.net> (raw)
In-Reply-To: <CAEAzY3-2cP9pqGFVL_OckXxzJZ7BGE1mhdbJpP-HEanCyi4UbQ@mail.gmail.com>

> 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.

it might be that the 9atom cd is a little out of date.  if you do
a pull you or simply go to /n/atom/plan9/sys/src/nix you will
see newer files.

port/devws.c and port/taslock.c were modified
today.  though the modification was fairly trivial, they set the
stage for improved locking.  (initial tests failed to show
improvement, however, perhaps *because* the locking was better.)

a few days ago, acpi boot was made the default.  thanks to cinap
and nemo for the aml interperter.

the 9atom nix kernel is, modulo time skew, the same as the one
running 9atom machines, my machines, etc.

all the changes are in /n/atom/patch.  anyone can submit patches.
you can subscribe to the change list (echo subscribe | mail \
sources-owner@9atom.org).  so, to turn the question around a bit,
why haven't there been many submissions?

tl;dr: as far as i know, there is no private nix development going on,
although there might be some unfinished projects, or research.

- erik



  reply	other threads:[~2013-09-05 22:35 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 22:13 Aram Hăvărneanu
2013-09-05 22:35 ` erik quanstrom [this message]
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=dc8d8530dc40ca5498f855def98843f1@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    --cc=aram.h@mgk.ro \
    /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).