Just looking for suggestions here.........

I've pretty well decided on Slack13 64 which I will be going multilib after a reinstall. I currently have a VERY schizo partioning scheme going on due to clearing out 3 hdd's totaling 1.5TB and trying out a LOT of different distros with various home partitions a few swap partitions, blah, blah, etc.

I currently have my Slack 64 system set up entirely on one partition which I don't like for a permanent system. My new partition scheme for the slack install will be simple unless someone gives me a good reason to do otherwise: I don't want to waste disk space making / too big, but I would like to keep room for how it might need to grow over time given the following criteria:

full install
current
multilb
building various kernels and slackbuilds (including OOo) in /usr/src.

Just a thought: I have only two partitions for Slackware64-13.0, one for swap and one for /.

I run other all other Linux systems in VirtualBox, that is to say they all lie in ~/.VirtualBox. For instance at present I have Arch, Debian, Fedora, Mandriva and Xunbuntu installed, all in less than 19 gigs-bytes

I didn't set a /home partition but I frequently synchronize my backup of /home (and some other directories like /etc and /var) on an external hard disk.

I'm running Slack64-current with multilib, and I have about 100 slackbuilds.org packages installed, including openoffice and some games. I made the partition 16GB, and I'm using 9.5GB of it with everything installed. I would make it at least 12GB to give yourself a little headroom. If you have 4GB or more ram, you probably don't really need a swap partition either. I have 4GB allocated to virtual machines with 4GB left over and no swap partition, and I've never had a problem.

If you have enough ram, you could mount /tmp, /var/tmp, and /var/lock as tmpfs to keep them in memory and save a little space on /.

I'm pondering the same thing for my new box. I always have a /home partition just because it makes life a lot easier when upgrading, since I prefer the old "dust and start over" method. I'm thinking of partitions like this:

/
/swap
/home
/media

I know I can't really use "/media" but I haven't come up with a better name yet. Basically that's the place where I would dump my pictures, MP3s, games, et al. I was going to create three separate partitions (one each for /pictures, /games, and /MP3s) but I could see one or the other growing faster and then I'd run into artificial boundaries. Right now, I've got 4G in pictures, 15G in MP3s, and 9.5G in games. I'm leaning toward something like this for a 1TB drive:

/ 100G
/swap 4 or 6G
/home 400G
/media ~500G

There's going to be a ton of empty space on that drive for a long time . . .

I call your /media jpartition /data. There is alrady a /media for things like your optical drives. For fear of having to someday use windows for something I have an ntfs version of /data that I mirror files to called /data2 that I only mount manually for backing up. It's actually a seperate disk.

I did something similar. I have a 30GB solid state drive that I basically split in half between / and /home. Having user preferences on the SSD speeds up app launches and login times. And then I have a 750GB mounted as /storage. Inside /storage, I have separate folders for music, pictures, video, etc. Remember you can always use symlinks to achieve what you want. For example, link /pictures to /storage/pictures. I just have symlinks in my home folder so that ~/docs links to /storage/docs. I did the same thing for other folders that are normally on home but take a lot of space. I moved my downloads and .wine folders over to /storage and symlink to them in home. That way I keep as much free space as possible on the SSD.

Thanks. That's something I hadn't really thought of. That's going to come in handy when multilib quits building.........if it ev.....

I ended up doing this, FWIW:

/ 100G
/boot 100M
swap 6G
/home 300G
/stuff ~600G

Yeah, I know that "stuff" isn't too descriptive of a name, but hey. I put the boot partition in the in case I wanted to do anything crazy like encrypt partitions in the future.

1 members found this post helpful.

Yeah, I went with just 20G for / and I'm kind of regretting it, for the simple fact that I tend to run as root all the time. I'm going to have to move some things around, but all in all it's not hurting me. I still have 10G on /. In a way it helps me to keep a cleaner system. I have a bad tendency of backing the same things up 5 times when I go for major system/hardware changes and then my backups are just too unwieldy.