> I'm planning on using LVM2. I'll be installing most of KDE 3.4. No > Gnome. I'll have a webserver and a mailserver running, but I've already > accounted the space required for them (as of right now) as 1GB in /var, > which of course will need to be expanded in future... to how much, I > don't know! But that's the point of using LVM2!
IMHO LVM2 is only valuable for creating partitions that need to cross disks (i.e. you have 2 100g disks but need a 200g partition). Using lvm2 simply to allow for future partition growth is overkill... No flames here please, I did say it is my opinion only ;-) > I have 768MB of RAM and so far I haven't seen it use any swap. So I'm > planning on a 256MB swap partition. Also, there will be a /boot which > would be about 50MB. You've got 80g, so double ram (the normal recommendation) shouldn't hurt you too much. If you ever get to the point that you run out of swap, you'll regret not having enough. As far as partitioning schemes, I come from the background that a full filesystem (especially /) comes at bad times and requires too much time to attempt to recover. To that end, I usually have around 10 different partitions: 1. / - large enough to hold the basic root entities (/etc, /bin, /sbin, and /lib). 2. /boot - 100M because I like to keep working kernels around for awhile. 3. /usr - Large enough to hold the /usr contents minus /usr/portage. 4. /usr/local - Separated to ensure that local installs don't kill the /usr partition. 5. /usr/portage - Keeps portage out of the /usr tree and simplifies /usr/portage partition resize when needed. 6. /opt 7. /var 8. /tmp 9. /var/tmp - Separated from /var so that temp space usage doesn't interfere with the spool (etc.) contents normally in /var. 10. /home On the mysql servers I also like to use a separate partition for the mysql data so I can easily grow the partition size when the database needs it. -- gentoo-user@gentoo.org mailing list
