LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: andrew via libreplanet-discuss <libreplanet-discuss@libreplanet.org>
To: Yasuaki Kudo <yasu@yasuaki.com>
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 19:08:16 +0800	[thread overview]
Message-ID: <20220516110816.mwzcuonij7jpkz4a@gentoo-dell> (raw)
In-Reply-To: <8CCCC7D2-C2F6-417E-B55D-3BC9EAABD610@yasuaki.com>


[-- Attachment #1.1: Type: text/plain, Size: 2439 bytes --]

On 22/05/16 06:10PM, Yasuaki Kudo wrote:
> Oh this is quite simple - When someone installs a Guix OS, there is a
> high chance that vital components of the computer won't work (unless
> "work" includes severely hampered performance)
>
> And the chances are, all one needs to do to obtain the hardware
> manufacture's native performance is do is to use the regular Linux
> kernel package, with none the "de-blobbing" of LinuxLibre.  (Aside
> from asking the manufacturer to provide the Free Software-based
> compilation mechanism for the required BLOB, something that may take
> many years, or forever)

This is really the job of nonguix, and their mailing lists if any (I
don't personally use nonguix so I can't tell).

Note that "regular Linux" in theory doesn't contain nonfree software
either- the nonfree software has been moved to linux-firmware.

Do note that nonfree firmware or other nonfree code linked again Linux
or specifically designed to work with Linux is a violation of Linux's
license, GNU GPL version 2 (only).

> To use the regular Linux, all that's needed is to tweak the
> configuration of the Guix system.   When people new to the system post
> questions along this line, on the Guix Help mailing list, the typical
> response is either via a direct personal email or some suggestions,
> short of the direct answer.

No, it isn't, you'd also need linux-firmware as explained.

> When, out of frustration, one directly answers, he is greeted with
> notices around this being a GNU mailing list and such matters are not
> to be discussed.

I do believe that the GNU Guix mailing list should be oriented towards
the Guix system itself and not compatibility with nonfree hardware,
though that may be a goal of people introducing users so that they would
eventually fully free systems.  Nonguix is such a community.

> The contradiction I see is that:

> * 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 Linux (not just LibreLinux).   However,
> it is not "advertised" (the verb seemingly preferred by the community)
> and even the discussion thereof is shunned.

(1) it's called linux-libre
(2) no linux-firmware -> free

--
Andrew Yu
https://www.anrewyu.org/

Free Computing, not just Free Software! <https://fcm.andrewyu.org/>

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 184 bytes --]

_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss

  reply	other threads:[~2022-05-16 12:48 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 [this message]
2022-05-16 11:55       ` Yasuaki Kudo
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=20220516110816.mwzcuonij7jpkz4a@gentoo-dell \
    --to=libreplanet-discuss@libreplanet.org \
    --cc=andrew@andrewyu.org \
    --cc=yasu@yasuaki.com \
    /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).