Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

This question already has an answer here:

Back before I knew what I was doing, I installed my Arch system with a 10 GB root and an 85 GB /home partition. Now my 10 GB root (where my pacman installs to) is full and I'm unable to get gparted running on my computer (it's a mac) to resize because my CD-ROM drive isn't working.

Is there an easy way to set my system up so that pacman installs and runs from my home partition where there is plenty of room?

share|improve this question

marked as duplicate by jasonwryan, slm, devnull, Anthon, strugee Apr 21 at 5:24

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

    
Only to mention: GParted also run form USB. –  user13500 Apr 20 at 17:19
    
Not on a Mac. I've tried everything to create a bootable gparted USB. I can't get it to load. –  JoshieSimmons Apr 20 at 17:26
    
Ah, ok. Too bad. –  user13500 Apr 20 at 17:30
    
Which filesystem? Maybe you can clean package cache, or move some big directory to another partition. –  uzsolt Apr 20 at 19:18
    
Oops. I actually forgot I asked that. Sorry. –  JoshieSimmons Apr 20 at 21:05

1 Answer 1

up vote 4 down vote accepted

Moving pacman is not the right approach.

You do, however, have a couple of options. All of them assume that you already have a full and tested backup of your data.

First, make sure that you have cleared all available space in pacman's cache with pacman -Sc: pass the second c for everything. There is a pacman tool for more fine-grained control fo this, see paccache --help for details.

If that still does not provide enough room, then you can resize your partitions with fdisk which is part of util-linux and is installed in the base group. There are a number of guides online for doing this.

The optimal solution, though, would be to grasp the nettle and do a full reinstall using LVM so that you have the flexibility to work around this issue (as well as other benefits like snapshotting) in the future. You could also fully encrypt your drive(s) while you are at it with LVM on LUKS.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.