public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@timpanogas.org>
To: "Keith Owens" <kaos@ocs.com.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [RFC-ONT (on topic)] Modprobe enhancement (was Re: "Dance of the Trolls")
Date: Sun, 11 Nov 2001 20:57:02 -0700	[thread overview]
Message-ID: <001b01c16b2e$164cbcc0$f5976dcf@nwfs> (raw)
In-Reply-To: <32224.1005531575@kao2.melbourne.sgi.com>

Sounds like it's already there.

Jeff
----- Original Message -----
From: "Keith Owens" <kaos@ocs.com.au>
To: "Jeff V. Merkey" <jmerkey@timpanogas.org>
Cc: <linux-kernel@vger.kernel.org>
Sent: Sunday, November 11, 2001 7:19 PM
Subject: Re: [RFC-ONT (on topic)] Modprobe enhancement (was Re: "Dance of
the Trolls")


> On Sun, 11 Nov 2001 16:49:46 -0700,
> "Jeff V. Merkey" <jmerkey@timpanogas.org> wrote:
> >Anton,
> >
> >This is a great suggestion.  You should ping Keith Owens (does he own
> >modutils, I think so) and make it happen.  A much desireable change.
> >----- Original Message -----
> >From: "Anton Altaparmakov" <aia21@cus.cam.ac.uk>
> >> I think we ought to do the same with closed source drivers. It's true
> >> after all... The whole point of tainting the kernel is so we can just
yell
> >> at users to go and bug the vendor. So the modprobe executable could
warn
> >> the user "hey, you are loading a binary only module, it can break the
> >> system, are you sure?". If the module is autoloaded we don't do jumping
> >> through hoops asking questions so the systen runs smoothly.
>
> Modutils 2.4.9 onwards gives a warning when loading tainted modules,
> including a reason why the tainting occurred.  I will not accept
> anything stronger than a warning, that is the Unix way(TM), give the
> user enough rope to hang themselves.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2001-11-12  3:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-11  3:34 Nazi kernels lobo
2001-11-11  3:05 ` Rik van Riel
2001-11-11  3:47 ` Mike Fedyk
2001-11-17  1:10   ` Jim Roland
2001-11-11  4:03 ` John Cavan
2001-11-11  4:09 ` Panagiotis Moustafellos
2001-11-11  5:35 ` Jeff V. Merkey
2001-11-11  5:58   ` Michael H. Warfield
2001-11-11 12:07     ` [Very-OT] " Anton Altaparmakov
2001-11-11 12:28       ` samson swanson
2001-11-11 23:49       ` [RFC-ONT (on topic)] Modprobe enhancement (was Re: "Dance of the Trolls") Jeff V. Merkey
2001-11-12  0:06         ` CaT
2001-11-12  0:24           ` [OT] " J Sloan
2001-11-12  0:34             ` CaT
2001-11-12 14:01             ` Stefan Smietanowski
2001-11-12  2:19         ` Keith Owens
2001-11-12  3:57           ` Jeff V. Merkey [this message]
2001-11-12  9:13       ` [Very-OT] Re: Nazi kernels Bernd Petrovitsch
2001-11-12  9:33         ` Anton Altaparmakov
2001-11-12  9:38           ` Bernd Petrovitsch
2001-11-11 10:51 ` Alex Buell
2001-11-11 13:32 ` Alan Cox
2001-11-11 16:46   ` Idea (Was: Re: .... kernels) degger
2001-11-11 16:50   ` Nazi kernels Tom Diehl
2001-11-11 19:07   ` Matt
2001-11-12 13:23   ` Marco Colombo
2001-11-12  9:13 ` Bernd Petrovitsch
2001-11-12 10:27 ` andrea gelmini
2001-11-12 10:32 ` DevilKin

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='001b01c16b2e$164cbcc0$f5976dcf@nwfs' \
    --to=jmerkey@timpanogas.org \
    --cc=kaos@ocs.com.au \
    --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