From owner-cvs-all@FreeBSD.ORG Tue Sep 13 18:06:20 2005 Return-Path: X-Original-To: cvs-all@FreeBSD.org Delivered-To: cvs-all@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3B3716A41F; Tue, 13 Sep 2005 18:06:20 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73E4F43D45; Tue, 13 Sep 2005 18:06:18 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j8DI6Lo5003839 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 13 Sep 2005 11:06:21 -0700 Message-ID: <43271516.9000808@root.org> Date: Tue, 13 Sep 2005 11:06:14 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Greg 'groggy' Lehey" References: <20050911002229.51F4916A471@hub.freebsd.org> <432382BC.5080105@root.org> <200509110310.36423@harrymail> <43255152.3000609@freebsd.org> <20050912165518.GA94181@dragon.NUXI.org> <20050913004536.GK53486@wantadilla.lemis.com> In-Reply-To: <20050913004536.GK53486@wantadilla.lemis.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, David O'Brien Subject: Re: Combined root, /var and /usr X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2005 18:06:21 -0000 Greg 'groggy' Lehey wrote: > I've been recommending and doing this for years. FWIW in the fourth > edition of "The Complete FreeBSD" I recommended 4 to 6 GB; I'd now say > that 8 to 10 is better. I also recommend a separate /var if you're > doing important things with it. Here's what I have on my two main > machines: > > === root@wantadilla (/dev/ttyp0) ~ 98 -> df > Filesystem 1048576-blocks Used Avail Capacity Mounted on > /dev/ad0s1a 9912 4211 4908 46% / > /dev/ad0s3h 51895 41842 5902 88% /home > > === root@echunga (/dev/ttyp4) ~ 29 -> df > Filesystem 1048576-blocks Used Avail Capacity Mounted on > /dev/ad0s1a 14873 7985 5698 58% / > /dev/ad0s1g 9916 3846 5276 42% /home > /dev/ad2s1h 188356 106658 66629 62% /src Large / means you have to wait for it to fsck before bg fsck can run on other filesystems. On my crashbox (laptop), that is unacceptable. /var on the same filesystem as / means that you're bound to have lots of problems found via fsck that you may have to review manually when a busy system crashes. With var separate from /, you can just blow it away (fsck -y) and get back to work. If you don't have a diskless server or livecd, having a separate / means you can boot and rebuild a fs with fsdb. With a combined partition, this is probabilistic. If you start getting block errors on your hard drive, separate partitions mean you can pull off the files still alive, remap bad sectors, and newfs. Try that with one large /. > In CFBSD IV I explain how / and /usr came to be: about 32 years ago, > they had / on an RK03 (0.5 MB), so they *had* to put the rest of the > system somewhere else. The fact that we still use a separate /usr has > something to do with the reliability of the Seventh Edition file > system See above for examples still valid today. > and something to do with not changing the way our grandfathers > did things (writing "return (FOO)" instead of "return FOO" is > another example). I think that one is more about consistency. return () is a keyword while exit() is a function. It's the same reason we don't write if(). -- Nate