From: Humm <hummsmith42@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 19:55:05 +0000 [thread overview]
Message-ID: <YecbGZ/mDiSvo2bn@beryllium.local> (raw)
In-Reply-To: <16425320420.dadC34A.505987@composer.9fans.topicbox.com>
Quoth Antonio Barrones:
>Linux distros are not only "Linux", they are GNU/Linux. Linux is only
>the kernel of a GNU/Linux system (a distro). Android is not a distro
>because they don't have GNU, but Android is "Linux" because it has
>Linux as kernel.
Linux distros are not only Linux, they are whatever other software they
consist of and Linux. Some of that might be developed under the
umbrella of the GNU project, much of it likely isn’t. The term
“GNU/Linux” is garbage.
Android is yet another operating system using Linux. It seldom getting
called “Linux distro” stems from it being used very differently (Java
hell) and perhaps from how hard it is to see its Unix-like-ness. That
has nothing to do with how much of it is part of the GNU project.
>It is not developed anymore in Bell Labs, but many of the original
>developers are part of the Plan9 Foundation and they are promoting it
>in different ways: https://plan9foundation.org/activities.html So
>I would not say that it "is not being developed anymore".
Patches for Plan 9 exist. Forks exist. Yet, Plan 9 stays the exact
same. Plan 9 with patches is Plan 9 with patches. 9front is 9front.
Plan 9 has a modification timestamp of 2015.
From the little I see, the Plan 9 Foundation changes little there.
Plan 9, with a timestamp of 2015, now is licensed under an Expat
license. And retains its timestamp.
So no, Plan 9 is not being developed anymore.
--
Humm
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T395156d4f2b00cde-M9431455edbac7b86ac06556e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-01-18 19:55 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 [this message]
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=YecbGZ/mDiSvo2bn@beryllium.local \
--to=hummsmith42@gmail.com \
--cc=9fans@9fans.net \
--subject='Re: [9fans] Despite being called a fork, is 9front similar to how Linux distros work?' \
/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
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).