Tom Rauschenbach wrote:
>
> So I suggest that we discuss
> 1) which directories should be separate file systems
> 2) how big should they be
> 3) other stuff related to disk organization
My rules of thumb for assigning directories to filesystems
go something like this:
1. If I'll be hosed if a subdirectory fills up, put the parent
on a separate filesystem. (This means / and /tmp each go
on their own.)
2. If it's subject to a lot of activity, especially rapid
growth, put it on its own filesystem. (So /var and
/home get their own, too. In my case, so does /usr/local.)
3. If it's relatively static, but huge, give it a separate
filesystem. (There goes /usr, and maybe /opt.)
The result is that I usually have the following filesystems:
/
swap
/tmp
/var
/usr
/usr/local
/home
/ won't fill up since nothing else volatile shares its filesystem.
Filling /tmp won't break any other filesystems.
FWIW; YMMV.
--
#ken P-)}
Ken Coar <http://Golux.Com/coar/>
Apache Software Foundation <http://www.apache.org/>
"Apache Server for Dummies" <http://Apache-Server.Com/>
"Apache Server Unleashed" <http://ApacheUnleashed.Com/>
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
