From owner-freebsd-questions Sun Feb 28 12:55: 1 1999 Delivered-To: freebsd-questions@freebsd.org Received: from revolution.3-cities.com (revolution.3-cities.com [204.203.224.155]) by hub.freebsd.org (Postfix) with ESMTP id 309A01529A for ; Sun, 28 Feb 1999 12:54:58 -0800 (PST) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (kenn1187.bossig.com [208.26.241.187]) by revolution.3-cities.com (8.8.5/8.7.3) with ESMTP id MAA13155; Sun, 28 Feb 1999 12:54:36 -0800 (PST) Message-ID: <36D9AD0E.9F17CDA@3-cities.com> Date: Sun, 28 Feb 1999 12:54:38 -0800 From: Kent Stewart Organization: Columbia Basin Virtual Community Project X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Ben Smithurst Cc: Deepu Sebastian Joseph , freebsd-questions@FreeBSD.ORG Subject: Re: Swap Space References: <19990228181847.A20725@scientia.demon.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Smithurst wrote: > > Deepu Sebastian Joseph wrote: > > > I see that I might be just able to squeeze with: > > / 20 MB > > swap 20 MB > > /usr 80 MB > > /var 4 MB > > Its given some where /+/usr should be 100MB. > > why not just > > / 104MB > swap 20MB > > ? It will warn that having separate /, /usr and /var is a good idea, but > it won't insist that you make them separate. I've recently installed > FreeBSD on a machine with a small disk (400MB), and I just used > something like 30 for swap, 380 for "/". On my machine "/" is a separate > filesystem, but if you've got so little space it probably won't hurt to > stick them all on one filesystem. > > Perhaps someone can tell me why my method is a bad idea, if it is. There are times when you want the system to go down in a nice manner. When you fill the entire disk, it can be rather abrupt. I missed a digit one time and tried to edit a 50MB file with vi on our Cray. I filled what ever space vi used for tmp and the system stopped. Nothing that required tmp would run but they could still go in and rm my tmp files. Then they came down and asked me what I was doing and that was when I discovered the file was 10 times larger than I thought. There were 150 people that couldm't work because of me. If there are only a couple of people, I don't think it matters as long as you know what happens when you fill the drive and how to fix it. The plus, of course, is that you use the entire disk and not a preconceived notion of what your needs are. I find that sooner or later I push the size of a filesystem and all of the normal filesystems except swp (300MB) and proc are part of /. My user filesystem's /usr1 and /usr2 are all on separate 2.5-3.1GB drives. On of my projects fills the 1.25GB /usr1 slice and that was before anyone has started running the program and leaving run output files for analysis behind. -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message