On Wed, 2005-01-26 at 15:09, Matt Domsch wrote:
On Wed, Jan 26, 2005 at 10:22:29AM +0100, Andreas Gruenbacher wrote:
On Wednesday 26 January 2005 07:05, Matt Domsch wrote:
Module: Add module version and srcversion to the sysfs tree
why do you need this?
a) Tools like DKMS, which deal with changing out individual kernel modules without replacing the whole kernel, can behave smarter if they can tell the version of a given module.
They can look at the modules in /lib/modules/$(uname -r).
I think he means he wants to know what's in memory, not on the disk.
[ snip ]
c) as the unbind-driver-from-device work takes shape, it will be possible to rebind a driver that's built-in (no .ko to modinfo for the version) to a newly loaded module. sysfs will have the currently-built-in version info, for comparison.
d) tech support scripts can then easily grab the version info for what's running presently - a question I get often.
That's something you can do entirely in userspace by looking at the *.ko files.
How do you find which *.ko file was used to load the module in memory? I think you are talking about two things here.
-- -bill davidsen ([EMAIL PROTECTED]) "The secret to procrastination is to put things off until the last possible moment - but no longer" -me - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
