From owner-freebsd-security Thu Jun 20 4:30:40 2002 Delivered-To: freebsd-security@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 92E7837B400 for ; Thu, 20 Jun 2002 04:30:34 -0700 (PDT) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 3.36 #1) id 17L09j-000J8m-00; Thu, 20 Jun 2002 13:31:15 +0200 Date: Thu, 20 Jun 2002 13:31:15 +0200 From: Sheldon Hearn To: Jonathan Arnold Cc: freebsd-security@FreeBSD.ORG Subject: Re: Apache 1.3.26 port Message-ID: <20020620113115.GA73571@starjuice.net> Mail-Followup-To: Jonathan Arnold , freebsd-security@FreeBSD.ORG References: <200206200658470001.031DD337@mail.speakeasy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200206200658470001.031DD337@mail.speakeasy.net> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On (2002/06/20 06:58), Jonathan Arnold wrote: > >data.default? Or are you saying that it was linked to data.default and you > >think (as well as I) that it should let you know before blowing > >data.default away (perhaps a make flag)? > > Yes, that's what I'm saying - it completely replaced data.default without > warning, and it shouldn't. I don't understand why it shouldn't. Is it because people are replacing the contents of data.default with their own content and leaving the symlink in place? If so, then the problem has to do with the fact that folks aren't using the symlinks and .defaults directories as intended. I think the intention was always for the operator to replace the symlink with either a directory or a symlink to the directory containing local content. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message