Me and libervisco were having a discussion about this earlier, so i figure i'll make a poll here. Do you use multiple partitions and mount them overtop of / or make one big / partition?
Well I usually have one small partition for /boot although there's no real technical reason behind that, I'm just used to it.
I also have a separate partition for home and the rest are data partitions.
The actual system is all on one partition so I don't have a separate /usr or /usr/local or stuff like that.
I guess I could say I'm on multiple partitions then, if you count boot and home.
I generally keep /home separate from everything else, thus, yea 2 partitions (not inc. swap of course). Actually, in this case I've gone a wee bit further with a data partition, where essentially ~/Documents is under. This means that data is completely separated from the system and thus config, even my own configuration in /home/.*
That's just me though.
That's much like what I have. My data partition is under /mnt/data and is completely independant from any systems installed on the hard drive. It is also the biggest partition because that's where stuff permanently accumulates (music, videos, backups, project files, archives, whatever..).
It's sort of my library.
/boot: Less risk of boot loader trouble in the future, especially removing a distro.
/home: Don't have to reconfigure things for a new distro.
/usr/local: Don't need to do things over for new distros, like /home.
/usr/local: Don't need to reinstall programs.
I never thought of that! that's a pretty cool idea..
i've been doing seperate partitions for / /boot /home /usr /var /tmp
i'll post my 'mount' after i get off this livecd.
Essentially you get the optimal power over your system when you split up everything under root. Therefore you'd have, for example /opt, /home/ /var and so forth all under different partitions.
Depending on how much you know about the Linux system and how it interacts with GNU/Linux this can be a great idea because you have optimal control over everything. If something goes wrong chances are you can isolate it, but in most cases this is something the average user, or rather, even most users would not explore.
That's the power of choice.
I've also heard /var is good for servers because it helps further avoid fragmentation problems.
I (normally) just use one partition.
I have a ~10GB /boot partition (the reason it's so big is that it was a spare partition, and I didn't want to partition further, so I used it as it was).
/srv for the server
/home/dylunio/files for files to share between distro's
everything else is in a / partition.
which is abut 20-30gig
which are both distros currently on the comp currently
on the desktop
on the server i have
both 40gig in size
Here's my setup.
/: Very small, usually 1GB or less. If there is a crash, it's less likely that data on the / partition will be corrupted if it is separated. It's also a performance issue since most everything on / is static. There's no need to mix it with partitions that are constantly being written to.
/usr: Since the / partition is small, I make this big.
/var and /tmp: Since these can both be written to without root privileges, it's good to keep them on a separate partition so that if a buggy program or a malicious script fills them to maximum capacity, there is no harm done. I keep them small, usually less than 1GB each.
/home: Large. Users can write to this, so I keep it separate.
/srv: Everything is served out of here. I keep it separate so that the data on it is less likely to be corrupted if there is an issue somewhere else on the system. It's also for organizational purposes.
You seem to have a really thought out system there. That must be on top of the top for security and stability, everything isolated and modularized. Very cool.
And that's a really good point about root stuff being mostly static..