Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I've used Slackware 10.0 and I'm currently using Slackware 10.1.
Both have default setups defining the location of both the database(s) and the webpages in /var.
I'm currently in the process of setting up a LAMP server and I'm wondering if the above setup is the way to go. Obviously people (who have a better understanding of servers than I have) have been thinking about this, but I still wonder.
I've read some howto's, but none of them seems to explain the reasoning behind a/the setup.
Logfiles (together with other stuff) usually end up in /var, possibly causing issues when they grow big or when the database or amount of uploaded files grow big. I see possible datacorruption or crashing applications coming with a setup like that.
Usually I don't bother to much about partitioning as I use old PCs with limited harddisk space. If possible, I will create a swap partition, a root partition and a home partition. Those machines are mostly used as desktops.
For this server, I'm trying to create a solid partitioning. Is it advisable to create a seperate partition and locate the databases and webpages there? Are there advantages in having a separate boot partion?