From: "Jeff V. Merkey" <jmerkey@timpanogas.org>
To: "Anton Altaparmakov" <aia21@cus.cam.ac.uk>,
"Michael H. Warfield" <mhw@wittsend.com>
Cc: <lobo@polbox.com>, <linux-kernel@vger.kernel.org>
Subject: [RFC-ONT (on topic)] Modprobe enhancement (was Re: "Dance of the Trolls")
Date: Sun, 11 Nov 2001 16:49:46 -0700 [thread overview]
Message-ID: <004601c16b0b$8b04bb80$f5976dcf@nwfs> (raw)
In-Reply-To: <Pine.SOL.3.96.1011111120107.21134C-100000@libra.cus.cam.ac.uk>
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.
Jeff
----- Original Message -----
From: "Anton Altaparmakov" <aia21@cus.cam.ac.uk>
To: "Michael H. Warfield" <mhw@wittsend.com>
Cc: "Jeff V. Merkey" <jmerkey@timpanogas.org>; <lobo@polbox.com>;
<linux-kernel@vger.kernel.org>
Sent: Sunday, November 11, 2001 5:07 AM
Subject: [Very-OT] Re: Nazi kernels
> On Sun, 11 Nov 2001, Michael H. Warfield wrote:
> > Oh, but you missed the mark! Think Windows XP. Now there's
> > the ticket. If you aren't a Windows XP certified driver, they can
> > just wipe your driver right off the face of the system... All in the
> > name of "stability" (as they define it). None of this nonsense of
> > merely flagging if their OS has a non-sanctified driver like Linux.
> > Linux lets the driver load and run, it merely lets people KNOW that
> > it's an un-sanctified driver when shit catches fire and burns. You
> > know MS. MS thinks Linux is just a bunch of whimps. Screw just letting
> > the user know AFTER something burps and burns. That's TOO complicated
> > for a user to figure out and MS has to be "user friendly". MS is for
> > men with balls (and no brains)... Just burn the driver BEFORE it has
> > a chance to run. Yeah! That's the ticket!
>
> Let's not get carried away. Windows XP does allow you to install anything
> you like. You just have to click several times on the Yes button when it
> asks things like "This driver is not XP certified. Do you really want to
> use it?" and "Installing a non-certified driver can cause system
> instability. Are you sure you want to do this?" (text is probably not
> quite right but you get the idea).
>
> 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.
>
> Best regards,
>
> Anton
> --
> Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
> Linux NTFS maintainer / WWW: http://linux-ntfs.sf.net/
> ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/
next prev parent reply other threads:[~2001-11-11 23:51 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 ` Jeff V. Merkey [this message]
2001-11-12 0:06 ` [RFC-ONT (on topic)] Modprobe enhancement (was Re: "Dance of the Trolls") 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
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='004601c16b0b$8b04bb80$f5976dcf@nwfs' \
--to=jmerkey@timpanogas.org \
--cc=aia21@cus.cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lobo@polbox.com \
--cc=mhw@wittsend.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