On Tue, 13 Sep 2005, iSteve wrote:
> Part of the project I'm working on -- click-click ui for handling modules,
> with some perks: in this case, getting info about loaded modules that I hoped
> to obtain via query_module.
>
> Oh, and one more question: There were no particular issues with query_module,
> or were they? If there weren't, why wasn't it kept?
I think it wasn't kept because it would have had to get rewritten anyway,
and the only user (modutils) was going away. Most of the information was
only there because the old system needed it, and the new system didn't
need it, so nobody bothered. Also, the modern style is to avoid
special-purpose syscalls and use sysfs. It probably wouldn't be too hard
to get the information exported through the sysfs interface if you ask
Rusty and explain exactly what you need.
(Note that you can get module symbols by searching /proc/kallsyms for
<tab>[<name>], so that part is available from the kernel, although not
efficiently if you have a lot of symbols that you aren't interested in)
-Daniel
*This .sig left intentionally blank*
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |