From owner-freebsd-current Sat Dec 9 11: 5:36 2000 From owner-freebsd-current@FreeBSD.ORG Sat Dec 9 11:05:33 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 6326737B401 for ; Sat, 9 Dec 2000 11:05:33 -0800 (PST) Received: (qmail 23209 invoked by uid 100); 9 Dec 2000 19:05:32 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14898.33404.356173.963351@guru.mired.org> Date: Sat, 9 Dec 2000 13:05:32 -0600 (CST) To: "Brandon D. Valentine" Cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: Confusing error messages from shell image activation In-Reply-To: References: <14898.31393.228926.763711@guru.mired.org> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brandon D. Valentine types: > >There are other places where FreeBSD doesn't comply with the > >appropriate standard - packages vs. FHS, for instance. I claim that > We don't seek to comply with the arbitrarily devised linux filesystem > standard. We comply with hier(5), a standard steeped in decades of > tradition. Corrections first: The only place where FreeBSD fails to follow FHS (in my quick perusal of it) is in putting packages in /usr/local instead of /opt. You can't blame that part of FHS on Linux - I have as yet to see a Linux distro or package do it that way. No, this bit comes from commercial vendors, where it's also steeped in years of tradition. Rant second: FreeBSD *violates* years of traditions with it's treatment of /usr/local. /usr/local is for *local* things, not add-on software packages! Coopting /usr/local for non-local software creates needless complexity and confusion, which of course leads to needless pain. All of which has nothing to do with the question of whether we want to continue giving error messages that are wrong, or commit this patch and provide ones that are actually informative.