Re: modinfo modulename question

2007-09-06 Thread Jan Engelhardt
On Sep 5 2007 13:31, Justin Piszcz wrote: Is there anyway to get/see what parameters were passed to a kernel module? Not really. Even if a module has parameters exported, they may carry default values (and hence, don't fulfill the word passed, as would be the case with `modprobe foo`

modinfo modulename question

2007-09-05 Thread Justin Piszcz
Is there anyway to get/see what parameters were passed to a kernel module? Running modinfo -p module will show the defaults, but for example, st, the scsi tape driver, is there a way to see what it is currently using? I know in dmesg it shows this when you load it initially (but if say dmesg

Re: modinfo modulename question

2007-09-05 Thread Randy Dunlap
On Wed, 5 Sep 2007 12:34:13 -0400 (EDT) Justin Piszcz wrote: Is there anyway to get/see what parameters were passed to a kernel module? Running modinfo -p module will show the defaults, but for example, st, the scsi tape driver, is there a way to see what it is currently using? I know in

Re: modinfo modulename question

2007-09-05 Thread Bodo Eggert
Justin Piszcz [EMAIL PROTECTED] wrote: Is there anyway to get/see what parameters were passed to a kernel module? Running modinfo -p module will show the defaults, but for example, st, the scsi tape driver, is there a way to see what it is currently using? /sys/modules/$NAME/parameters (if

Re: modinfo modulename question

2007-09-05 Thread Chris Snook
Justin Piszcz wrote: Is there anyway to get/see what parameters were passed to a kernel module? Running modinfo -p module will show the defaults, but for example, st, the scsi tape driver, is there a way to see what it is currently using? I know in dmesg it shows this when you load it