LAMP server setup
 

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?

Thats' a very generic question if you don't provide more
detail about the hardware and the expected sizes of the site
and the database(s), and the potential growth of the lot.

In general it's a sensible thing to have logs on a separate
file-system (in case for instance /home would overflow) or
even (ideally) on a separate physical device, for performance
reasons. :}



Cheers,
Tink

It was the intention to be generic. Else I will ask questions related to the same subject every time (with minor differences).

boot-partition (any advantages in having that)
root-partition
server-partiton (both db and webpages)
home-partition

This will keep the data seperate from the system. Only question is the boot partition. Usefull or not?

/boot

It was very sensible back in the day when lilo couldn't touch stuff
beyond cylinder 1023 .. these days those limitations have gone away
to the best of my knowledge.


Cheers,
Tink