You are not logged in.
Pages: 1
Hello all, couldn't find a forum which really fit my issue so I'm putting it here.
I noticed in the latest update of filesystem, "filesystem 2012.2-5", that the changelog states "remove /lib". Now, I updated to this package with 'pacman -Syuu' and I still have a /lib populated with libraries. Upon further inspection, I noticed that most of the libraries in /lib were duplicated in /usr/lib32 (on a x86_64 system).
My question is this: is it okay to delete my /lib? I'm worried that future library updates will go in one of the /usr directories while the /lib directory will take precedence and shadow the updates.
There were a few libraries which I could not find anywhere else, notably the ld binary. Where is this supposed to be located in the new system?
Offline
First of all: don't delete /lib.
Second of all: everything is as expected, no need to do anything :-)
As for what's happening:
At some point in the not to distant future we want to move the last remaining contents of /lib into /usr/lib and replace /lib with a symlink to /usr/lib. For that to be possible we need to remove /lib from all packages. What you saw was just me removing it from the filesystem package, but the /lib folder will still remain on your system as long as other packages have files in there (at the moment it will probably only be glibc and the kernel modules (in /lib/modules)).
The reason you are seeing duplicates in /usr/lib32 is that those are the 32-bit versions of your libs on your 64-bit system so that you are able to run both 32-bit and 64-bit programs. You can't delete the 64-bit ones though, that will seriously break your system (as most important low-level processes will be 64-bit only) :-)
As to /lib/ld* that's the dynamic loader, which is responsible for finding and loading libraries dynamically. Removing that is probably the most efficient way of completely messing up your system, as virtually all binaries will stop working, so don't do that either ;-)
Offline
Pages: 1