From: as <as.utf8@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] There is no fork
Date: Sat, 10 Feb 2018 12:03:45 +0000 [thread overview]
Message-ID: <CAL__Z5adHO72bp8uAVoZ4vYAtnhHjQidhD6Yd1RfNCTKQrbAJQ@mail.gmail.com> (raw)
In-Reply-To: <1518259893.2759231.1266170088.4F324D82@webmail.messagingengine.com>
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
Ive been using 9front as a primary system ever since the one true
distribution neutered bintime and replaced it with the nsec system call.
Its nice that the 9front maintainers voulenteer to keep plan9's simplicity
alive (9atom is great too and has myriad device drivers written for modern
hardware as well). Maintaining these systems is a lot more meritable of an
endeavor than inhaling the aeresol of the Linux cloud and contributing to
an ecosystem superceeded over 3 decades ago.
On Sat, Feb 10, 2018, 02:53 Ethan Grammatikidis <eekee57@fastmail.fm> wrote:
> eeh... I cut out a bunch of stuff from my last mail because I didn't want
> to derail the thread.
>
> Anyone want a new thread on discussing the differences, or shall we just
> bung it all here?
>
>
[-- Attachment #2: Type: text/html, Size: 1052 bytes --]
next prev parent reply other threads:[~2018-02-10 12:03 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 [this message]
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
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=CAL__Z5adHO72bp8uAVoZ4vYAtnhHjQidhD6Yd1RfNCTKQrbAJQ@mail.gmail.com \
--to=as.utf8@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).