public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "Alan Shutko" <ats@acm.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Linux 2.4.9-ac6
Date: Wed, 5 Sep 2001 11:46:11 -0700	[thread overview]
Message-ID: <NOEJJDACGOHCKNCOGFOMMEFEDLAA.davids@webmaster.com> (raw)
In-Reply-To: <87zo8atcvz.fsf@wesley.springies.com>


> "David Schwartz" <davids@webmaster.com> writes:

> > Yes, but even if the module is GPL'd, the module could still cost
> > $1,000 and you're not entitled to the source if you didn't buy the
> > module.

> OTOH, if you're getting a bug report from someone who has a GPLed
> module, they can get the source and send it to you.

	Perhaps, but:

	1) They may not have it or know the procedure to get it.

	2) The offer for the source may have expired.

	3) This is true whether or not the module is GPLed, they may have the
source or they may not.

	4) Many other licenses may result in publically available source and may
not, just like the GPL.

	If you want to make sure the user has the source from which the module was
built, that can be checked for. (Though it's not simple, unfortunately.)

	What you want to do is make sure the user understands that he had better be
able to produce the source for any kernel modules loaded at the time of the
problem. If not, he needs to reproduce the bug on a system without the
relevant modules.

	I think a tag for 'source code is available to anyone for debugging
purposes, no questions asked' is more what's wanted.

	DS


  reply	other threads:[~2001-09-05 18:46 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-03  1:50 Linux 2.4.9-ac6 Alan Cox
2001-09-03  2:51 ` Keith Owens
2001-09-03  3:08   ` Dave Jones
2001-09-03 13:05 ` Andrea Arcangeli
2001-09-03 13:21   ` Alan Cox
2001-09-05  1:51   ` Keith Owens
2001-09-05  3:30     ` David Schwartz
2001-09-05  3:50       ` Keith Owens
2001-09-05  5:16         ` David Schwartz
2001-09-05  5:39           ` Alan Shutko
2001-09-05 18:46             ` David Schwartz [this message]
2001-09-05  5:52           ` H. Peter Anvin
2001-09-05  5:56           ` Aaron Lehmann
2001-09-05  7:03             ` David Schwartz
2001-09-05  7:09               ` David Schwartz
2001-09-05  9:50                 ` Alex Bligh - linux-kernel
2001-09-05  9:57                   ` David Schwartz
2001-09-05 12:50                     ` christophe barbé
2001-09-05 13:06                       ` Alan Cox
2001-09-05 13:14                       ` Alex Bligh - linux-kernel
2001-09-05 13:23                         ` christophe barbé
2001-09-05 14:05                       ` Henning P. Schmiedehausen
2001-09-05  7:18               ` Aaron Lehmann
2001-09-05  7:19                 ` David Schwartz
2001-09-05  9:41               ` Justin Guyett
2001-09-05  9:53                 ` David Schwartz
2001-09-05 10:21                   ` Justin Guyett
2001-09-05 11:55                   ` Alan Cox
2001-09-05 18:46                     ` David Schwartz
2001-09-05 18:54                       ` Alan Cox
2001-09-05 22:09                       ` Linux 2.4.9-ac6 (really about tainting) David Schwartz
2001-09-05 12:07       ` Linux 2.4.9-ac6 Alan Cox
2001-09-05 12:16         ` Arjan van de Ven
2001-09-05 12:23           ` Jan-Benedict Glaw
  -- strict thread matches above, loose matches on Subject: below --
2001-09-05 14:36 Thomas Foerster
2001-09-06 19:23 ` Camiel Vanderhoeven
2001-09-06 20:14   ` Alan Cox

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=NOEJJDACGOHCKNCOGFOMMEFEDLAA.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=ats@acm.org \
    --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