From: "H. Peter Anvin" <hpa@zytor.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux Kernel M/L <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Make procfs obligatory except under CONFIG_EMBEDDED
Date: Wed, 31 May 2006 15:18:30 -0700 [thread overview]
Message-ID: <447E1636.8050300@zytor.com> (raw)
In-Reply-To: <447E161B.6060206@tmr.com>
Bill Davidsen wrote:
> 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.
>
Probably because procfs predates CONFIG_EMBEDDED by many years, and noone really thought
about it. Either that or it was part of the "let's switch all of userspace to sysfs,
overnight!" conspiracy.
-hpa
prev parent reply other threads:[~2006-05-31 22:18 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
2006-05-31 22:18 ` H. Peter Anvin [this message]
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=447E1636.8050300@zytor.com \
--to=hpa@zytor.com \
--cc=davidsen@tmr.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