From owner-freebsd-arch@FreeBSD.ORG Sun Aug 7 17:49:58 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 DC88416A420; Sun, 7 Aug 2005 17:49:58 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68ED943D45; Sun, 7 Aug 2005 17:49:58 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j77I1uuc007460; Sun, 7 Aug 2005 12:01:57 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42F649C1.4050009@samsco.org> Date: Sun, 07 Aug 2005 11:49:53 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Linimon References: <42F47C0D.2020704@freebsd.org> <20050806092232.GA850@zaphod.nitro.dk> <42F489DC.1080400@freebsd.org> <20050807115927.GA851@zaphod.nitro.dk> <20050807173003.GA7290@soaustin.net> In-Reply-To: <20050807173003.GA7290@soaustin.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org 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:49:59 -0000 Mark Linimon wrote: > 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 We are already in agreement that the default size of /var will grow in sysinstall, the only thing left is deciding if it should grow for future use also (i.e. make it big enough to actually hold a crashdump). I think that portsnap is a very good feature and I'm ready to tout it for the 6.0 release. The technical problems, such as they are, are pretty insignificant and are just about solved. I think that we are pretty darn lucky to have someone with both the skills and motivation working on adding features that benefit our users. Scott