On 3/28/06, <b class="gmail_sendername">Toshio Kuratomi</b> <<a href="mailto:toshio@tiki-lounge.com">toshio@tiki-lounge.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;">
I think Nicholas Mailhot had an extremely valid point: The<br>configuration format (key = value; <key>value</key>; etc) is not a major<br>stumbling block for a system admin. It's what the application<br>developers choose as the name for key and what they fill value with that
<br>make configuration files easy or hard to understand. Elektra and the<br>like are seeking to solve a problem that will only marginally aid a<br>system administrator in editing a config file from a text editor.</blockquote>
<div><br><br>Yeah, thats because Elektra main goal is not to help sysadmins, but to help unrelated programs to colaborate automaticaly. this way, helping the sysadmin is an inevitable consequence.<br><br>How many times you see regular non-sysadmin Windows users dealing with low level configurations? The answer is exactly "never", because the applications can do this task for themselves instead of asking the user to edit this and that configurations to make all work correctly.
<br><br>Of course Elektra adds a considerable amount of security and filesystem-like access permissions, compared to what Microsoft did with the their registry.<br></div><br><div><br>Avi </div><br></div>