Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264815AbUD2PLd (ORCPT ); Thu, 29 Apr 2004 11:11:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264849AbUD2PLc (ORCPT ); Thu, 29 Apr 2004 11:11:32 -0400 Received: from kinesis.swishmail.com ([209.10.110.86]:32006 "EHLO kinesis.swishmail.com") by vger.kernel.org with ESMTP id S264815AbUD2PKo (ORCPT ); Thu, 29 Apr 2004 11:10:44 -0400 Message-ID: <40911C01.80609@techsource.com> Date: Thu, 29 Apr 2004 11:15:13 -0400 From: Timothy Miller MIME-Version: 1.0 To: Rik van Riel CC: Marc Boucher , lkml - Kernel Mailing List , Rusty Russell , David Gibson Subject: Re: [PATCH] Blacklist binary-only modules lying about their license References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1129 Lines: 33 Rik van Riel wrote: > On Wed, 28 Apr 2004, Marc Boucher wrote: > > >>At the same time, I think that the "community" should, without >>relinquishing its principles, be less eager before getting the facts to >>attack people and companies trying to help in good faith, and be more >>realistic when it comes to satisfying practical needs of ordinary >>users. > > > I wouldn't be averse to changing the text the kernel prints > when loading a module with an incompatible license. If the > text "$MOD_FOO: module license '$BLAH' taints kernel." upsets > the users, it's easy enough to change it. > > How about the following? > > "Due to $MOD_FOO's license ($BLAH), the Linux kernel community > cannot resolve problems you may encounter. Please contact > $MODULE_VENDOR for support issues." Sounds very "politically correct", but certainly more descriptive and less alarming. - 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/