On Mon, Aug 3, 2015 at 5:21 AM, Helmut Jarausch <jarau...@skynet.be> wrote: > > Hi, > > some update yesterday which was not yet available on August, 1st, complete broke my system. > (Probably systemd-224) > > I couldn't do anything, especially no downgrading a package. > I had to revert to a backup from July, 29th. > > It turned out that something has installed /lib/udev while removing the symlink /lib -> /lib64 on my machine. > Therefore /lib did contains nothing but udev which broke my system completely. > > Has anybody made a similar experience or does anybody have explanation for that?
I have 2 versions on systemd in different machines: 218 and 222. Both of them install files in /lib and in /lib64. None of them touch the symbolic link, and I don't see how they could do it. That pertains to portage; when a package gets installed, it installs into /var/tmp (or wherever PORTAGE_TMPDIR points to), and then portage merges the files from PORTAGE_TMPDIR into the filesystem. I don't see how the symbolic link from /lib to /lib64 could be modified. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
