From: Phil Auld <pauld@egenera.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Configure.help is complete
Date: Fri, 01 Jun 2001 08:43:58 -0400 [thread overview]
Message-ID: <3B178E0E.A4530D47@egenera.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0105311555250.17748-100000@weyl.math.psu.edu>
Alexander Viro wrote:
...snip...
>
> We should start removing the crap from procfs in 2.5. Documenting shit is
> a good step, but taking it out would be better.
>
Not to open a what may be can of worms but ...
What's wrong with procfs?
It allows a general interface to the kernel that does not require new
syscalls/ioctls and can be accessed from user space without specifically
compiled programs. You can use shell scripts, java, command line etc.
Cheers,
Phil
------------------------------------------------------
Philip R. Auld, Ph.D. Technical Staff
Egenera Corp. pauld@egenera.com
165 Forest St, Marlboro, MA 01752 (508)786-9444
next prev parent reply other threads:[~2001-06-01 12:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-31 17:24 Configure.help is complete Eric S. Raymond
2001-05-31 20:13 ` José Luis Domingo López
2001-05-31 18:23 ` Eric S. Raymond
2001-05-31 18:21 ` Alan Cox
2001-06-01 1:50 ` José Luis Domingo López
2001-05-31 19:48 ` Arjan van de Ven
2001-05-31 19:57 ` Alexander Viro
2001-06-01 12:43 ` Phil Auld [this message]
2001-06-01 12:59 ` David Weinehall
2001-06-01 15:45 ` Jonathan Lundell
2001-06-02 18:27 ` Remi Turk
2001-05-31 22:56 ` Nerijus Baliunas
-- strict thread matches above, loose matches on Subject: below --
2001-05-31 20:12 BH
2001-05-31 20:42 ` Arjan van de Ven
2001-05-31 20:50 ` Eric S. Raymond
2001-05-31 21:22 ` 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=3B178E0E.A4530D47@egenera.com \
--to=pauld@egenera.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 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.