From: "Riley Williams" <Riley@Williams.Name>
To: "jw schultz" <jw@pegasys.ws>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: What exactly does "supports Linux" mean?
Date: Wed, 14 May 2003 08:57:28 +0100 [thread overview]
Message-ID: <BKEGKPICNAKILKJKMHCAMEONCPAA.Riley@Williams.Name> (raw)
In-Reply-To: <20030514021210.GD30766@pegasys.ws>
Hi.
> This is really a trademark related labelling issue. The trademark
> allows Linus or his assignee to specify in what way Linux (tm) may
> be used in labelling and advertising. Linux is just like other
> products with third-party parts and supplies. If Linus's assignee
> (Linux international?) where to specify explicit guidelines then
> people would know what to expect. Something like:
>
> Linux certified:
> The mainline kernel has a driver and it has been certified
> as functioning with this hardware by OSDL or some other
> officially sanctioned lab.
>
> Linux supported:
> The mainline kernel has a driver.
Fine so far.
> Linux compatible:
> Source code driver is available as a patch.
In other words, if a patch is available for the 1.0.0 kernel, they
can claim "Linux compatible" ??? That's meaningless...replace with
something like...
Linux 2.2.2 compatible:
Source code driver is available as a patch for the stated
mainline kernel.
...with the specific version to be made explicit. As a minimum, it
needs to state the actual kernel series the patch is for.
> Runs on Linux:
> A binary only driver is available that can be used with
> mainline kernel.
Similar comments apply. Again, require that the kernel that driver
works with is made explicit.
> Supports Linux:
> A portion of the purchase price will be donated to
> Linux International.
So a company provides a product for $5,000.00 and donates $0.01 of
the purchase price to the specified organisation, thus entitling
themselves to say "Supports Linux" by this rule. Can I suggest
this alternative definition:
Supports Linux:
At least 1% of the purchase price will be donated to
Linux International.
> You will notice this all relates to mainline kernels (Linus and
> Marcello). If the product requires a vendor kernel they need to
> negotiate with the vendor to say so.
Agreed.
> These are just suggestions. Many other products (including MS
> windows) have similar labelling restrictions, often with logos.
> Use of the term "Linux" in packaging or advertising or products
> inconsistent with the official designations would be trademark
> infringement.
Agreed.
> Different rules would apply to products that exist strictly in
> user-space.
That's not necessary - just define:
Runs under Linux:
This product work on a system based on a mainline Linux
kernel without making any modification to the kernel
itself or loading any kernel modules.
That is all that is required there.
Best wishes from Riley.
---
* Nothing as pretty as a smile, nothing as ugly as a frown.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.481 / Virus Database: 277 - Release Date: 13-May-2003
next prev parent reply other threads:[~2003-05-14 7:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 15:12 What exactly does "supports Linux" mean? Chuck Ebbert
2003-05-13 20:36 ` Måns Rullgård
2003-05-14 2:12 ` jw schultz
2003-05-14 7:57 ` Riley Williams [this message]
2003-05-14 17:58 ` Måns Rullgård
2003-05-17 16:05 ` Pavel Machek
2003-05-18 1:39 ` jw schultz
2003-05-18 3:53 ` Werner Almesberger
2003-05-18 21:49 ` Pavel Machek
2003-05-18 22:20 ` Neale Banks
2003-05-19 10:20 ` Helge Hafting
2003-05-14 14:11 ` Henning P. Schmiedehausen
2003-05-14 15:29 ` Mike Dresser
2003-05-15 0:11 ` jw schultz
2003-05-14 14:09 ` Henning P. Schmiedehausen
2003-05-14 14:44 ` Dave Jones
2003-05-14 15:58 ` Henning Schmiedehausen
2003-05-14 16:14 ` Dave Jones
2003-05-14 19:40 ` David Schwartz
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 13:16 Stephan von Krawczynski
2003-05-13 12:53 ` Alan Cox
2003-05-13 14:24 ` Richard B. Johnson
2003-05-13 15:07 ` Lionel Bouton
2003-05-13 16:45 ` Jonathan Matthews
2003-05-13 13:46 ` Duncan Sands
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=BKEGKPICNAKILKJKMHCAMEONCPAA.Riley@Williams.Name \
--to=riley@williams.name \
--cc=jw@pegasys.ws \
--cc=linux-kernel@vger.kernel.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).