From: Benjamin Huntsman <BHuntsman@mail2.cu-portland.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] There is no fork
Date: Mon, 12 Feb 2018 00:58:37 +0000 [thread overview]
Message-ID: <MWHPR03MB2573919DE3059389155DA3B5E4F70@MWHPR03MB2573.namprd03.prod.outlook.com> (raw)
In-Reply-To: <CAHL7psFvCk=2ZV_WBxEP=MR52BrT+YEnABjG0i3pFahqVkBPmA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]
> Out of curiosity, what's your use case for the NIX kernel?
Use case?? My use case for NIX, and Plan 9 in general, is basically "fun" and "curiosity". For my day job I run AIX, IBM i, and Windows when I have to (which is a lot) :)
________________________________
From: 9fans-bounces@9fans.net <9fans-bounces@9fans.net> on behalf of Giacomo Tesio <giacomo@tesio.it>
Sent: Sunday, February 11, 2018 4:20 PM
To: Fans of the OS Plan 9 from Bell Labs
Subject: Re: [9fans] There is no fork
2018-02-12 0:48 GMT+01:00 Benjamin Huntsman <BHuntsman@mail2.cu-portland.edu>:
> Or, if one wants NIX but to stay a little closer to the original
> distribution, are there options, or is Harvey the only way?
Out of curiosity, what's your use case for the NIX kernel?
@Lyndon: https://bitbucket.org/forsyth/plan9-9k
forsyth / plan9-9k — Bitbucket<https://bitbucket.org/forsyth/plan9-9k>
bitbucket.org
Source for an experimental 64-bit Plan 9 kernel, and supporting software. It features a revised memory-management system, MCS spin locks, and other changes to system ...
@Rui: Jehanne diverged a lot from Plan 9, in a pursuit for my vision
of simplicity.
While it's in no way a Unix, many won't even consider it a Plan 9
system. Still for anyone interested: http://jehanne.io
Jehanne<http://jehanne.io/>
jehanne.io
Jehanne, an operating system derived from Plan9. Introduction overview, screen shot, Joan Documentation
Giacomo
[-- Attachment #2: Type: text/html, Size: 6952 bytes --]
next prev parent reply other threads:[~2018-02-12 0:58 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 2:48 Benjamin Huntsman
2018-02-10 4:24 ` Lucio De Re
2018-02-10 10:43 ` Ethan Grammatikidis
2018-02-10 4:43 ` Jens Staal
2018-02-10 10:46 ` hiro
2018-02-10 10:51 ` Ethan Grammatikidis
2018-02-10 11:59 ` hiro
2018-02-10 14:54 ` Ethan Grammatikidis
2018-02-10 12:03 ` as
2018-02-11 12:26 ` Giacomo Tesio
2018-02-11 13:48 ` Rui Carmo
2018-02-11 22:40 ` Lyndon Nerenberg
2018-02-11 23:48 ` Benjamin Huntsman
2018-02-12 0:20 ` Giacomo Tesio
2018-02-12 0:58 ` Benjamin Huntsman [this message]
2018-02-12 1:10 ` Ethan Grammatikidis
2018-02-12 8:33 ` Giacomo Tesio
2018-02-12 13:05 ` Ethan Grammatikidis
2018-02-12 13:39 ` Lucio De Re
2018-02-13 13:59 ` Ethan Grammatikidis
2018-02-12 15:21 ` Giacomo Tesio
2018-02-12 15:50 ` Chris McGee
2018-02-12 16:13 ` tlaronde
2018-02-12 18:51 ` Steve Simon
2018-02-12 20:40 ` Giacomo Tesio
2018-02-12 23:49 ` Benjamin Huntsman
2018-02-14 13:17 ` Ethan Grammatikidis
2018-02-14 13:57 ` Erik Quanstrom
2018-02-12 23:48 sl
2018-02-13 3:06 ` Lucio De Re
2018-02-13 9:31 ` Rui Carmo
2018-02-13 10:43 ` Lucio De Re
2018-02-13 11:05 ` hiro
2018-02-13 11:07 ` hiro
2018-02-13 11:13 ` hiro
2018-02-13 13:45 ` Lucio De Re
2018-02-13 14:35 ` hiro
2018-02-13 16:09 ` Lucio De Re
2018-02-13 15:10 ` Rui Carmo
2018-02-13 15:22 ` Lucio De Re
2018-02-13 16:25 ` Kurt H Maier
2018-02-13 17:01 ` Rui Carmo
2018-02-13 18:12 ` Kurt H Maier
2018-02-13 18:21 ` Rui Carmo
2018-02-13 19:10 ` Kurt H Maier
2018-02-13 23:37 ` Rui Carmo
2018-02-14 9:09 ` Steve Simon
2018-02-14 11:10 ` Lucio De Re
2018-02-14 11:32 ` hiro
2018-02-14 13:53 ` Ethan Grammatikidis
2018-02-13 19:14 ` hiro
2018-02-13 18:16 ` Steve Simon
2018-02-13 18:46 ` Bakul Shah
2018-02-13 14:15 sl
2018-02-14 0:31 sl
2018-02-14 7:18 ` Rui Carmo
2018-02-14 14:37 sl
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=MWHPR03MB2573919DE3059389155DA3B5E4F70@MWHPR03MB2573.namprd03.prod.outlook.com \
--to=bhuntsman@mail2.cu-portland.edu \
--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).