Chad Carr wrote:
May I suggest that the config-db be maintained as a "config-tree," with
the root at /leaf-cdb (or something shallow like that) and keys may be
nested as deeply as needed by creating directory levels. I.e. you could
make the key
interfaces/eth0/ipaddr
like this:
echo -n "172.24.8.24" > /leaf-cdb/interfaces/eth0/ipaddr
I also like the idea of a config-tree, Chad. It's proven
itself useful for Linux a la /proc.
I wish the config-tree api to have significant lattitude in how
it displays the data:
a) Something along the lines of a -H argument the way "who -Hu"
prints out column headers.
b) The ability to dump var=value pairs to stdout.
Would you like to remark any furthur on how a tree is significantly
better than a single config-db file and how the tree would store a
variable's "type" information, for instance?
Matt.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
