On Mon, Jan 29, 2001 at 07:20:12PM -0500, David B. Harris wrote: > To quote ktb <[EMAIL PROTECTED]>, > # I would add /var to this list. The reason being is if you run > something > # like squid and don't manage it right it will bring your system down if > # it grows too large. Maybe with todays large HD's it doesn't matter as > # much but I've had it happen. Log files can get large also. Course if > # you are on top of it there isn't a problem but not everyone is, > # especially in the beginning:) In addition take a look at - > # http://www.linuxgazette.com/issue54/stoddard.html > # There is a little section on partitioning for a gateway. There are > good > # reasons for having more than 3 partitions. > > That's the entire point - "if you run something like squid and don't > manage it right" ... > > *IF* you run *something like squid*. > > When you over-partition, you *really* screw up versatility. Until they > know what they're using their system for, versatility is key. >
With todays large HD's in some sense both of our positions are moot. A one gig /var partition would be insane for a home user. Enough room for versatility and months of bad squid administration. Of course not everyone has large drives to work with. I guess it comes down to either you learn how to choose the size of your partitions in the beginning or you don't. You choose between versatility and security. Personal choice. kent -- I'd really love ta wana help ya Flanders but... Homer Simpson
