> Date: Mon, 26 Feb 1996 09:59:56 -0500 (EST)
> From: Albert Cahalan <albert@ccs.neu.edu>
> To: linux-kernel@vger.rutgers.edu
> Subject: Re: Tagged files in /proc
>
> Why make this so hard for the kernel and apps?
>
> Always quote filenames like this: /my filename has a space/
Yes, I like that one.
> Numbers are always 0-padded hex: 00000B62
> Memory sizes are given in allocation units, often 4k or 8k pages.
> Space pad all strings - thus filenames are always padded to about 255.
>
> It would not be pretty, but it is still human readable.
> It is much faster, and you can just use proper tools to read proc
> information. I would say that /bin/cat is not a proper tool,
> unless you are trying to debug a better tool.
the whole point of /proc was that /bin/cat _WAS_ a proper tool.
if you want to only use tools to read config info, just use /dev/kmem
and rebuild without proc.
I personally like to cat /proc/status or /proc/cpuinfo or whatever.
It is still machine readable, as well as humanly readable.
--Dan