Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263195AbTEOAAz (ORCPT ); Wed, 14 May 2003 20:00:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263200AbTEOAAz (ORCPT ); Wed, 14 May 2003 20:00:55 -0400 Received: from vladimir.pegasys.ws ([64.220.160.58]:42250 "HELO vladimir.pegasys.ws") by vger.kernel.org with SMTP id S263195AbTEOAAc (ORCPT ); Wed, 14 May 2003 20:00:32 -0400 Date: Wed, 14 May 2003 17:11:08 -0700 From: jw schultz To: linux-kernel@vger.kernel.org Subject: Re: What exactly does "supports Linux" mean? Message-ID: <20030515001108.GC2009@pegasys.ws> Mail-Followup-To: jw schultz , linux-kernel@vger.kernel.org References: <200305131114_MC3-1-38B0-3C13@compuserve.com> <20030514021210.GD30766@pegasys.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2717 Lines: 73 On Wed, May 14, 2003 at 02:11:10PM +0000, Henning P. Schmiedehausen wrote: > jw schultz 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. > I left out versioning because i don't see that as belonging on the front of the box. That falls under "system requirements" with a URL for downloading up-to-date drivers. Hardware that has a driver in, or for, the mainline development tree but not the stable tree should probably not qualify or should have another another category or a category modifier. > As there is no real body to enforce misuse of these labels, they're > moot. I'd suggest Linux International. I think Linus has assigned trademark enforcement to them. With decent guidelines most manufacturers would be only to glad to comply. Some might even be willing to pony up $$ for certification or the right to use some copyrighted logo. Those who play fast-and-loose will generally fall in line if asked to do so. Witness the effectiveness of the EFF in defending the GPL. The resistant would face public criticism for false labelling (possible criminal fraud charges?) and the potential of a trademark infringement suit. The categories i suggest don't really leave anyone out. Even if you make a piece of crap hardware with a binary only driver that only supports one kernel version as long as you hide which version in the "system requirements" (where we all look first) you can claim "runs on Linux". -- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws Remember Cernan and Schmitt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/