<div style='font: 10pt "EngraversGothic BT", "Copperplate Gothic Light", "Century Gothic"; text-align: left; '>Of course, it depends on what the other admin factored out of the root partition. Anyway, the best solution would be to remove a secondary partition (with plenty of free space) that can be backed up, and create two more. One would be the replacement of the one you just clobbered (as a smaller size, of course), and the other would be a place to put one of the directories in root. Here's what my setup generally is:
/ - Very small (maybe only a few hundred MBs)
/var - Small (1GB or so)
/var/log - Medium (1-2GB, depending on how big the log files get)
/home - Large (especially on a server)
/usr - Very large (biggest cut)
/boot - (Optional) Extremely small (maybe 50MBs)
/tmp - symbolic link to /var/tmp
/usr/local - symbolic link to . [/usr] (fucking stupid idea for a directory anyway)
/usr/X11R6 - symbolic link to X11 (sometimes people uses these two interchangably)
/opt - symbolic link to /usr/opt
In any case, look at the current size of your directories before thinking of size recommendations. However, it is best to have as many partitions as you can, without running into space problems with any one of them. On the plus side, if one of the partitions fail, you're not going to lose everything. On the negative side, if you have too many partitions, you may run into space problems on one with major problems fixing it. (The general solution for the latter problem is move a big directory within the overloaded partition to one that has enough space, and then use a symbolic link.)</div>
Rosalina: But you didn't.
Robert: But I DON'T.
Rosalina: You sure that's right?
Robert: I was going to HAVE told you they'd come?
Rosalina: No.
Robert: The subjunctive?
Rosalina: That's not the subjunctive.
Robert: I don't think the syntax has been invented yet.
Rosalina: It would have had to have had been.
Robert: Had to have...had...been? That can't be right.