public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: iSteve <isteve@rulez.cz>
To: "Randy.Dunlap" <rdunlap@xenotime.net>, linux-kernel@vger.kernel.org
Subject: Re: query_modules syscall gone? Any replacement?
Date: Tue, 13 Sep 2005 18:26:10 +0200	[thread overview]
Message-ID: <4326FDA2.90808@rulez.cz> (raw)
In-Reply-To: <Pine.LNX.4.50.0509130835120.7614-100000@shark.he.net>

>>I would like to be able to query symbols of a loaded module, get list of
>>and list of dependencies of loaded module from an app, preferably
>>without having to parse a file...
> 
> 
> No, no syscall to do that.  Looks like it will require reading
> and parsing files.
> 
> And you answered my "what" question clearly, so I have one more.
> Why?  for what purpose, to what end?  What are you tring to
> accomplish?

The files so far provided still do not seem to give these informations 
though...

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?

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

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

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=4326FDA2.90808@rulez.cz \
    --to=isteve@rulez.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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