public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: What exactly does "supports Linux" mean?
Date: Wed, 14 May 2003 14:11:10 +0000 (UTC)	[thread overview]
Message-ID: <b9tipu$e3m$4@tangens.hometree.net> (raw)
In-Reply-To: 20030514021210.GD30766@pegasys.ws

jw schultz <jw@pegasys.ws> writes:

>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:
>	Mainline kernel has driver and it has been certified
>	as functioning with this hardware by OSDL or some
>	other officially sanctioned lab.

>Linux supported:
>	Mainline kernel has driver.

>Linux compatible:
>	Source code driver available as a patch.

>Runs on Linux:
>	Binary only driver available that can be used with
>	mainline kernel.

>Supports Linux:
>	Portion of the purchase price will be donated to
>	Linux International.

As there is no real body to enforce misuse of these labels, they're
moot.

And you forgot:

Linus certified:
	Used by Linus Torvalds to develop new versions of Linux. :-)

	Regards
		Henning

-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
hps@intermeta.de        +49 9131 50 654 0   http://www.intermeta.de/

Java, perl, Solaris, Linux, xSP Consulting, Web Services 
freelance consultant -- Jakarta Turbine Development  -- hero for hire

  parent reply	other threads:[~2003-05-14 14:00 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
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 [this message]
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='b9tipu$e3m$4@tangens.hometree.net' \
    --to=hps@intermeta.de \
    --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