public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: iSteve <isteve@rulez.cz>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
	linux-kernel@vger.kernel.org
Subject: Re: query_modules syscall gone? Any replacement?
Date: Fri, 09 Sep 2005 18:10:44 +0200	[thread overview]
Message-ID: <4321B404.1000400@rulez.cz> (raw)
In-Reply-To: <Pine.LNX.4.61.0509091116490.4715@chaos.analogic.com>

Drat, that's a pity, the interface seemed pretty neat and usable (from 
my rather linux-kernel-newbie point of view, anyway:), especially neater 
than parsing a file.

Why did the query_module get removed, by the way? (I searched lkml, but 
lkml.org search on 'query module' or 'query_module' didn't really give 
me any relevant hits).

  - iSteve

linux-os (Dick Johnson) wrote:
> On Fri, 9 Sep 2005, iSteve wrote:
> 
> 
>>Greetings,
>> I'm coding an application that messes with modules a lot, and I've
>>stumbled upon a query_modules syscall in my docs. Later I've found out
>>that the docs come from modutils and that module-init-tools doesn't seem
>>to document (any of) the syscalls.
>>
>> May I then ask, why is the query_module syscall gone? And more
>>importantly, what replaces it, if anything? It seems to me that parsing
>>the /proc/modules is not only less comfortable, but according to the
>>very obsolete manpage I have, it also can provide less information.
>>
>> For exmaple I'm not aware of anything like QM_SYMBOLS on per-module
>>basis like it was (do correct me if I am wrong, it'd simplify my work a
>>lot), ... and getting QM_REFS for example requires extensive parsing of
>>/proc/modules.
>>
>>Thanks in advance for reply.
>>
>> - iSteve
> 
> 
> The newer modutils package doesn't use query_modules and calling
> that function will return -ENOSYS in 'modern' kernels. The
> latest modutils becomes very sparse because most of the module
> functionality got moved into the kernel where it expanded, err,..
> don't get me started. Anyway, your user-mode interface is now
> /proc/modules. It does provide a bit more information than
> before, but as you noticed, it sucks^M^M^M^M^Mis not nice.
> Have fun!
> 
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.6.13 on an i686 machine (5589.53 BogoMips).
> Warning : 98.36% of all statistics are fiction.
> .
> I apologize for the following. I tried to kill it with the above dot :
> 
> ****************************************************************
> The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
> 
> Thank you.

  reply	other threads:[~2005-09-09 16:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 15:02 query_modules syscall gone? Any replacement? iSteve
2005-09-09 15:27 ` linux-os (Dick Johnson)
2005-09-09 16:10   ` iSteve [this message]
     [not found] <4KSFY-2pO-17@gated-at.bofh.it>
2005-09-09 20:25 ` Bodo Eggert
2005-09-09 20:33   ` iSteve
2005-09-13 14:11   ` iSteve
2005-09-13 15:15     ` Randy.Dunlap
2005-09-13 15:30       ` iSteve
2005-09-13 15:44         ` Randy.Dunlap
2005-09-13 16:26           ` iSteve
2005-09-13 16:52             ` Randy.Dunlap
2005-09-13 19:50             ` Daniel Barkalow
2005-09-13 15:50         ` Jesper Juhl

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=4321B404.1000400@rulez.cz \
    --to=isteve@rulez.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    /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