Message-ID: <4326DE0E.2060306@rulez.cz>
Date: Tue, 13 Sep 2005 16:11:26 +0200
From: iSteve <isteve@rulez.cz>
User-Agent: Debian Thunderbird 1.0.2 (X11/20050602)
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: Re: query_modules syscall gone? Any replacement?
References: <4KSFY-2pO-17@gated-at.bofh.it> <E1EDpQq-0000iV-Oe@be1.lrz>
In-Reply-To: <E1EDpQq-0000iV-Oe@be1.lrz>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1091
Lines: 27

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/