From: jlnance@unity.ncsu.edu
To: linux-kernel@vger.kernel.org
Subject: Possible module auto-loading problem
Date: Wed, 1 Jan 2003 20:50:18 -0500 [thread overview]
Message-ID: <20030102015018.GA14465@ncsu.edu> (raw)
Hello All,
I think I may have found a problem with respect to module
autoloading. While running the 2.5.53 kernel on a Red Hat 8.0 system,
I tried to automount an ext2 filesystem from a chrooted environment.
The mount failed with a message about ext2 not being supported by the
kernel. If I try this and the automounter is not running chrooted, then
the module gets autoloaded.
I must admit that I do not really know how module autoloading works.
I believe that the kernel exec /sbin/modprobe when it thinks it may
need a module. My theory is that when a chrooted command needs a module
/sbin/modprobe gets run with the chrooted root fs and it cant see the
ext2 module that it needs from there. I am not sure that this behavior
would be a bug, but I suspect it is something that no one has thought
about. Could someone shed some light on this?
Thanks,
Jim
reply other threads:[~2003-01-02 1:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030102015018.GA14465@ncsu.edu \
--to=jlnance@unity.ncsu.edu \
--cc=linux-kernel@vger.kernel.org \
/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