My root seems to fill up quite quickly with Slackware and somehow 15G isn't enough - I don't believe I've put 8Gs of software in since I installed a month or two back, but I guess I have unless df -h is wrong!

I'm a little puzzled as to how this is happening. I uninstalled/reinstalled wine and used up 500megs apparently. No big deal I guess - I've got loads of spare space so I may as well make a new / directory on another HDD where I've got loads of space.

To change root, would it be sufficient to copy the existing root to the new partition, change the applicable entry in fstab and then mount -a?

what's in /tmp?

No, that would not be sufficient, and could possibly damage the system. To do it safely you should copy the partition, change fstab, and edit /etc/lilo.conf from a live cd. But before you do that, you should try to find out why it's happening in the first place. The first thing that comes to mind is /tmp. Second is /var. I'm assuming of course that they're on the root partition, and not seperate. If you could run
and post the output here so we can help you better, otherwise you'll likely run into the same problem eventually no matter how large you make the new root partition.

3 members found this post helpful.

Thanks for the replies.

/tmp is mainly full of the packages I've installed through sbopkg. I guess it's OK just to clear /tmp out - what's the best way safely to clean it up?

Using the same code reveals another 1.2G in /var, of which 1G is in /var/tmp.

If we assume that the full install was 7G, then there's still 4G or so to be accounted for; some will be a good number of AlienBob's packages, Flash, LibreOfffice as well as multilibs.

My system's working very well and I have nothing else weird going on.

You can just delete the packages if you are sure you won't need them. I usually save the packages in another folder and clean /tmp afterwards. Also, you can clear the sources cache from sbopkg, this will free some space in /var

1 members found this post helpful.

Thanks - cleaning /tmp and /var/tmp has got it back to 9.5G, probably where it should be.

If you have enough RAM, why not put /tmp in tmpfs? Then, when you reboot, it's all gone. Of course, that seems like a LOT of stuff from SBo that you've built. I hope you keep those pkgs.

2 members found this post helpful.

Thanks - I'll have a look at tmpfs.

I haven't put that much on though, maybe 1.5G decompressed but about 1G nominal.

/usr is about 8G; the larger entries are as follows

Is this about right?

I'd just toss /tmp/SBo and any cached packages out and leave the rest.