linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
To: Valdis.Kletnieks@vt.edu
Cc: linux-os@analogic.com, Colin Leroy <colin.lkml@colino.net>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: insmod module-loading errors, Linux-2.6.9
Date: Wed, 10 Nov 2004 12:38:22 -0500	[thread overview]
Message-ID: <4192520E.2080101@tmr.com> (raw)
In-Reply-To: <200411090000.iA900Obi004485@turing-police.cc.vt.edu>

Valdis.Kletnieks@vt.edu wrote:
> On Mon, 08 Nov 2004 12:52:18 EST, linux-os said:

>>They simply should not have removed the "-f" option of
>>insmod. It's just that simple. This option allowed transient
>>(possible) incompatibilities so that one could be productive
>>and not spend a whole day reinstalling from a distribution
>>CD because the new modules wouldn't work because somebody
>>decided that their special VERMAGIC_STRING was so ")@*&#$%)"
>>important that they preempted my work. Don't get me started....
> 
> 
> Yes, instead you can spend a whole day reinstalling from a
> distribution CD, and then restoring user files from backup,
> because the new module you just 'insmod -f' had a different
> number of parameters to some kernel call, and as a result your
> stack got smashed and took the root filesystem with it....

This is Linux, not MS-DOS, where the system works for the user and you 
shouldn't have to do nonsense like "do you really want to load the 
module?" I agree with Dick, you shouldn't have to recompile the whole 
kernel to fix a trivial change. If you shoot yourself in the foot it's 
your fault, taking away the the gun is the policy of another o/s I won't 
name.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

      parent reply	other threads:[~2004-11-10 20:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 15:12 insmod module-loading errors, Linux-2.6.9 linux-os
2004-11-08 16:56 ` Colin Leroy
2004-11-08 17:52   ` linux-os
2004-11-09  0:00     ` Valdis.Kletnieks
2004-11-09 12:46       ` linux-os
2004-11-09 18:04         ` Mike Waychison
2004-11-09 23:37           ` Rusty Russell
2004-11-10 17:38       ` Bill Davidsen [this message]

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=4192520E.2080101@tmr.com \
    --to=davidsen@tmr.com \
    --cc=colin.lkml@colino.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.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;
as well as URLs for NNTP newsgroup(s).