On Thu, 6 Jan 2005 19:34:19 -0500, Paul W. Abrahams
On Thursday 06 January 2005 6:01 pm, B. Stia wrote:
Going to have a problem soon. My /usr partition is 94% full. (didn't realize that /usr/lib_64 was over 300 megs alone) When I originally setup my system I created several large partitions, some of which have lots of space.
I've set up several SuSE systems, and for a long time I thought it was wise to have separate partitions for the separate top-level partitions (/usr,/var,/home, etc.). But my experience now is that it's better to put everything in one partition to avoid precisely the pickle you're in -- one partition grows unexpectedly while the others still have plenty of room left.
I think the idea of having separate partitions for separate components of the top-level filesystem is really a historical remnant of the days when you needed to distribute the filesystem over several hard drives because a single drive wasn't big enough. Those days are gone. I know there's a case to be made for having /usr, say, mounted read-only so people don't muck with it, but really, you can do just as much by setting the permissions properly.
Maybe I'm missing something here. I'd like to hear other opinions.
Paul
I think the logic for different partitions has more to do with backups than anything else. / would get backed up most rarely. /usr a little more frequently /var and /home daily Also /home is good to have seperate so you can enforce quota's on a user only filesystem. /boot is a fairly new concept to me and I assume makes diagnosing boot issues easier. For a lot of my machines that don't have much critical data, I do as Paul suggested and just have one big filesystem. Greg -- Greg Freemyer