Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 89CDD2E0038 for ; Fri, 6 Jun 2008 11:59:59 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 02546-08 for ; Fri, 6 Jun 2008 11:59:56 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from oxford.xeocode.com (unknown [62.232.55.118]) by developer.postgresql.org (Postfix) with ESMTP id BC4362E0035 for ; Fri, 6 Jun 2008 11:59:55 -0300 (ADT) Received: from localhost ([127.0.0.1] helo=oxford.xeocode.com) by oxford.xeocode.com with esmtp (Exim 4.69) (envelope-from ) id 1K4dOV-0003EG-Iq; Fri, 06 Jun 2008 15:58:19 +0100 To: "Peter Eisentraut" Cc: , "Aidan Van Dyk" , "Andreas Pflug" , "Decibel!" , "Tom Lane" , "Greg Smith" , "Josh Berkus" Subject: Re: Overhauling GUCS In-Reply-To: <200806061424.26830.peter_e@gmx.net> (Peter Eisentraut's message of "Fri\, 6 Jun 2008 14\:24\:25 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) X-Draft-From: ("nnimap+mail01.enterprisedb.com:INBOX.hackers" 23086) References: <48409D1E.3070208@agliodbs.com> <4846A483.8000001@pse-consulting.de> <20080604143548.GE14498@yugib.highrise.ca> <200806061424.26830.peter_e@gmx.net> From: Gregory Stark Organization: EnterpriseDB Date: Fri, 06 Jun 2008 15:58:19 +0100 Message-ID: <87ve0md304.fsf@oxford.xeocode.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/282 X-Sequence-Number: 119395 "Peter Eisentraut" writes: > And note that one of the major advances in X.org over XFree86 was that all the > useless garbage was removed from the configuration file, so that the final > and usable configuration fits on one screen, and you can even write it from > memory if you dare to. This is a good point, though I think the big advance wasn't in actually removing the garbage so much as making it irrelevant. That is, the advances were in making the server actually work automatically with less manual configuration. That's always a noble goal. I would be interested in what parameters people thought we could eliminate from the initial config file because the server normally gets it right anyways and users shouldn't have to adjust it anyways. (I'm specifically *not* referring to sections like the kerberos parameters which even if most users can leave them alone those who do use that feature *do* need to adjust those parameters because the server does *not* get them right automatically) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support!