From: Telford002@aol.com
To: tim@tjansen.de, rusty@rustcorp.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5 PROPOSAL: Replacement for current /proc of shit.
Date: Sat, 3 Nov 2001 08:06:01 EST [thread overview]
Message-ID: <86.1204971d.291545b9@aol.com> (raw)
In a message dated 11/3/01 6:47:18 AM Eastern Standard Time, tim@tjansen.de
writes:
> On Saturday 03 November 2001 00:31, you wrote:
> > Hmm, I'd argue that a GUI tool would be fairly useless without knowing
> what
> > the values meant anwyay, to give help, in which case you might as well
> know
> > the types.
>
> Take, as an example, the compression module parameter of the PWC (Philips
> Webcam) driver. Currently you can specify a value between 0 for
uncompressed
>
> and 3 for high compression. If a GUI shows me that only values between 0
and
>
> 3 are allowed I could guess that I have to enter "3" for high compression
> without searching for the documentation. It would be even better if I
could
> select four strings, "none", "low", "medium" and "high".
>
> I do see the advantages of using strings in proc, and maybe there is
another
>
> solution: keep the type information out of the proc filesystem and save it
> in a file similar to Configure.help, together with a description for a
file.
>
> I just don't know how to ensure that they are in sync.
>
It would always be possible to build a front end to the /proc file
system.
Joachim Martillo
next reply other threads:[~2001-11-03 13:06 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-03 13:06 Telford002 [this message]
2001-11-03 13:36 ` [PATCH] 2.5 PROPOSAL: Replacement for current /proc of shit Dave Jones
2001-11-03 14:20 ` Tim Jansen
-- strict thread matches above, loose matches on Subject: below --
2001-11-01 10:32 Rusty Russell
2001-11-01 10:42 ` Jeff Garzik
2001-11-01 16:49 ` Martin Dalecki
2001-11-01 17:06 ` Gábor Lénárt
2001-11-02 1:42 ` Rusty Russell
2001-11-02 1:56 ` Erik Andersen
2001-11-02 11:44 ` Padraig Brady
2001-11-02 9:11 ` Alexander Viro
2001-11-02 12:39 ` Martin Dalecki
2001-11-02 11:57 ` Alexander Viro
2001-11-02 13:55 ` Keith Owens
2001-11-02 15:08 ` Martin Dalecki
2001-11-04 5:36 ` Albert D. Cahalan
2001-11-02 12:46 ` Miquel van Smoorenburg
2001-11-01 12:06 ` Tim Jansen
2001-11-01 18:34 ` James Simmons
2001-11-02 2:20 ` Rusty Russell
2001-11-02 13:59 ` Tim Jansen
[not found] ` <20011103103106.7eb6098b.rusty@rustcorp.com.au>
2001-11-03 11:47 ` Tim Jansen
2001-11-03 23:44 ` Rusty Russell
2001-11-04 1:40 ` Daniel Phillips
2001-11-04 2:08 ` Jakob Østergaard
2001-11-04 12:30 ` Tim Jansen
2001-11-04 13:36 ` Daniel Kobras
2001-11-04 14:13 ` Tim Jansen
2001-11-05 0:12 ` Rusty Russell
2001-11-05 3:34 ` Daniel Phillips
2001-11-05 22:48 ` Rusty Russell
2001-11-06 10:25 ` Daniel Phillips
2001-11-06 15:46 ` Theodore Tso
2001-11-07 23:35 ` Rusty Russell
2001-11-05 16:49 ` Jonathan Lundell
2001-11-05 20:46 ` Tim Jansen
2001-11-05 23:04 ` Greg KH
2001-11-05 22:19 ` Tim Jansen
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=86.1204971d.291545b9@aol.com \
--to=telford002@aol.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=tim@tjansen.de \
/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.