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 18:21:47 +1000 [thread overview]
Message-ID: <23837.1003738907@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 22 Oct 2001 04:05:54 -0400." <Pine.GSO.4.21.0110220404000.2294-100000@weyl.math.psu.edu>
On Mon, 22 Oct 2001 04:05:54 -0400 (EDT),
Alexander Viro <viro@math.psu.edu> wrote:
>On Mon, 22 Oct 2001, Keith Owens wrote:
>> On Mon, 22 Oct 2001 02:47:39 -0400 (EDT),
>> Alexander Viro <viro@math.psu.edu> wrote:
>> >post-install binfmt_misc mount -t binfmt_misc none /proc/sys/binfmt_misc
>> >pre-remove binfmt_misc umount /proc/sys/binfmt_misc
>>
>> It is not hard wired in the standard modutils, because there is no way
>> of overriding it.
>
>???
>Elaborate, please.
When the post-install and pre-remove entries for module binfmt_misc are
hard coded into modprobe, there is no syntax in modules.conf to prevent
modprobe from always issuing those commands. The next time somebody
decides that binfmt_misc needs different commands, everybody using the
old modutils on the new kernel will break. I don't want the hassle,
put it in modules.conf where it can easily be changed.
If I can get an iron clad guarantee that binfmt_misc will never, ever
change again then I might consider hard coding the entries in modprobe.
BTW, I will need a signature in blood that says I can kill you if
binfmt_misc is ever changed :).
next prev parent reply other threads:[~2001-10-22 8:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 11:54 [PATCH] binfmt_misc.c, kernel-2.4.12 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 [this message]
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
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=23837.1003738907@kao2.melbourne.sgi.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.