mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Rodland <arodland@noln.com>
Cc: Yann Dirson <ydirson@altern.org>,
	linux-kernel@vger.kernel.org, kaos@ocs.com.au
Subject: Re: Dual BSD/GPL [ was: Re: Generic modules documentation is outdated]
Date: 22 Jul 2002 13:25:45 +0100	[thread overview]
Message-ID: <1027340745.31782.1.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20020723025639.1baf8c1b.arodland@noln.com>

On Tue, 2002-07-23 at 07:56, Andrew Rodland wrote:
> 
> 	* According to Alan Cox, a license of "BSD without advertisement
> 	clause" is not a suitable free software license. This license type
> 	allows binary only modules without source code. Any modules in the
> 	kernel tarball with this license should really be "Dual BSD/GPL".

The problem with just the BSD tag is that means it might be binary only
so undebuggable. If its dual BSD/GPL then at the least the user can
demand their GPL rights and get the source to debug it

I think all these are now sorted


  reply	other threads:[~2002-07-22 11:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-04 21:22 oops with 2.4.18 and preempt patch, on SMP + ext3 machine Yann Dirson
2002-07-18 21:02 ` Generic modules documentation is outdated Yann Dirson
2002-07-18 22:48   ` Alan Cox
2002-07-18 23:17     ` Yann Dirson
2002-07-18 23:25     ` Yann Dirson
2002-07-18 23:04       ` Richard B. Johnson
2002-07-19  8:12       ` Stelian Pop
2002-07-23  6:56       ` Dual BSD/GPL [ was: Re: Generic modules documentation is outdated] Andrew Rodland
2002-07-22 12:25         ` Alan Cox [this message]
2002-07-19  8:24   ` Generic modules documentation is outdated Stelian Pop

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=1027340745.31782.1.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=arodland@noln.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ydirson@altern.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®