On 2013 Apr 22, at 16:36 , Brian Mathis wrote: > Say what you will about them, but Microsoft realized this was a problem with > INI files a long time ago and migrated to the registry. You may scoff, and > one could say that early *implementations* of the registry left something to > be desired, but the *idea* of having a centrally managed config store with a > standard API used by all programs is what allows them to completely dominate > in the Enterprise market (and is what Puppet tries to achieve now). A lot of > the complex things you do with Puppet are complete child's play with Group > Policy.
Yes, because the AIX configuration DB and the mandatory commands (smit, smitty, et al) behind them never break for anyone. And for every job that is trivial with group policy, there's another job that is hell with group policy and trivial with Unix's more freeform approach to configuration. At $oldjob, I worked on the Unix security team and talked regularly with the Windows security team. Almost every week, there was a problem that one side found trivial due to the underlying OS, and it changed regularly which side had the easier time. Some things, Windows had a great and clean answer, other things, Unix was far simpler. A DB/API isn't the only answer, and in some cases, believe it or not, it's the wrong answer. ---- "The speed of communications is wondrous to behold. It is also true that speed can multiply the distribution of information that we know to be untrue." Edward R Murrow (1964) Mark McCullough mark.mc...@gmail.com _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
