Re: *nix partitioning practices
"ISP Lists" <[email protected]>
| Newsgroups | gmane.org.operators.internet-access |
|---|---|
| Message-ID | <[email protected]> |
> [email protected] wrote: >> >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] >> On >> Behalf Of Jeff Willis >> Sent: Monday, June 15, 2009 1:41 PM >> To: [email protected] >> Subject: Re: *nix partitioning practices >> >>> [email protected] wrote: >>>> 8GB - SWAP (4GB RAM) >>>> 1GB - / (root) >>>> 15GB - /var (qmail puts everything in there) >>>> 10GB - /usr (base binaries and ports) >>>> 10GB - /usr/local (additional binaries I install) >>>> 200GB - /home I used to just have one home fs, but I found that it >>>> 200GB - /home2 makes for very long amanda restores for a customer >>>> site >> >> >>> I would also add a /tmp partition. Having root fill-up isn't pleasant >>> plus having /tmp on a separate partition means the root file system is >>> changed less often so fsck is faster and more reliable after an unclean >>> shutdown. >> >> Agreed. I'd also point out that having a separate partition for /tmp >> allows >> you to set /tmp as noexec which foils a healthy percentage of script >> kiddie >> exploit scripts. >> >> Andrew >> > I always set up with /boot, /, /tmp, /home (where users dump things) and > /var (where Linux dumps things). That covers most of the accidental > system disk fill ups. > SG > Since /var/log is a traditional logging destination, server distros in linux are often built with that as a separate partition - again to avoid having a logging spree fill up /var or / and gumming up the box. BTW, I really like the noexec on /tmp idea!!!!!!! -- Eat sushi frequently. - Avi [email protected] is the human contact address. [email protected] is the list posting address. See below URL for subscribe/unsubscribe and list options: http://inet-access.net/mailman/listinfo/list