From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 08:24:23 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 57E1516A41F for ; Mon, 29 Aug 2005 08:24:23 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED59343D49 for ; Mon, 29 Aug 2005 08:24:22 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from SMILEY (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 47F8D19F3B; Mon, 29 Aug 2005 01:27:53 -0700 (PDT) From: "Darren Pilgrim" To: "'C. Michailidis'" , Date: Mon, 29 Aug 2005 01:24:19 -0700 Message-ID: <000d01c5ac73$0e4fbb50$6b2a15ac@SMILEY> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <200508282330.09302.dinom@balstonresearch.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Importance: Normal Cc: 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 08:24:23 -0000 From: C. Michailidis >=20 [sysinstall FS sizing defaults] >=20 > <...> Isn't it safe to make some of the default sizes a=20 > wee bit larger? That is, a 256mb /tmp and /var doesn't seem=20 > "appropriate" if you have one of these massive modern disk=20 > drives. For christ's sake, I'd gladly give up a GB or two of=20 > /usr so I could build openoffice without needing to consider=20 > that I may need an extra few megabytes in /var at the time of=20 > the system install. >=20 <...> >=20 > Wouldn't it be smart to remove the hardcoded default sizes=20 > altogether and dynamically generate them according to a=20 > reasonable function? Probably, but a template for something like this isn't simple unless it's created as part of a general profile-based installer that would inform sysinstall of the machine's purpose in life. For example, a "workstation or Windows replacement" would need several extra GB in /usr whereas a server would get away with a much smaller /usr, but need those extra file-systems for logs, spools and other data. There are, however, some basic constants: If /usr, /var and /home are on another file-system, / doesn't need to be more than 150-200 MB. There just isn't that much in the root file-system. Assuming the default log retention and no spooling, /var will likely never grow past 50MB. Adding a mail, web, db or log server or increasing log retention will go well past that mark, but then such servers should have subordinate file-systems to handle the extra data. What comes with the OS will take less than 300MB in /usr. /usr/src and /usr/obj eat around 500 MB each. /usr/local eats around 1 GB for most servers and 3 GB on a desktop. /usr/X11R6 is empty if X isn't installed, the base Xorg server package is a few hundred MB and a desktop can need several GB. /usr/ports should have 1-2 GB just for distfiles on a desktop built from ports and 3 GB for work if you're building something huge, like KDE. I size /usr/ports to 6 GB on my desktop machines.