9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Despite being called a fork, is 9front similar to how Linux distros work?
Date: Tue, 18 Jan 2022 01:33:12 +0100	[thread overview]
Message-ID: <CAFSF3XNXNVVaCkfFUOjqW_4itXCCDAcKhU5jvXXBbRCh1W+cPA@mail.gmail.com> (raw)
In-Reply-To: <16424657580.fe246AE3F.762336@composer.9fans.topicbox.com>

if there's any branch of plan9 missing in 9front please just send the
patch or a reminder.

On 1/18/22, Matt <matthpmoreira@gmail.com> wrote:
>
> On Monday, January 17, 2022, at 8:36 PM, Sigrid Solveig Haflínudóttir
> wrote:
>> I'm afraid you got it wrong. Community is mostly centered around
> 9front. One of the reasons is that it actually works and is still
> being developed and used by many. Plan 9 is dead, 9front lives on.
> There is also software developed outside of 9front git repo, by people
> who use 9front: http://only9fans.com Whether some "secret community" decides
> to "accept" (or not) 9front as
> "official" doesn't matter.
> I see. Now that I look at it, 9fans its more similar to 9front than Plan 9
> indeed. My confusion arose from the description being "Fans of the OS Plan 9
> from Bell Labs". Besides that, the subreddit is r/plan9, and people seem to
> talk more often about Plan 9 itself than 9front. Thanks for clearing it up.
>
> On Monday, January 17, 2022, at 9:21 PM, Thaddeus Woskowiak wrote:
>> 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.
> That's really great. I'm also interested and quite enthusiastic about
> working with 9front. Although, I'd have more chances of winning a
> competition for the worst developer... Thanks for your help.

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T395156d4f2b00cde-Ma28c3e32d3b18dd271e6d989
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2022-01-18  0:33 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 [this message]
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

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=CAFSF3XNXNVVaCkfFUOjqW_4itXCCDAcKhU5jvXXBbRCh1W+cPA@mail.gmail.com \
    --to=23hiro@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).