> >1) IT SHOULD NOT BE PRETTY. No tabs to line up columns. No "progress
> >bars." No labels except as "proc comments" (see later). No in-line labelling.
>
> It should not be pretty TO HUMANS. Slight difference. It should
> be pretty to shellscripts and other applications though.
I really fail to see your point, it's trivial to make
files which are easy to read by humans and also very
easy to parse by shellscripts.
PROCESSOR=0
VENDOR_ID=GenuineIntel
CPU_FAMILY=6
MODEL=6
MODEL_NAME="Celeron (Mendocino)"
.....
As you can see, this is easily readable by humans,
while "parsing" by a shell script would be as follows:
. /proc/cpuinfo
After which you could just "echo $PROCESSOR" or
something like that ...
Yes, this is probably a bad example, but it does show
that machine-readable and human-readable aren't mutually
exclusive.
regards,
Rik
-- DMCA, SSSCA, W3C? Who cares? http://thefreeworld.net/http://www.surriel.com/ http://distro.conectiva.com/
- 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/