public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "M. R. Brown" <mrbrown@0xd6.org>
To: pierre@lineo.com
Cc: arjanv@redhat.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: GPLONLY kernel symbols???
Date: Thu, 18 Oct 2001 08:45:59 -0500	[thread overview]
Message-ID: <20011018084559.H22296@0xd6.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10110171126480.5821-100000@innerfire.net> <3BCDE77F.D1B164A@lineo.com> <200110171934.f9HJY8w01260@adsl-209-76-109-63.dsl.snfc21.pacbell.net> <3BCDF89C.32916516@lineo.com> <3BCDEAD9.DEC2415F@redhat.com> <3BCDFFE8.3DDB2591@lineo.com>
In-Reply-To: <3BCDFFE8.3DDB2591@lineo.com>

[-- Attachment #1: Type: text/plain, Size: 2277 bytes --]

* pierre@lineo.com <pierre@lineo.com> on Wed, Oct 17, 2001:

> > 
> > It's not legal issues.
> 
> Of course it is, this is code that deals with
> whether or not the kernel has loaded something
> that's not covered under the GPL license.
> 

No, it isn't, the fact that a module is GPL'd or BSD'd means that the
source is available, which means that any available kernel hacker can debug
it.  Proprietary/binary-only modules won't have such a license, the source
isn't accessible, and can't be debugged by the general hacking community.

You've been reading waaaay too much into this.

> 
> Then that's the wrong purpose : instead, oops
> posters should be made aware that they should
> post the list of loaded modules as well. If you
> really insist on having the kernel deal with this,
> make the kernel print the list of modules as well
> as the oops.
> 

Obviously that's not enough if the tainted mechanism is needed to "dismiss"
those posts.  And how does printing the use of active modules help
determine which modules are supported and which aren't?  You'd still need
to label those modules as being proprietary and such, so you still end up
with the tainted mechanism.

> 
> Yes it is : what about the code that allows me
> to cat /proc/sys/kernel/tainted and echo an integer
> into it ? and the code that's not loaded into kernel
> memory sure takes storage space, even if it's not
> much.
> 

What the hell are you talking about?

> But that's not the point : the point is, the kernel
> should contain as much non-kernel junk as possible.
> Kernel code, even a small amount of it, that deals
> with licensing is junk code. It's silly enough to
> have "sponsored by" strings in the kernel as it is.
> 

Two things.  Bitching about code that you don't agree with without
providing a suitable alternative won't really get you anywhere.  The
tainted inteface is needed to sway or halt the onslaught of bug reports for
unsupported modules.  You do realize that the kernel community can't
support modules without source?  Also, it's up to the copyright holder of a
piece of code what strings are in their code, as long as it's accepted by
whomever who cares if it contains "I'd like to give a shout out...".

M. R.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2001-10-18 13:46 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-16 16:27 GPLONLY kernel symbols??? Christoph Lameter
2001-10-16 17:07 ` John Levon
2001-10-16 17:22   ` Alexander Viro
2001-10-17  2:17 ` Keith Owens
2001-10-17  4:59   ` Christoph Lameter
2001-10-17  5:54     ` Keith Owens
2001-10-17  6:15       ` Christoph Lameter
2001-10-17 18:28         ` Gerhard Mack
2001-10-17 19:34           ` Ben Greear
2001-10-17 20:18           ` pierre
2001-10-17 19:34             ` Wayne Whitney
2001-10-17 21:31               ` pierre
2001-10-17 20:32                 ` Arjan van de Ven
2001-10-17 19:14                   ` David Lang
2001-10-17 20:37                     ` Arjan van de Ven
2001-10-17 19:20                       ` David Lang
2001-10-17 22:02                   ` pierre
2001-10-18 13:45                     ` M. R. Brown [this message]
2001-10-21 16:05                     ` Alan Cox
2001-10-18 13:32                 ` M. R. Brown
2001-10-17 14:15   ` John Levon
2001-11-13  2:57     ` Richard Gooch
2001-11-13  3:21       ` Dave Jones
2001-11-13  3:24         ` Richard Gooch
2001-11-13  3:53           ` Alexander Viro
2001-11-13  3:58             ` Richard Gooch
2001-11-13  4:10               ` Alexander Viro
2001-11-13  4:21                 ` Richard Gooch
2001-11-13  4:36                   ` Alexander Viro
2001-11-13  4:49                     ` Richard Gooch
2001-11-13 10:46                   ` Martin Dalecki
2001-11-13  4:15               ` Jeff Garzik
2001-11-13  4:37                 ` Richard Gooch
2001-11-13  4:49                   ` Alexander Viro
2001-11-13  5:03                     ` Richard Gooch
2001-11-13  5:27                       ` Alexander Viro
2001-11-13  5:35                         ` Richard Gooch
2001-11-13  5:44                           ` Jeff Garzik
2001-11-13  4:54                   ` Jeff Garzik
2001-11-13  5:00                     ` Richard Gooch
2001-11-13  5:14                       ` Jeff Garzik
2001-11-13  5:23                         ` Richard Gooch
2001-11-13  5:29                           ` Robert Love
2001-11-13  5:44                           ` Erik Andersen
2001-11-13  5:56                             ` Richard Gooch
2001-11-13  4:58                   ` Davide Libenzi
2001-11-13  5:07                     ` John Alvord
2001-11-28 22:41                       ` Dr. Kelsey Hudson
2001-11-29  0:35                         ` Michael H. Warfield
2001-11-29  5:04                           ` Dr. Kelsey Hudson
2001-11-13 10:01                   ` Alan Cox
2001-11-13 10:29                     ` Jeff Garzik
2001-11-13 13:47                     ` Dave Jones
2001-11-13 16:54                       ` Alan Cox
2001-11-13 17:17                         ` Dave Jones
2001-11-15 10:03                       ` [PATCH] mtrr (was Re: GPLONLY kernel symbols???) Paul Gortmaker
2001-11-13 10:48                   ` GPLONLY kernel symbols??? Martin Dalecki
2001-11-13  9:57                 ` [OT] Coding Style (was: Re: GPLONLY kernel symbols???) Henning P. Schmiedehausen
2001-11-28 22:35                 ` GPLONLY kernel symbols??? Dr. Kelsey Hudson
2001-11-13  9:52               ` Roman Zippel
2001-11-13  4:05       ` Jeff Garzik

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=20011018084559.H22296@0xd6.org \
    --to=mrbrown@0xd6.org \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre@lineo.com \
    /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