Date: Tue, 02 May 2000 17:48:29 -0400 From: Mitch Collinsworth <mkc@Graphics.Cornell.EDU> To: Peter.McGarvey@telinco.net Cc: FREEBSD-Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: BSD Theology: swap, /var, /tmp and /usr/tmp Message-ID: <200005022148.RAA31869@larryboy.graphics.cornell.edu> In-Reply-To: Message from Peter McGarvey <Peter.McGarvey@telinco.net> of "Tue, 02 May 2000 22:00:45 BST." <390F41FD.5880279E@telinco.net>
next in thread | previous in thread | raw e-mail | index | archive | help
IMHO this is really going to depend greatly on what the system is being used for. But then again that's why you're free to customize it how you want. If the system is for linux man, why not give him what he wants. If you're going to be supporting it maybe you want to make it look more like the rest of your systems. FWIW I've been managing BSD systems since 1985 and I've never seen a / partition less than 16 MB. My personal preferences: - make / big enough to hold a few extra kernels - err high on swap - make /usr big enough for what the OS puts there and don't let my users put anything there. It basically becomes read-only so doesn't need a lot of extra space. I alway leave some anyway. - put /var in it's own partition and link /tmp and /usr/tmp to /var/tmp or even to a separate /tmp partition. /var and /tmp if there is one get all leftover space. - separate /usr/local usually shared by all systems of the same OS. In the last few years disks have gotten much much bigger and I've started leaving a lot more room for slop in all partitions. It's a whole lot easier than having to shuffle things around later because you made / 10 MB too small. -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005022148.RAA31869>