From: Jonathan Lundell <jlundell@pobox.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Configure.help is complete
Date: Fri, 1 Jun 2001 08:45:17 -0700 [thread overview]
Message-ID: <p05100308b73d672c7f2b@[207.213.214.37]> (raw)
In-Reply-To: <20010601145900.C12402@khan.acc.umu.se>
In-Reply-To: <Pine.GSO.4.21.0105311555250.17748-100000@weyl.math.psu.edu> <3B178E0E.A4530D47@egenera.com> <20010601145900.C12402@khan.acc.umu.se>
At 2:59 PM +0200 2001-06-01, David Weinehall wrote:
> > Not to open a what may be can of worms but ...
>>
>> What's wrong with procfs?
>
>Imho, a procfs should be for process-information, nothing else.
>The procfs in its current form, while useful, is something horrible
>that should be taken out on the backyard and shot using slugs.
>
>Ehrmmm. No, but seriously, the non-process stuff should be separate
>from the procfs. Maybe call it kernfs or whatever.
>
>> 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.
>
>Yes, and it's also totally non standardised.
It clearly fills a need, though, and has the distinct side benefit of
cutting down on the proliferation of ioctls. Sure, it's non-standard
and a mess. But it's semi-documented, easy to use, and v. general.
What's the preferred alternative, to state the first question another
way? For any single small project/driver, creating a new fs simply
isn't going to happen.
--
/Jonathan Lundell.
next prev parent reply other threads:[~2001-06-01 15:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-31 17:24 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
2001-06-01 12:59 ` David Weinehall
2001-06-01 15:45 ` Jonathan Lundell [this message]
2001-06-02 18:27 ` Remi Turk
2001-05-31 22:56 ` Nerijus Baliunas
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='p05100308b73d672c7f2b@[207.213.214.37]' \
--to=jlundell@pobox.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
all inboxes | Powered by JetHome®