From: Keith Owens <kaos@ocs.com.au>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Sean Hunter <sean@dev.sportingbet.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RFC: modules and 2.5
Date: Tue, 03 Jul 2001 17:39:02 +1000 [thread overview]
Message-ID: <2422.994145942@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 03 Jul 2001 03:24:26 -0400." <3B41732A.DD617268@mandrakesoft.com>
On Tue, 03 Jul 2001 03:24:26 -0400,
Jeff Garzik <jgarzik@mandrakesoft.com> wrote:
>> On Tue, 3 Jul 2001 07:50:50 +0100,
>> Sean Hunter <sean@dev.sportingbet.com> wrote:
>> >Does this defeat my favourite module-related gothcha, that the machine panics
>> >if I have (say) a scsi driver builtin to the kernel and the same driver tries
>> >to load itself as a module?
>
>If this occurs in 2.4 it is a bug and should be fixed in 2.4.
Human error. Create a new kernel with something built in which used to
be a module and forget to make modules_install, so the code is in the
kernel and in /lib/modules. Then do an explicit insmod, if probing
does not fail the module load then oops is all she wrote. One of the
reasons I changed modules_install to erase the old directory first was
to minimize this problem, but humans can still stuff it up. AFAICT it
cannot be fixed in 2.4 because there is no identifier for which
"modules" are included in the kernel.
next prev parent reply other threads:[~2001-07-03 7:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-03 5:13 RFC: modules and 2.5 Jeff Garzik
2001-07-03 6:50 ` Sean Hunter
2001-07-03 7:05 ` Jeff Garzik
2001-07-03 7:16 ` Keith Owens
2001-07-03 7:24 ` Jeff Garzik
2001-07-03 7:39 ` Keith Owens [this message]
2001-07-03 7:44 ` Jeff Garzik
2001-07-03 7:48 ` Fang Han
2001-07-03 7:18 ` Keith Owens
2001-07-03 12:15 ` jlnance
2001-07-06 10:34 ` Rusty Russell
2001-07-07 14:12 ` Jeff Garzik
2001-07-08 7:40 ` Rusty Russell
2001-07-11 22:04 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2001-07-03 17:35 Andrzej Krzysztofowicz
2001-07-03 17:39 ` Jeff Garzik
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=2422.994145942@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sean@dev.sportingbet.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