From: Matthew Wilcox <willy@debian.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Matthew Wilcox <willy@debian.org>,
Linus Torvalds <torvalds@transmeta.com>,
Andrew Morton <akpm@zip.com.au>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Consolidate Kconfigs for binfmts
Date: Fri, 13 Jun 2003 19:29:18 +0100 [thread overview]
Message-ID: <20030613182918.GC30843@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.GSO.4.21.0306131523490.13821-100000@vervain.sonytel.be>
On Fri, Jun 13, 2003 at 03:24:34PM +0200, Geert Uytterhoeven wrote:
> On Fri, 13 Jun 2003, Matthew Wilcox wrote:
> > +config BINFMT_MISC
> > + tristate "Kernel support for MISC binaries"
> > + ---help---
>
> > + You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
> > + use this part of the kernel.
>
> You don't want to add an explicit dependency?
I was thinking about this and decided to check it out. It's actually
not true any more. binfmt_misc was converted (back in 2.4) to be its
own filesystem. If binfmt_misc is compiled in or as a module (?!),
procfs creates somewhere for you to mount it (/proc/sys/fs/binfmt_misc)
but there's no need to mount it there.
I note that if you have CONFIG_SYSCTL=n, it will actually silently fail
to create this directory.
#ifdef CONFIG_SYSCTL
proc_sys_root = proc_mkdir("sys", 0);
#endif
#if defined(CONFIG_BINFMT_MISC) || defined(CONFIG_BINFMT_MISC_MODULE)
proc_mkdir("sys/fs", 0);
proc_mkdir("sys/fs/binfmt_misc", 0);
#endif
So I guess I'll remove the bit from the helptext about procfs
and substitute some better words instead. Maybe I'll update
Documentation/binfmt_misc too.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
parent reply other threads:[~2003-06-13 18:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.GSO.4.21.0306131523490.13821-100000@vervain.sonytel.be>]
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=20030613182918.GC30843@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=akpm@zip.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®