All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Tainting kernels for non-GPL or forced modules
Date: Sat, 22 Sep 2001 23:15:29 +1000	[thread overview]
Message-ID: <27975.1001164529@ocs3.intra.ocs.com.au> (raw)

I have started work on the patch for /proc/sys/kernel/tainted with the
corresponding modutils and ksymoops changes.  insmod of a non-GPL
module ORs /proc/sys/kernel/tainted with 1, insmod -f ORs with 2.

What to do about modules with no license?  Complain and taint or
silently ignore?  A lot of modules in -ac14 have no MODULE_LICENSE,
probably because they have no MODULE_AUTHOR.  IMHO the default should
be complain and taint, even though it will generate lots of newbie
questions to l-k.


             reply	other threads:[~2001-09-22 13:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-22 13:15 Keith Owens [this message]
2001-09-22 13:33 ` Tainting kernels for non-GPL or forced modules André Dahlqvist
2001-09-22 16:00   ` Tom Rini
2001-09-22 16:05 ` Alan Cox
2001-09-23  1:56   ` Keith Owens
2001-09-22 20:28 ` Albert D. Cahalan
2001-09-23  1:48   ` Keith Owens
2001-09-24 18:00 ` Timur Tabi
2001-09-24 18:10   ` John Levon
2001-09-24 22:48   ` Keith Owens
2001-09-24 23:31   ` 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=27975.1001164529@ocs3.intra.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.