2.5 PROPOSAL: Replacement for current /proc of shit.
In a message dated 11/3/01 6:47:18 AM Eastern Standard Time, [email protected]
Quoted 9 lines · writes:
Quoted 1 line · you
Hmm, I'd argue that a GUI tool would be fairly useless without knowing
what
Quoted 1 line
the values meant anwyay, to give help, in which case you might as well
know
Quoted 1 line
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
Quoted 2 lines
and 3 for high compression. If a GUI shows me that only values between 0
and
Quoted 3 lines
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
Quoted 3 lines
select four strings, "none", "low", "medium" and "high".
I do see the advantages of using strings in proc, and maybe there is
another
Quoted 3 lines
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.
Quoted 3 lines
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
Quoted 5 lines · On Sat, 3 Nov 2001 [email protected] wrote:
Quoted 2 lines
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.
It would always be possible to build a front end to the /proc file system.
The approach taken by powertweak (http://www..powertweak.org) was to use an XML description of /proc to define types etc. It's worked out quite well, and has the added advantage of being buzzword compliant 8)
Dave.
Signature · 2 lines
| Dave Jones. http://www.codemonkey.org.uk | SuSE Labs
Quoted 3 lines · On Saturday 03 November 2001 14:06, [email protected] wrote:
Quoted 1 line
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.
Yes, but we are talking about a file system that is used to configure ALL drivers. So these descriptions should be written by the authors and distributed with the kernel.
bye...