From owner-freebsd-arch@FreeBSD.ORG Sun Aug 7 17:30:04 2005 Return-Path: X-Original-To: freebsd-arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C145116A41F; Sun, 7 Aug 2005 17:30:04 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6356843D49; Sun, 7 Aug 2005 17:30:04 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 60A5E2A6C; Sun, 7 Aug 2005 12:30:03 -0500 (CDT) Date: Sun, 7 Aug 2005 12:30:03 -0500 To: "Simon L. Nielsen" Message-ID: <20050807173003.GA7290@soaustin.net> References: <42F47C0D.2020704@freebsd.org> <20050806092232.GA850@zaphod.nitro.dk> <42F489DC.1080400@freebsd.org> <20050807115927.GA851@zaphod.nitro.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050807115927.GA851@zaphod.nitro.dk> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: Colin Percival , "freebsd-arch@freebsd.org" Subject: Re: /usr/portsnap vs. /var/db/portsnap X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Aug 2005 17:30:04 -0000 On Sun, Aug 07, 2005 at 01:59:27PM +0200, Simon L. Nielsen wrote: > I don't really think that is a big problem, especially if the default > /var size is increased so it doesn't happen to total novices using > default install. > > If it turns out the be a problem, I think it would be better to have > portsnap warn the users when /var runs full e.g. with a URL to the FAQ > that describes how to work around the problem. I think we bought the /var size problem years ago, whenever the first use of /var/db was made. I don't think portsnap is going to be the make-or-break deal that having e.g. the default mysql location is -- certainly not enough to break with this standard usage. Now, whether we can do a better job with the defaults, and educating users, is another story :) mcl