<br><br><div><span class="gmail_quote">On 9/26/07, <b class="gmail_sendername">Mike Perkins</b> <<a href="mailto:mikep@randomtraveller.org.uk">mikep@randomtraveller.org.uk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Brett Kosinski wrote:<br>><br>> Um... huh? How is, say, a standardized location for configuration files<br>> and their formats, along with an API to ease the construction and<br>> maintenance of said files, any different than what we have now, aside
<br>> from making things sane and consistent?<br>><br>> Besides, I'd love to hear how /etc solves these "concurrency and access<br>> control issues" which you allude to.<br>><br>Because each app that wants to read/update it's config just opens a single file
<br>(or group of files under a dedicated catalog) instead of contending for the same<br>resource, i.e. the registry hive that's got everything in it. Every app has a<br>different file, so no concurrency arises.</blockquote>
<div><br>What part of "standardized location for configuration files and their formats, along with an API to ease the construction..." don't you understand? I explicitly reject the centralized database model that Microsoft has chosen, instead opting to represent the same data in the filesystem itself, much as we do now, only with a proscribed directory structure and file format.
<br><br>Think about it. The registry is what? A hierarchical arrangement of key-value pairs, essentially. There is *nothing* about that model that can't be represented in the filesystem itself.<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;">
Further, each text file in /etc is human-readable, and reasonably easy to find,</blockquote><div><br>Again, apparently you didn't read what I wrote. This is precisely how things would work if I had my way, just like today. It's all theoretical, of course, but... :)
<br><br>Personally, I think you're still mistaking the concept of a "centralized configuration repository" with the Windows registry. The latter is an exceedingly poor an implementation of the former. The former, however, is not a fundamentally bad idea, if done right. Which was my point at the outset.
<br><br>Now, shall we move on to counting the number of angels that can dance on the head of a pin? ;)<br><br>Brett.<br></div><br></div><br>