public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: iSteve <isteve@rulez.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: query_modules syscall gone? Any replacement?
Date: Tue, 13 Sep 2005 16:11:26 +0200	[thread overview]
Message-ID: <4326DE0E.2060306@rulez.cz> (raw)
In-Reply-To: <E1EDpQq-0000iV-Oe@be1.lrz>

Okay, so, I have so far gathered:

  - the whole module interface change between 2.4 and 2.6 was because 
some security concerns, most of the stuff (loading module etc.) moved 
towards kernel
  - query_module is gone, there is no syscall similar in function but 
with different name
  - losing of query_module also prevents binary-only modules 
(guesswork@work)
  - /proc/modules and /sys/module interface doesn't by far supply what 
query_module could do

My questions are:
a) Are my observations correct? Where did I go wrong?
b) Is there any planned replacement of query_module, or extendind sysfs 
or procfs module interface?
c) Wouldn't revamping query_module also allow binary-only modules, 
therefore easier decisions for vendors, whether to support Linux?

Thanks in advance and sorry for these probably quite silly questions.

  - iSteve

  parent reply	other threads:[~2005-09-13 14:11 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 [this message]
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
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=4326DE0E.2060306@rulez.cz \
    --to=isteve@rulez.cz \
    --cc=linux-kernel@vger.kernel.org \
    /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