kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: FMDF <fmdefrancesco@gmail.com>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Does Linux (Torvald's tree) infringe GPLv2 and contain proprietary binary blobs?
Date: Fri, 11 Mar 2022 09:14:35 -0500	[thread overview]
Message-ID: <20220311141435.geqwbrtzshlhmxe6@meerkat.local> (raw)
In-Reply-To: <CAPj211t_d1u4DYYv19B5FajhAVjTkwP1bkYfAq8HJcD5nVM5Gw@mail.gmail.com>

On Fri, Mar 11, 2022 at 03:48:37AM +0100, FMDF wrote:
> Unfortunately, there have been several attempts to state that Linux is
> _not_ a free and open source kernel and that it contains proprietary binary
> blobs.
> 
> I'm asking for help to remove those fake information, mainly sponsored and
> backed by the FSF and by the Linux libre project (or something like that).
> 
> Can someone please provide reliable sources that I can use when reverting
> the above-mentioned false information? Unfortunately, I cannot simply
> revert them by just saying that the Linux Community won't ever accept non
> GPLv2 complaint code.
> 
> There is a strict rule that says "No original research": mostly everything
> must be supported by links to third party reliable documentation (web,
> books, and so on).
> 
> Again, can someone please help?

I doubt anyone really cares about the purity of wikipedia articles here. The
best I can link you to is this FAQ entry:

https://www.kernel.org/faq.html#i-heard-that-linux-ships-with-non-free-blobs

-K

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  parent reply	other threads:[~2022-03-11 14:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11  2:48 Does Linux (Torvald's tree) infringe GPLv2 and contain proprietary binary blobs? FMDF
2022-03-11  3:09 ` FMDF
2022-03-11 14:14 ` Konstantin Ryabitsev [this message]
2022-03-11 14:24 ` Robert Joslyn

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=20220311141435.geqwbrtzshlhmxe6@meerkat.local \
    --to=konstantin@linuxfoundation.org \
    --cc=fmdefrancesco@gmail.com \
    --cc=kernelnewbies@kernelnewbies.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 NNTP newsgroup(s).