On Wed, Jul 11, 2012 at 5:52 AM, David C. Rankin <drankinatty@xxxxxxxxxxxxxxxxxx> wrote: > So then since /lib is very much still a directory and not a symlink, then I > should: First, notice that /lib as a symlink is only in testing so far, so that might explain why you haven't seen it yet. It could be that your problem is unrelated... > (1) cp -a /lib /usr > (2) rm -r /lib > (3) ln -s /usr/lib /lib You probably want to be a bit more careful in order to make sure that the pacman db is not out of sync. That is, check who owns the files in /lib, if they are owned by glibc leave them alone, if they are owned by packages, then rebuild and reinstall the packages with the files in /usr/lib instead, if they are not owned by anyone then move them over manually as you described. Once that is done, you should be able to "pacman -S glibc" and it should create the symlink for you. Also check Allan's last email to dev-public, it is probably explained better there. > ... and the kernel modules for the running kernel ending up in /usr/lib/modules > and udev ending up in /usr/lib/udev -- are all OK with this? All official packages have their modules in /usr/lib/modules and their udev rules in /usr/lib/udev, in fact modules in /lib/modules will no longer work (if you are using testing). > And what is /usr > and /lib as _separate_ partitions on the main box? softlinks won't work across > partition boundaries -- so what then? Softlinks work across filesystem boundaries, no problem. -t
