From: Bill Davidsen <davidsen@tmr.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel M/L <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Make procfs obligatory except under CONFIG_EMBEDDED
Date: Wed, 31 May 2006 18:18:03 -0400 [thread overview]
Message-ID: <447E161B.6060206@tmr.com> (raw)
In-Reply-To: <200605292207.k4TM722M027624@terminus.zytor.com>
H. Peter Anvin wrote:
> From: H. Peter Anvin <hpa@zytor.com>
>
> This patch makes procfs non-optional unless EMBEDDED is set, just like
> sysfs. procfs is already de facto required for a large subset of
> Linux functionality.
I have no objection, but I'm curious why this wasn't done long ago.
>
> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
>
> diff --git a/fs/Kconfig b/fs/Kconfig
> index 71d6b30..2c3a733 100644
> --- a/fs/Kconfig
> +++ b/fs/Kconfig
> @@ -764,7 +764,8 @@ endmenu
> menu "Pseudo filesystems"
>
> config PROC_FS
> - bool "/proc file system support"
> + bool "/proc file system support" if EMBEDDED
> + default y
> help
> This is a virtual file system providing information about the status
> of the system. "Virtual" means that it doesn't take up any space on
next prev parent reply other threads:[~2006-05-31 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 22:07 [PATCH] Make procfs obligatory except under CONFIG_EMBEDDED H. Peter Anvin
2006-05-31 22:18 ` Bill Davidsen [this message]
2006-05-31 22:18 ` H. Peter Anvin
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=447E161B.6060206@tmr.com \
--to=davidsen@tmr.com \
--cc=hpa@zytor.com \
--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