Linux tmp-like dir in home folder

Two things:

1. /boot only needs to be about 256MB, 512MB if you really want to be safe. How many kernels do you really need?
2. For the love of [insert deity here] use LVM

In general I will use:

• First primary partition 256MB /boot (ext2)
• Second primary partition as physical volume (PV) in LVM
• Logical Volume /
• Logical Volume /home
• Logical Volume /usr (optional)
• Logical Volume /tmp (optional, prefer hdd over ssd)
• Logical Volume /var (optional, prefer hdd over ssd)
• Logical Volume swap (2 * RAM && <= 4GB)

Sizes depend on usage, but leave some (most) unused space in the volume group (VG) to expand any logical volumes that fill up.

This stems from LSB which says "/var contains variable data files. This includes spool directories and files, administrative and logging data, and transient and temporary files." but says this for /srv: "/srv contains site-specific data which is served by this system."

SuSE was one of the first disto's that I used that kept webroot's in /srv - typically Debian/Ubuntu/RHEL use /var/www - but also be aware that if you install a web application using yum or apt then they will likely end up in /usr/share. Also the packaging guidelines for Fedora say that a "package, once installed and configured by a user, can use /srv as a location for data. The package simply must not do this out of the box".

On balanced reflection I would say keep to /var/www - or you can do both by making /var/www a symlink to /srv/www. I know that on oracle RDBMS systems that I build I often create /u01 /u02 etc as symlinks to /home/oracle. The reason for this is that many DBA's expect to find things in /u01 and many others expect /home/oracle. The same can be said of Sysadmins in general - some will instinctively look in /var/www and some in /srv/www while others like myself will grep the apache config for the DocumentRoot.

Hope this provides some guidance for you.