> In message <Pine.SOL.3.96.1011111120107.21134C-100000@libra.cus.cam.ac.uk>, Ant
> on Altaparmakov wrote:
> >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.
>
> Un*x admins know what they are doing by definition. So this is not
> necessary.
> Now you see what some Seattle area company think of admins of theirs
> (so called) OS.
Admins know what they are doing. Your average person trying Linux for the
first time doesn't... You are forgetting that Linux is actually becoming
useful as a desktop OS and a wider audience is starting to use it.
But considering you already get a warning message on insertion that will
do fine, no need to ask are you sure. GUI configuration tools can always
do the "are you sure bit" if they want to.
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/- 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/