>>    Well, in systems used by groups of people (ie. not at home), /usr
>> and /usr/local (oft the same) grow and this gets replaced and someone
>> needs that and put it in and, oh where did the space go?
>
>Thats why I like having one big partition. On a 120G drive, I don't
>like deciding /usr/pkg needs N gigs and /home needs M gigs etc. I just
>make it one big partition and I rarely have trouble. I used to spend
>lots of time symlinking crud back and forth because of space
>misallocations -- it no longer happens...

you don't need to waste time and energy on symlinks...

...you can use null mounts (with the hidden option to make the df
output stay nice) if you need to move space around.

the one big filesystem thing *blows chunks* if you need repeatedly to
crash a machine (or if a machine is repeatedly crashing) in search of
a kernel bug.  with multiple filesystems, you can choose not to mount
or to mount ro some larger ones, so that the fsck time on reboot is
shorter.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
werdna@squooshy.com       * "information is power -- share the wealth."