The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Vito Caputo <vcaputo@pengaru.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [QUESTION] Microsoft, WSL, and the Linux trademark
Date: Wed, 7 Nov 2018 21:36:07 -0500	[thread overview]
Message-ID: <20181108023607.GA22459@thunk.org> (raw)
In-Reply-To: <20181108010608.mlcjfwwsdwt2nee5@shells.gnugeneration.com>

On Wed, Nov 07, 2018 at 05:06:08PM -0800, Vito Caputo wrote:
> In reading the news today, I stumbled across an article talking about a
> $20 "linux-based distro" app for Windows 10.
> 
> This is just a bundled userspace for WSL, there is no actual Linux in
> this thing, yet the trademarked Linux name is used throughout.
> 
> Did Microsoft license the trademark or something?  Did I miss a memo?
> Does their joining the Linux Foundation as a Platinum member two years
> ago include such use of the trademark?
> 
> I'm confused by what seems to be total silence about what _appears_ to
> be an obvious large-scale trademark abuse in everything WSL-related.
> 
> Could somebody informed please shed some light on this?

For information about for the Linux Trademark, please see:

	https://www.linuxmark.org/

I'll note that while Microsoft's Subsystem for Linux does not
*contain* Linux, it certainly can run Linux binaries.  WSL is not
unique in that regard.  Google's gVisor, which is used[1] in Google
Compute Engine's App Engine is implemented in Go and is a Userspace
Kernel, that can also run Linux binaries.

[1] https://cloud.google.com/blog/products/gcp/introducing-app-engine-second-generation-runtimes-and-python-3-7

I can't speak to whether Microsoft registered and received a
sublicense for WSL, or not.  Per the FAQ[2] on the Linux Mark
Institute's web site, it would appear that anyone who wants to use
Linux in a product name, whether it's "Red Hat Enterprise Linux" or
"SuSE Linux Enterprise Server" must request a free sublicense and
agree to the terms of the Sublicense Agreement[3].  Technically,
"Windows Subsystem for Linux" is not product name, but a feature.  I'm
not a trademark lawyer, so I can't speak to whether this would be
required or whether it would fall under Fair Use of a trademark.  For
certain, it would appear to me that "WLinux", Microsoft's distribution
derived from Debian, would be much like "Red Hat Enterprise Linux" as
requiring a trademark sublicense.

If you have further questions that are not answered by the FAQ, the
web site directs people to send inquiries to
trademarks@linuxfoundation.org.

[2] https://www.linuxmark.org/programs/legal/trademark/faq
[3] https://www.linuxmark.org/programs/legal/trademark/sublicense-agreement

Cheers,

						- Ted

  reply	other threads:[~2018-11-08  2:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08  1:06 [QUESTION] Microsoft, WSL, and the Linux trademark Vito Caputo
2018-11-08  2:36 ` Theodore Y. Ts'o [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-11-08  4:39 Hayden Barnes

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=20181108023607.GA22459@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vcaputo@pengaru.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