From: Yasuaki Kudo <yasu@yasuaki.com>
To: andrew <andrew@andrewyu.org>
Cc: libreplanet-discuss <libreplanet-discuss@libreplanet.org>
Subject: Re: Question of Aiding and Abetting Proprietary (or non-free) Software in GNU projects
Date: Mon, 16 May 2022 20:55:44 +0900 [thread overview]
Message-ID: <6639F1F9-C9B3-4A43-BCB8-2F43D35C1F1F@yasuaki.com> (raw)
In-Reply-To: <20220516110816.mwzcuonij7jpkz4a@gentoo-dell>
Now I think it is becoming clear that the main point of my question is indeed this seeming contradiction:
>> * Emacs runs on Windows. Instructions and reasons are stated clearly
>> (as you quoted)
>
> Which I am indeed questioning why it is handled by GNU, too.
>
>> * Guix OS technically runs on normal, unqualified Linux Kernel (not just Linux-Libre). However,
>> it is not "advertised" (the verb seemingly preferred by the community)
>> and even the discussion thereof is shunned.
-Yasu
PS1
Thank you for technical corrections. 😄 (To move away from Linux-Libre, all that's needed [as you mentioned, nonguix, for example] is a config change though - I know it because I practice it myself)
PS2
Regarding the technical wording of what is Linux, I have seen so many people going into various details of what it means But I still think, albeit without much understanding of the technicalities, the basic fact of the matter is:
- Linux-Libre exists so that unaccountable (meaning no source code, not Free Software) binary drivers are removed
- Linux, as opposed to above, does include (although there might be further technical delineations of how driver files are packaged and given names) the Blob drivers
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2022-05-16 12:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 2:25 Question of Aiding and Abetting Proprietary (or non-free) Software in GNU projects Yasuaki Kudo
2022-05-15 17:11 ` andrew via libreplanet-discuss
2022-05-16 9:10 ` Yasuaki Kudo
2022-05-16 11:08 ` andrew via libreplanet-discuss
2022-05-16 11:55 ` Yasuaki Kudo [this message]
2022-05-17 6:51 ` Jean Louis
2022-05-17 6:57 ` andrew via libreplanet-discuss
2022-05-17 8:12 ` Yasuaki Kudo
2022-05-17 8:48 ` andrew via libreplanet-discuss
2022-05-17 13:35 ` Jean Louis
2022-05-17 14:02 ` Yasuaki Kudo
2022-05-18 3:12 ` Alexandre Oliva
2022-05-17 6:39 ` Jean Louis
[not found] <mailman.83.1652716864.26523.libreplanet-discuss@libreplanet.org>
2022-05-16 17:49 ` lkcl
2022-05-17 0:59 ` Yasuaki Kudo
2022-05-17 9:53 ` lkcl
2022-05-17 10:38 ` Yasuaki Kudo
2022-05-17 12:05 ` lkcl
2022-05-17 12:51 ` Yasuaki Kudo
2022-05-17 13:48 ` lkcl
2022-05-17 14:17 ` Yasuaki Kudo
2022-05-17 14:40 ` Greg Farough
2022-05-17 15:38 ` Andrew Yu via libreplanet-discuss
2022-05-18 0:55 ` Yasuaki Kudo
2022-05-17 17:14 ` Jean Louis
2022-05-17 13:48 ` Jean Louis
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
List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6639F1F9-C9B3-4A43-BCB8-2F43D35C1F1F@yasuaki.com \
--to=yasu@yasuaki.com \
--cc=andrew@andrewyu.org \
--cc=libreplanet-discuss@libreplanet.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).