From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 06:21:53 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4733A16A41F for ; Mon, 29 Aug 2005 06:21:53 +0000 (GMT) (envelope-from dinom@balstonresearch.com) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [216.148.227.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 154CC43D49 for ; Mon, 29 Aug 2005 06:21:53 +0000 (GMT) (envelope-from dinom@balstonresearch.com) Received: from [192.168.1.105] (pcp09554062pcs.verona01.nj.comcast.net[68.36.0.26]) by comcast.net (rwcrmhc11) with ESMTP id <20050829062152013005s39ge>; Mon, 29 Aug 2005 06:21:52 +0000 From: "C. Michailidis" To: freebsd-stable@freebsd.org Date: Mon, 29 Aug 2005 02:25:32 -0400 User-Agent: KMail/1.8.2 References: <200508282330.09302.dinom@balstonresearch.com> <20050829035729.GH88693@dan.emsphone.com> In-Reply-To: <20050829035729.GH88693@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200508290225.32394.dinom@balstonresearch.com> Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 06:21:53 -0000 On Sunday 28 August 2005 11:57 pm, you wrote: > For anything over a 9gb disk, I just make one big / partition. If you > sub partition, you'll always end up filling one (either /var or /tmp > quickly or /usr eventually) and wish you had picked different sizes. >=20 This is a very straight-forward way of doing things. Do you really think t= hat sysinstall should use a similar method when it attempts to auto-configu= re a slice? =46rom what I understand there are quite valid reasons why you would want a= seperate /, /var, /tmp, and /usr. For some reason I recall being informed= that more critical filesystems should reside closer to the beginning of th= e disk. I'm not too sure why, maybe someone would care to explain why it isn't the = best practice to have a single monster /? I have simply come to accept thi= s as fact and wouldn't mind a refresher myself. =2DDino *************************** Maude Lebowski: What do you do for recreation? The Dude: Oh, the usual. I bowl. Drive around. The occasional acid flashbac= k.=20