From: Mike Waychison <Michael.Waychison@Sun.COM>
To: linux-os@analogic.com
Cc: Valdis.Kletnieks@vt.edu, Colin Leroy <colin.lkml@colino.net>,
Linux kernel <linux-kernel@vger.kernel.org>,
rusty@rustcorp.com.au
Subject: Re: insmod module-loading errors, Linux-2.6.9
Date: Tue, 09 Nov 2004 13:04:49 -0500 [thread overview]
Message-ID: <419106C1.40809@sun.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0411090745160.11563@chaos.analogic.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
linux-os wrote:
> On Mon, 8 Nov 2004 Valdis.Kletnieks@vt.edu wrote:
>
>> On Mon, 08 Nov 2004 12:52:18 EST, linux-os said:
>>
>>> There are certainly work-arounds for problems that shouldn't
>>> exist at all. So, every time I do something to a kernel, I
>>> have to change whatever the EXTRAVERSION field is? Then, when
>>> a customer demands that the kernel version be exactly the
>>> same that was shipped with Fedora or whatever, I'm screwed.
>>
>>
>> If you didn't have the foresight to keep that kernel version around,
>> there isn't much we can do to help you. Yes, this may mean you have
>> a big bunch of /usr/src/linux-2.6.* directories.
>>
>
> Wrong. Whoever put the module-loading code INSIDE the kernel,
> for POLITICAL reasons, created a new POLICY.
>
No. Version information is still stripped in module-init-tools in
_userspace_ for modprobe --force. The fact that insmod doesn't support
'-f' is probably an oversight and Rusty would likely accept a patch.
- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBkQbBdQs4kOxk3/MRArfFAJ9So6d7pRXqAgkuGj9XhsELsrymdgCfZs+x
Yz1bhTMbZkD35dbd8CEk+vk=
=kAgK
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-11-09 18:05 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 [this message]
2004-11-09 23:37 ` Rusty Russell
2004-11-10 17:38 ` Bill Davidsen
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=419106C1.40809@sun.com \
--to=michael.waychison@sun.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=colin.lkml@colino.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=rusty@rustcorp.com.au \
/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.