On 3/29/06, <b class="gmail_sendername">Bill Crawford</b> <<a href="mailto:billcrawford1970@gmail.com">billcrawford1970@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
How does .ini format give you containers beyond the first level? By numbering<br>the keys? ugh.</blockquote><div><br>The ini format was a bad example because you get 2 dimensions only.<br>On Elektra you'll have something like this:
<br><br><span class="q">> > default-lease-time 21600;<br>> > subnet <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://10.202.46.0/" target="_blank">10.202.46.0</a> netmask <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://255.255.255.0/" target="_blank">
255.255.255.0</a> {<br>> > use-host-decl-names on;<br>> > option log-servers <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://10.202.46.2/" target="_blank">10.202.46.2</a>
;<br>> > host ws001 {<br>> > hardware ethernet 00:11:22:33:44:55;<br>> > fixed-address <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://192.168.0.1/" target="_blank">
192.168.0.1</a>;<br>> > default-lease-time 10000<br>> > filename "/lts/vmlinuz-2.4.26-ltsp-1";<br>> > }<br>> > }</span><br><br>system/sw/dhcpd/default-lease-time = 21600
<br>system/sw/dhcpd/subnets/10.202.46.0-24/use-host-decl-names = on<br>system/sw/dhcpd/subnets/10.202.46.0-24/options/log-servers = <a href="http://10.202.46.2">10.202.46.2</a><br>system/sw/dhcpd/subnets/10.202.46.0-24/hosts/ws001/fixed-address =
<a href="http://192.168.0.1">192.168.0.1</a><br>
system/sw/dhcpd/subnets/10.202.46.0-24/hosts/ws001/default-lease-time = 10000<br>
system/sw/dhcpd/subnets/10.202.46.0-24/hosts/ws001/filename = <span class="q">/lts/vmlinuz-2.4.26-ltsp-1<br></span>system/sw/dhcpd/subnets/10.202.46.0-24/hosts/ws001/hw = <span class="q">ethernet:00:11:22:33:44:55</span>
<br>
<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> The dhcp config file format is a much better match for a) the way people<br>think if they know the problem domain b) allows *hierarchy*. XML at least
<br>gets that right (and I *don't* think xml is the answer).</blockquote><div><br>Anyway, Elektra also provides standard ways for you to represent this hierarchy in an XML format, useful for exporting and importing.<br> </div>
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> But things change considerably<br>> when instead we deal with all configuration elements as keys and their
<br>> values in a filesystem like structure.<br><br> And this is the issue. Look at the mess that is SNMP MIBs. Can you read<br>those? Can you?</blockquote><div><br>Again, the point is not you (a human being) to read them, but make them accessible in an atomic way to any other (non-human) program.
<br><br><br>Avi</div></div>