Re: What /proc should contain [was: /proc/driver/microcode]

From: Strohm Thomas (FV/SLD) * (
Date: Thu Feb 24 2000 - 08:57:44 EST

...fine. Once again the neverending proc

IMHO the only serious point against /proc [here and in the discussion
sysctl() vs.
/proc] is the formatting issue (performance set aside).

SO: Why don't you consider introducing *binary* proc files in addition
to human readable ones?

meminfo would be paralleled by a binary file meminfo.b and a struct
{...} in <linux/proc_fmts.h>. Then there would be no problem with parsing
The human being :-) reads meminfo and the C program reads meminfo.b and type
casts it to struct proc_meminfo [introducing once again a flat namespace


[please CC me...]

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

This archive was generated by hypermail 2b29 : Tue Feb 29 2000 - 21:00:10 EST