From: Thaddeus Woskowiak <tswoskowiak@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Despite being called a fork, is 9front similar to how Linux distros work?
Date: Mon, 17 Jan 2022 19:20:54 -0500 [thread overview]
Message-ID: <CAG3JMtaZim3HLFg9+jV9Ya_E7ZDC=GXmMrbU7XTshTXz7105Wg@mail.gmail.com> (raw)
In-Reply-To: <16424622620.b9EedC5.684450@composer.9fans.topicbox.com>
On Mon, Jan 17, 2022 at 6:32 PM Matt <matthpmoreira@gmail.com> wrote:
>
> But that's why 9front was forked, right? They say it on their FAQ. Even though Plan 9 isn't being developed anymore, doesn't the fork cause worry that one day they become too different, especially since the community is rather centered around Plan 9 rather than 9front? Or is the community actively trying to make 9front be accepted as the official continuation of Plan 9?
> 9fans / 9fans / see discussions + participants + delivery options Permalink
All wrong. From my perspective 9front is plan 9 from the future
compared to today's plan 9. 9front development moves at a much faster
pace thanks to adopting tools like mercurial in the past and now git.
That enables devs who are passionate about moving plan 9 forward
commit access using tools they, and most of today's developers are
already intimate with. It has virtualization, modern encryption,
cleaned up pci code, rc fixes, boot clean up, and so much more.
The mailing list is very active and crawling with devs eager to review
and apply fixes. It has a lot of enthusiastic energy behind it and
keeps the core philosophy of plan 9 alive. This has attracted many
wonderful and talented devs who would have otherwise stumbled with the
old defaults of legacy.
Personally, I struggled with plan 9 until finding 9front. I run a CPU
server at home 24/7 and it's been running reliably for years. I then
netboot or tcp boot everything else. I love working with this
operating system.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T395156d4f2b00cde-M25c8857f931ef72ce276287f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
prev parent reply other threads:[~2022-01-18 0:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 22:04 matthpmoreira
2022-01-17 22:41 ` Humm
2022-01-17 23:04 ` ori
2022-01-17 23:18 ` Matt
2022-01-17 23:22 ` ori
2022-01-17 23:31 ` Matt
2022-01-17 23:36 ` Sigrid Solveig Haflínudóttir
2022-01-18 0:29 ` Matt
2022-01-18 0:33 ` hiro
2022-01-18 16:22 ` Humm
2022-01-18 18:54 ` Antonio Barrones
2022-01-18 19:55 ` Humm
2022-01-18 20:48 ` Kurt H Maier via 9fans
2022-01-18 22:16 ` vic.thacker
2022-01-18 22:59 ` Duke Normandin
2022-01-18 0:47 ` Kurt H Maier via 9fans
2022-01-18 4:38 ` Andrew Back
2022-01-18 0:20 ` Thaddeus Woskowiak [this message]
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='CAG3JMtaZim3HLFg9+jV9Ya_E7ZDC=GXmMrbU7XTshTXz7105Wg@mail.gmail.com' \
--to=tswoskowiak@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).