On Thu, Jun 29, 2006 at 02:00:17PM -0700, John Brahy wrote: > > So am I going overboard? or am I missing any good partions. > > when I first posted Nick Holland replied with several reasons to have > multiple partions. Those being > security, fragmentation, protecting the filesystem from overfilling, > organization and space tracking.
It's hard to know if you're going overboard or not. To some degree it's a matter of personal preference, but mostly it's what the system will be doing. If mysql is there only for testing, then it can live in the normal /var partition. If mysql is heavily used it should not only have it's own partition, but you should move it to another disk (and even controller). Etc., etc... The more experienced I get, the better I am at choosing what to partition seperately, and how big to make the partitions. Some of the best advice is to partition what you think you'll need and leave the rest as free space. This gives you flexibility to adapt to unanticipated needs. I usually stick pretty close to the "standard" slicing, which gets you nice stuff like noexec, nosuid where you need it. Then I may do more partitions like for the mysql example above. I like things fairly simple. -- Darrin Chandler | Phoenix BSD Users Group [EMAIL PROTECTED] | http://bsd.phoenix.az.us/ http://www.stilyagin.com/ |
