Re: does /proc/sys/kernel/modprobe actually do anything?

2007-11-29 Thread Robert P. J. Day
On Thu, 29 Nov 2007, Kay Sievers wrote: > On Nov 29, 2007 1:58 PM, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > > On Thu, 29 Nov 2007, Alexey Dobriyan wrote: > > > > > On 11/29/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > > > > echo '#! /bin/sh' > /tmp/modprobe > > > > echo 'echo "$@" >> /tm

Re: does /proc/sys/kernel/modprobe actually do anything?

2007-11-29 Thread Kay Sievers
On Nov 29, 2007 1:58 PM, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > On Thu, 29 Nov 2007, Alexey Dobriyan wrote: > > > On 11/29/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > > > echo '#! /bin/sh' > /tmp/modprobe > > > echo 'echo "$@" >> /tmp/modprobe.log' >> /tmp/modprobe > > > echo 'exec /sb

Re: does /proc/sys/kernel/modprobe actually do anything?

2007-11-29 Thread Robert P. J. Day
On Thu, 29 Nov 2007, Alexey Dobriyan wrote: > On 11/29/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > > 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/mod

Re: does /proc/sys/kernel/modprobe actually do anything?

2007-11-29 Thread Robert P. J. Day
On Thu, 29 Nov 2007, Alexey Dobriyan wrote: > On 11/29/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > > 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/mod

Re: does /proc/sys/kernel/modprobe actually do anything?

2007-11-29 Thread Alexey Dobriyan
On 11/29/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > 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 a

does /proc/sys/kernel/modprobe actually do anything?

2007-11-29 Thread Robert P. J. Day
(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/modp