Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!hellgate.utah.edu!helios.ee.lbl.gov!epb2.lbl.gov!envbvs
From: envbvs@epb2.lbl.gov (Brian V. Smith)
Newsgroups: comp.unix.ultrix
Subject: Re: Disk Partitioning, ULTRIX
Message-ID: <4306@helios.ee.lbl.gov>
Date: 28 Nov 89 22:05:05 GMT
References: <5001@buengc.BU.EDU> <2615@canisius.UUCP>
Sender: usenet@helios.ee.lbl.gov
Reply-To: envbvs@epb2.lbl.gov (Brian V. Smith)
Organization: lbl
Lines: 31

In article <5001@buengc.BU.EDU>, bph@buengc.BU.EDU (Blair P. Houghton) writes:
< In article <2615@canisius.UUCP> pavlov@canisius.UUCP (Greg Pavlov) writes:
< >
< >  The disktab file on a DECStation 3100 here includes the following in a
< >  comment at the top of the file:
< 
< [...default partitioning strategy deleted...]
< 
< > Ok, we pay attention to the "rule" for the 'c' partition.  But none of the
< > rest make any sense to us, at least most of the time.  Where does
these algo-
< > rithms come from ?  What is in ULTRIX that penalizes ignoring them ?
< 
< Sounds like some development-policy rule-of-thumb, kindof like the
< 9-to-1 resistance ratio for biasing a class-A common-emitter bipolar
< transistor amplifier stage.  It seems that, since the size of the 'a',
< (root) partition is roughly proportional to the size of the system,
< then the size of the 'b' (default swapping) partition would also be
< roughly proportional to the size of the 'a' partition.
< 

Seems to me like you should set the size of the swap partition to 
whatever you need in virtual memory.

Except to make sure that you have enough space in the g partition for /usr,
it seems kind of silly to restrict swap space or waste disk space by having
more than one needs just to follow some rule-of-thumb for sizing.
_____________________________________
Brian V. Smith    (bvsmith@lbl.gov)
Lawrence Berkeley Laboratory
I don't speak for LBL, these non-opinions are all mine.