Here's some real overkill for you:
Code:
Filesystem Size Used Avail Use% Mounted on
/dev/root 15G 7.4G 6.7G 53% /
/dev/sda3 19G 2.5G 15G 14% /home
/dev/sda5 19G 2.0G 16G 12% /usr/local
/dev/sda6 19G 977M 17G 6% /opt
/dev/sda7 19G 287M 18G 2% /var/lib/mysql
/dev/sda8 92G 33G 55G 38% /var/lib/virtual
/dev/sda9 92G 8.1G 79G 10% /spares
/dev/sda10 173G 220M 164G 1% /var/lib/pgsql
Here's why: when you get a new release of Slackware, the only partition it installs in is
/ (root). As you go through an installation, you add your partitions and you have the choice of formatting or
not formatting them as you go; bear in mind we're talking down the road here, not just convenience the first time out.
All the stuff I add goes in one of the above partitions (and a lot of it is huge). If I don't format those on installation, they're still sitting there when the new installation boots. This is good. Copying all multi-gigabytes of stuff somewhere then copying it back on, well, this is not good (don't fit on a heckuva lot of media, eh -- yeah, yeah, I can copy to a disk drive [and do, just in case]).
I also try to install any additional software in
/usr/local, never touching the distribution directories if at all possible (applications, like, say,
OpenOffice.org, go in
/opt by default, that's fine with me); that means I modify
SlackBuilds, but the reason I do it is so I don't have to do it again and again and again following the above partitioning scheme.
And, this is a new 64-bit box and the data bases haven't been built on it yet (they'll use just about 75% of the partition when loaded).
Saves me a lot of time and trouble.
Hope this helps some.
