Messages in this thread | | | Date | Wed, 25 Apr 2001 23:50:00 +0200 | From | "J . A . Magallon" <> | Subject | Re: /proc format (was Device Registry (DevReg) Patch 0.2.0) |
| |
On 04.25 Jesse Pollard wrote: > > Alternatively, you can always put one value per record: > tag:value > tag2:value2... > > This is still simpler than XML to read, and to generate. >
Just my two cents.
It looks clear that /proc is for programs, not for humans. So the best format for proc is just binary values. So programs can read it quickly, even in a chunk if they know the format. But sometimes it is usefull to do a cat on a /proc entry.
Question: it is possible to redirect the same fs call (say read) to different implementations, based on the open mode of the file descriptor ? So, if you open the entry in binary, you just get the number chunk, if you open it in ascii you get a pretty printed version, or a format description like Bus: %d Device: %h .. to 'vprintf' the values.
-- J.A. Magallon # Let the source mailto:jamagallon@able.es # be with you, Luke...
Linux werewolf 2.4.3-ac14 #1 SMP Wed Apr 25 02:07:45 CEST 2001 i686
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |