mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: does /proc/sys/kernel/modprobe actually do anything?
Date: Thu, 29 Nov 2007 04:41:55 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.0.9999.0711290438060.13461@localhost.localdomain> (raw)


  (i asked about this earlier on the newbies list, but after poking
around a bit more, i thought i'd ask here.)

  according to Documentation/debugging-modules.txt:

The correct way of debugging module problems is something like this:

echo '#! /bin/sh' > /tmp/modprobe
echo 'echo "$@" >> /tmp/modprobe.log' >> /tmp/modprobe
echo 'exec /sbin/modprobe "$@"' >> /tmp/modprobe
chmod a+x /tmp/modprobe
echo /tmp/modprobe > /proc/sys/kernel/modprobe

  i've tried that and i don't see that it does anything whatsoever.  i
ran modprobe under "strace" and it doesn't appear to make any effort
to check /proc/sys/kernel/modprobe.  i even downloaded the source to
the module-init-tools package and scanned the source and ... nothing.

  so what's up with that?

rday

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================

             reply	other threads:[~2007-11-29  9:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29  9:41 Robert P. J. Day [this message]
2007-11-29 10:07 ` Alexey Dobriyan
2007-11-29 10:19   ` Robert P. J. Day
2007-11-29 12:58   ` Robert P. J. Day
2007-11-29 17:14     ` Kay Sievers
2007-11-29 17:21       ` Robert P. J. Day

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=alpine.LFD.0.9999.0711290438060.13461@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --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

all inboxes | Powered by JetHome®