mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul Rolland" <rol@as2917.net>
To: "'Sean Estabrooks'" <seanlkml@rogers.com>,
	"'Marc Boucher'" <marc@linuxant.com>
Cc: <torvalds@osdl.org>, <rusty@rustcorp.com.au>,
	<linux-kernel@vger.kernel.org>, <riel@redhat.com>,
	<tconnors+linuxkernel1083378452@astro.swin.edu.au>,
	<mbligh@aracnet.com>, <nico@cam.org>
Subject: Re: [PATCH] clarify message and give support contact for non-GPL modules
Date: Sun, 2 May 2004 15:05:12 +0200	[thread overview]
Message-ID: <200405021305.i42D5L625036@tag.witbe.net> (raw)
In-Reply-To: <20040502084345.4b89d35f.seanlkml@rogers.com>

Hello,

I'm definitely no native English speaker, but I wanted to give my pov
on this topic...

> > Understood. So perhaps we should call it "open" and 
> "proprietary" which 
> > are clear, well known words. "tainted" is honestly 
> confusing/hard to 
> > understand for many ordinary users, especially 
> international/non-native 
> > speakers who do not encounter the word that often (thankfully ;-).
> 
> No.  It's tainted.  And hopefully if the user is concerned or 

Agreed. Once you have loaded such a module, your kernel is really
"tainted" by something that cannot really be controlled.
Proprietary is too much neutral and doesn't reflect what you are
now running : some piece of code which may by bloated without anyone
being able to control it.

> Linux is an open source operating system.  There is nothing wrong with
> promoting and protecting the code and license.
Correct.
 
> I've been looking at the latest version of the patch and 
> thinking that it is really
> wrong for any message to be displayed only once.   If the 
> user is unfortunate 
> enough to be loading two or more closed-source modules, the second
> module should not be hidden by the first.   The author of the 
> second module
> should not have their name hidden just because another module 
> was loaded first.

Agreed too.

This patch should make its way in the kernel, so that people are
aware they are using closed-source code.

I simply hope that some "vendors" will not alter kernel code before
building to remove such a warning if they include closed source
module in their distro.

Regards,
Paul

Paul Rolland, rol(at)as2917.net
ex-AS2917 Network administrator and Peering Coordinator

--

Please no HTML, I'm not a browser - Pas d'HTML, je ne suis pas un navigateur

"Some people dream of success... while others wake up and work hard at it" 



  reply	other threads:[~2004-05-02 13:05 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <009701c42edf$25e47390$ca41cb3f@amer.cisco.com>
2004-04-30 19:19 ` [PATCH] Blacklist binary-only modules lying about their license Linus Torvalds
2004-04-30 19:37   ` Hua Zhong
2004-04-30 22:47     ` Allowing only "-g" compiled modules! (was: [PATCH] Blacklist binary-only modules lying about their license) Jan-Benedict Glaw
2004-04-30 20:11   ` [PATCH] Blacklist binary-only modules lying about their license Marc Boucher
2004-04-30 20:26     ` Linus Torvalds
2004-04-30 20:39       ` Marc Boucher
2004-04-30 20:44         ` Linus Torvalds
2004-04-30 20:53           ` Marc Boucher
2004-04-30 21:05             ` Linus Torvalds
2004-04-30 21:10             ` Timothy Miller
2004-04-30 20:46         ` Sean Estabrooks
2004-04-30 20:34     ` Stefan Smietanowski
2004-04-30 20:47     ` A compromise that could have been reached. " Timothy Miller
2004-04-30 21:07       ` Marc Boucher
2004-04-30 21:16         ` Rik van Riel
2004-04-30 21:38         ` Timothy Miller
2004-04-30 22:05           ` Marc Boucher
2004-05-01  2:36           ` Tim Connors
2004-05-01  0:40     ` Jorge Bernal
2004-05-01  5:07     ` Martin J. Bligh
2004-05-01 19:12       ` Marc Boucher
2004-05-01 19:27         ` Davide Libenzi
2004-05-01 19:32         ` Zwane Mwaikambo
2004-05-01 19:33         ` Sean Estabrooks
2004-05-01 22:14           ` Randy.Dunlap
2004-05-01 19:47         ` Nicolas Pitre
2004-05-01 20:53           ` [PATCH] clarify message and give support contact for non-GPL modules Marc Boucher
2004-05-01 21:34             ` Sean Estabrooks
2004-05-01 21:48               ` Marc Boucher
2004-05-01 21:53                 ` Sean Estabrooks
2004-05-01 22:22                 ` Sean Estabrooks
2004-05-01 22:53                   ` Marc Boucher
2004-05-01 23:10                     ` viro
2004-05-02  7:04                       ` Xavier Bestel
2004-05-04 17:06                       ` Timothy Miller
2004-05-01 22:48                 ` Linus Torvalds
2004-05-01 23:28                   ` Marc Boucher
2004-05-02  0:22                     ` Linus Torvalds
2004-05-02  1:02                       ` Marc Boucher
2004-05-02 12:43                         ` Sean Estabrooks
2004-05-02 13:05                           ` Paul Rolland [this message]
2004-05-02 15:35                             ` Marc Boucher
2004-05-02 15:45                               ` Sean Estabrooks
2004-05-04 17:09                     ` Timothy Miller
2004-05-01 20:47         ` [PATCH] Blacklist binary-only modules lying about their license Martin J. Bligh
2004-05-01 20:58           ` Marc Boucher
2004-05-03  0:04         ` Horst von Brand
     [not found] ` <40929F5B.9090603@techsource.com>
2004-04-30 18:58   ` Hua Zhong
2004-04-30 20:14   ` Bartlomiej Zolnierkiewicz

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=200405021305.i42D5L625036@tag.witbe.net \
    --to=rol@as2917.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc@linuxant.com \
    --cc=mbligh@aracnet.com \
    --cc=nico@cam.org \
    --cc=riel@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=seanlkml@rogers.com \
    --cc=tconnors+linuxkernel1083378452@astro.swin.edu.au \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®