Hi, On 07-03-19 11:45, Richard W.M. Jones wrote:
Actually it's more subtle. It didn't remove the files, but it did break something really fundamental, perhaps execv? Perhaps new binaries cannot link with the slightly older glibc? $ echo /usr/bin/ls /usr/bin/ls $ /usr/bin/ls -bash: /usr/bin/ls: No such file or directory
In my experience with breaking systems through glibc changes, the "No such file or directory" error is not about ls, it is about /lib64/ld-linux.so.2 missing. On my system I have: [hans@shalem ~]$ ls -l /lib/ld-linux.so.2 lrwxrwxrwx. 1 root root 10 14 dec 01:46 /lib/ld-linux.so.2 -> ld-2.28.so I suspect the symlink somehow ended up broken or missing due to the downgrade. Regards, Hans _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
