[lkml]   [2001]   [Nov]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: PROPOSAL: dot-proc interface [was: /proc stuff]
On Sunday 04 November 2001 16:33, you wrote:
> Maintaining the current /proc files is very simple, and it offers the
> system administrator a lot of functionality that isn't reasonable to take
> away now.
> * They should stay in a form close to the current one *

I doubt that it is worthwhile to keep them in the current form for any other
reason than compatibility (with existing software and people's habits).
It doesn't make sense to describe things in 200 different formats, you won't
help anybody with that. It also violates the good old principle of keeping
policy out of the kernel. And, for me, layout is clearly policy.

The reason for proc's popularity is clearly that you can use any tool, from
cat over more/less to the text editor of choice, and read the files. There
should be ways to achieve this without putting things into the kernel. Is
there is a way to implement a filesystem in user-space? What you could do is
to export the raw data using single-value-files, XML or whatever and then
provide an emulation of the old /proc files and possibly new ones in user
space. This could be as simple as writing a shell-script for each emulated

> The dot-proc file is basically a binary encoding of Lisp (or XML), e.g. it
> is a list of elements, wherein an element can itself be a list (or a

Why would anybody want a binary encoding?
It needs special parsers and will be almost impossible to access from shell

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:12    [W:0.389 / U:0.460 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site