From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Closed nix development is an insult
Date: Sat, 7 Sep 2013 12:28:05 -0400 [thread overview]
Message-ID: <57f75c237dedeb638c0a67cc3de11115@kw.quanstro.net> (raw)
In-Reply-To: <CAEAzY38ZybH=BVrM1zOKJ0VyHoAPgn=HL5QO1fPHMx_DfDT+=g@mail.gmail.com>
> [...] Nix is
> not a personal project. It's listed right there on the lsub page
one thing seems to be missed is that nix is the name for at least
two independent projects.
a brief history. this is the best of my understanding. please
correct me if i haven't credited folks properly. i am sure there
are bits i don't know.
at one time there was unified open development on google code
(or whatever site it was). this was based on the 9k work.
some of the participants felt that this wasn't working out
due to differences in direction, and the fact that hg was a pain.
so this split into a project called NxM and nix, which was
hosted at lsub using a patch-like process. but lsub was interested
in some disruptive changes, and there was a conflicting desire for
a kernel to replace the 386 kernel. so i moved this 386-replacement
kernel into 9atom. we run exactly this code every day on ~32 machines.
9atom accepts patches (see /n/atom/plan9/rc/bin/apatch), there
is a mailing list for changes (sources@9atom.org) or if you prefer
/n/atom/patch.
> > there is no private nix development going on
>
> Let's quote something from a recent nix paper:
>
> "We are grateful to Charles Forsyth for his advice regarding this
> work, and to the new Plan 9 secret society."
>
> Ahem.
*WOOSH*.
this is an obvious joke. see e.g. http://9fans.net/archive/2006/06/18
either that or you're just trolling.
- erik
next prev parent reply other threads:[~2013-09-07 16:28 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
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 [this message]
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=57f75c237dedeb638c0a67cc3de11115@kw.quanstro.net \
--to=quanstro@quanstro.net \
--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).