Received: (from major@localhost) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id JAA70030 for pups-liszt; Fri, 4 Feb 2000 09:38:03 +1100 (EST) Received: from smtp.sw.oz.au (firewall-user@smtp.sw.oz.au [203.31.96.1]) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id JAA70021 for ; Fri, 4 Feb 2000 09:37:54 +1100 (EST) Received: (from peterc@localhost) by smtp.sw.oz.au (8.8.8+Sun/8.8.8) id JAA19456; Fri, 4 Feb 2000 09:37:42 +1100 (EST) From: Peter Chubb MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14490.822.632534.491258@swag.sw.oz.au> Date: Fri, 4 Feb 2000 09:37:42 +1100 (EST) To: Greg Lehey Cc: UNIX Heritage Society , FreeBSD Chat Subject: Re: Why upper case configuration file names in BSD? In-Reply-To: <20000204084928.E26290@freebie.lemis.com> References: <20000204084928.E26290@freebie.lemis.com> X-Mailer: VM 6.71 under 21.1 "Gimme a 6 and 5!" XEmacs Lucid (patch 2) Comments: Hyperbole mail buttons accepted, v04.023. Sender: owner-pups@minnie.cs.adfa.edu.au Precedence: bulk >>>>> "Greg" == Greg Lehey writes: Greg> I've just been asked a rather unusual question: when you build a BSD Greg> kernel, the name of the configuration file is traditionally upper Greg> case. Does anybody have insight as to why this should be? The same reason that Makefile has an upper-case first letter -- so it appears early in an ls listing, rather than in the middle of a big long list. Peter C