From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] There is no fork
Date: Sat, 10 Feb 2018 14:54:42 +0000 [thread overview]
Message-ID: <1518274482.2841788.1266291784.26FDC62C@webmail.messagingengine.com> (raw)
In-Reply-To: <CAFSF3XO8RS0PvXh-_FoyT-cXcP5jN0oWEP12hFKbXd2WBidX+g@mail.gmail.com>
So we're all putting it here? Okay then. I agree with pretty-much
everything hiro said this time.
Regarding differences between forks, what springs to my mind is the
fixes 9front needed to host cat-v.org. The site was switched to a
9front server at the time of Uriel's death, news of which triggered a
huge traffic increase for a while. It was evident that no-one had put
Plan 9 under that kind of load before, or if they had, they hadn't
released their fixes. I remember someone saying, "Everyone who used
Plan 9 seriously must have maintained their own fork."
Hosting cat-v.org may be unusual load. Web server and CMS are both a
lot of shell scripts, so there is a lot of pipes and new processes all
the time. 9front has received more fixes relating to hosting it over
the years.
There was also a change to factotum to prevent it deadlocking the
filesystem. I don't remember what triggered that bug!
Plenty of other stuff, but I'm out of time to write (for once). I
have no idea if any other forks picked up any of the changes, although
I'm sure 9atom has its own fixes particularly related to NAS work.
next prev parent reply other threads:[~2018-02-10 14:54 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 [this message]
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
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=1518274482.2841788.1266291784.26FDC62C@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--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).