How does .ini format give you containers beyond the first level? By numbering
the keys? ugh.
The ini format was a bad example because you get 2 dimensions only.
On Elektra you'll have something like this:
> > default-lease-time 21600;
> > subnet 10.202.46.0 netmask 255.255.255.0 {
> > use-host-decl-names on;
> > option log-servers 10.202.46.2 ;
> > host ws001 {
> > hardware ethernet 00:11:22:33:44:55;
> > fixed-address 192.168.0.1;
> > default-lease-time 10000
> > filename "/lts/vmlinuz-2.4.26-ltsp-1";
> > }
> > }
system/sw/dhcpd/default-lease-time = 21600
system/sw/dhcpd/subnets/10.202.46.0-24/use-host-decl-names = on
system/sw/dhcpd/subnets/10.202.46.0-24/options/log-servers = 10.202.46.2
system/sw/dhcpd/subnets/10.202.46.0-24/hosts/ws001/fixed-address = 192.168.0.1
system/sw/dhcpd/subnets/10.202.46.0-24/hosts/ws001/default-lease-time = 10000
system/sw/dhcpd/subnets/10.202.46.0-24/hosts/ws001/filename = /lts/vmlinuz-2.4.26-ltsp-1
system/sw/dhcpd/subnets/10.202.46.0-24/hosts/ws001/hw = ethernet:00:11:22:33:44:55
The dhcp config file format is a much better match for a) the way people
think if they know the problem domain b) allows *hierarchy*. XML at least
gets that right (and I *don't* think xml is the answer).
Anyway, Elektra also provides standard ways for you to represent this hierarchy in an XML format, useful for exporting and importing.
> But things change considerably
> when instead we deal with all configuration elements as keys and their
> values in a filesystem like structure.
And this is the issue. Look at the mess that is SNMP MIBs. Can you read
those? Can you?
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.
Avi
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
