This happened just after an upgrade of glibc-* on Slint64-14.2 (but I don't know if/how this can be related to that):
Code:
ls -ltr /old/var/log/packages
<snip>
-rw-r--r-- 1 root root 23255 juil. 1 05:36 glibc-2.23-x86_64-2_slack14.2
-rw-r--r-- 1 root root 263554 juil. 1 05:36 glibc-i18n-2.23-x86_64-2_slack14.2
-rw-r--r-- 1 root root 1102 juil. 1 05:36 glibc-profile-2.23-x86_64-2_slack14.2
-rw-r--r-- 1 root root 8586 juil. 1 05:37 glibc-solibs-2.23-x86_64-2_slack14.2
The system doesn't find files like /bin/bash anymore.
This is also what it says when I try to chroot from another one, even though the binaries /bin/bash seem identical according to stat and after having copied /bin/bash from a working (same arch and version) to the broken system. Perms and ownership in /bin seem correct.
I have no idea what happened, any clue or thing to do to investigate appreciated.
EDIT. The broken system gets a kernel panic just after "fast init done". It says "kernel panic: not syncing: no working init found. Try passing init= option to kernel. See linux/Documentation/admin guide/init.rst for guidance".
This message occurs when booting a 4.10 kernel as well as sith 4.4.38 (only the link to the doc differ).
EDIT 2. Now solved, re-installing the new glibc-solibs with "installpkg --root /rootofbrokensystem glibc-solibs-2.23-x86_64-2_slack14.2". It seems that the "doinst.sh" didn't work as expected.
Now I have to investigate what happened, trying the upgrade another system. Maybe there is an issue using spkg instead of installpkg in this specific case? I will report my findings.
EDIT 3: I confirm that spkg didn't work as expected. It said
Code:
WARNING: Post-installation script failed. (32512)
I will reboot to repair from another system as now:
Code:
root[/home/didier]# installpkg -i glibc-solibs-2.23-x86_64-2_slack14.2.txz
bash: /sbin/installpkg : /bin/sh : mauvais interpréteur: Aucun fichier ou dossier de ce type
EDIT 4: posted a warning and a fix in the
sticky Slint thread and
in the Slint forum @ Salix.
