9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Matt <matthpmoreira@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 18:18:59 -0500	[thread overview]
Message-ID: <16424615390.0F13B68C3.21800@composer.9fans.topicbox.com> (raw)
In-Reply-To: <C2CF20C234D9A2285387F6286CEEFD33@eigenstate.org>

[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]

@Humm: I understand that Android isn't a fork of Linux, I meant to imply that although Android is argued to be a Linux distro, they have very different environments that can't easily interact with each other. I also know that the meaning of forking is objective, I meant that forking invokes the mentioned feelings in me, subjectively. I understand that Plan 9 is not being developed anymore, but the community seems to be centered around it rather than 9front. Therefore, I wondered if that's because 9front, despite being forked, intends to stay true to Plan 9, like Linux distros stay true to the Linux kernel despite small configurations, as you said, so that if other operational systems are forked from Plan 9, they are able to interoperate easily with 9front.

@ori: Those are examples of forked software that happened because of the discontinuation of the original software, right? At least most of them are. That's what 9front is to Plan 9, right? If so, thanks for the clarification.

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

[-- Attachment #2: Type: text/html, Size: 1802 bytes --]

  reply	other threads:[~2022-01-17 23:19 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 [this message]
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

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=16424615390.0F13B68C3.21800@composer.9fans.topicbox.com \
    --to=matthpmoreira@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).