From: "Kurt H Maier via 9fans" <9fans@9fans.net>
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 12:48:38 -0800 [thread overview]
Message-ID: <Yecnpp4ATgLvEiL6@wopr> (raw)
In-Reply-To: <16425320420.dadC34A.505987@composer.9fans.topicbox.com>
On Tue, Jan 18, 2022 at 01:54:02PM -0500, Antonio Barrones wrote:
> 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.
Please keep FSF FUD off this list. Alpine is a Linux distro and doesn't
rely on GNU. There are, and always have been, several such. Copyright
cultists riding on coattails notwithstanding, there isn't much point in
belaboring such terminology, since Plan 9 is not typically distributed
in modular packages, but as an integrated system, and GNU cruft doesn't
readily build on it anyway.
khm
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T395156d4f2b00cde-M7ec276e4c284c40496449d0e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-01-18 20:49 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 [this message]
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=Yecnpp4ATgLvEiL6@wopr \
--to=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).