From: Keith Owens <kaos@ocs.com.au>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] binfmt_misc.c, kernel-2.4.12
Date: Mon, 22 Oct 2001 21:17:48 +1000 [thread overview]
Message-ID: <25634.1003749468@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 22 Oct 2001 05:34:43 -0400." <Pine.GSO.4.21.0110220526480.2294-100000@weyl.math.psu.edu>
On Mon, 22 Oct 2001 05:34:43 -0400 (EDT),
Alexander Viro <viro@math.psu.edu> wrote:
>On Mon, 22 Oct 2001, Keith Owens wrote:
>> In modutils 2.5 I will get rid of all the hard coded entries in
>> util/alias.h. Instead each module will define what it supports,
>> including any special commands to be run when the module is loaded or
>> unloaded. Much easier for everyone and far more flexible.
>
>Heh. OK, so you've stopped me in the middle of writing RFC that proposes
>addition of
>MODULE_CONF(string)
Strange, that was exactly what I was planning for 2.5 :).
>that would put that string into separate section and making modules_install
<pedantic>
depmod, not modules_install, depmod is run at other times.
</pedantic>
>dump these sections, feed them through s/_NAME_/`basename $module`/ and
kbuild 2.5 does -DKBUILD_OBJECT=module_name for all objects linked into
a module. KBUILD_OBJECT defines the overall module, not the individual
files that make up the module. We have the technology!
>cat them into defaults file that would go into $INSTALL_MOD_PATH.
Just another modules.* file, probably modules.dynamic.conf.
BTW, INSTALL_MOD_PATH is dead in kbuild 2.5, it is a configuration
option and is held in .config.
>MODULES_BLKDEV(), MODULE_LDISC(), etc. would be trivial wrappers around that.
Everything is a device and can be handled by the hotplug project. It
is really a cunning plan by David Brownell and Greg Kroah-Hartman to
own the entire device subsystem ;).
>Looks like the thing you mentioned would make quite a few people happy.
>Might be worth doing in 2.4...
Please, no more 2.4 changes. Let Linus get 2.4 stable, fork 2.5 so we
can break it on a daily basis then backport to 2.4 when it works.
next prev parent reply other threads:[~2001-10-22 11:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 11:54 Albert Bartoszko
2001-10-19 12:54 ` Alexander Viro
2001-10-19 13:32 ` Richard Guenther
2001-10-19 18:48 ` Alexander Viro
2001-10-19 21:35 ` Richard Guenther
2001-10-19 22:00 ` Alexander Viro
2001-10-22 6:00 ` Albert Bartoszko
2001-10-22 6:47 ` Alexander Viro
2001-10-22 7:42 ` Keith Owens
2001-10-22 8:05 ` Alexander Viro
2001-10-22 8:21 ` Keith Owens
2001-10-22 8:33 ` Alexander Viro
2001-10-22 9:19 ` Keith Owens
2001-10-22 9:34 ` Alexander Viro
2001-10-22 9:55 ` Alexander Viro
2001-10-22 11:17 ` Keith Owens [this message]
2001-10-22 11:33 ` Alexander Viro
2001-10-22 11:52 ` Keith Owens
2001-10-22 12:15 ` Alexander Viro
2001-10-22 12:37 ` Keith Owens
2001-10-22 15:56 ` bill davidsen
2001-10-22 15:47 ` bill davidsen
2001-10-22 17:24 ` Andrew Morton
2001-10-22 17:50 ` Alexander Viro
2001-10-23 9:28 ` Albert Bartoszko
2001-10-21 15:26 ` Alan Cox
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=25634.1003749468@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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
all inboxes | Powered by JetHome®