On 10/14/19 2:06 PM, Jared Stevens wrote:
We need to address the "no such file or directory" problem first.
Can you run:
ldd /bin/ls
Please and get back to us with the results? What you should get
(used on an SVN system):
renodr [ /sources ]$ ldd /bin/ls
linux-vdso.so.1 (0x00007ffe3b1e8000)
libcap.so.2 => /lib/libcap.so.2 (0x00007fcfff8c0000)
libc.so.6 => /lib/libc.so.6 (0x00007fcfff6fc000)
/lib64/ld-linux-x86-64.so.2 (0x00007fcfff8e2000)
I believe that your glibc installation might be corrupt. If your
glibc install is corrupt, try using this:
sln libc-2.30.so <http://libc-2.30.so> /lib/libc.so.6
And then running 'ldconfig'.
We've made some progress!
So the initial output of *'ldd /bin/ls'* was:
*bash: /usr/bin/ldd : /bin/bash: bad interpreter: No such file or
directory*
And the output of '*sin libc-2.30.so <http://libc-2.30.so>
/lib/libc.so.6'* was:
*bash: sin: command not found*
Regardless, I ran the*'ldconfig' *command anyways and after a brief
pause was given the following output:
*ldconfig: Cannot mmap file /usr/lib/libdbus-1.so*
HOWEVER, following this command I was finally able to run commands in
the /bin directory once again (such as 'ls'), and the output of*'ldd
/bin/ls'* changed to:
*linux-vdso.so.1 (0x00007ffea7f1a000)
libcap.so.2 => /lib/libcap.so.2 (0x00007f1b55ef5000)
libc.so.6 => /lib/libc.so.6 (0x00007f1b55d31000)
/lib64/ld-linux-x86-64.so.2 (0x00007f1b55f1f000)*
Unfortunately, the 'sin' command still outputs the same result. So now
it appears there is an issue with the libdbus file.
My PATH variable was also restored to how it was before these events
took place:
*PATH=/opt/rustc/bin:/usr/local/sbin:/usr/local/bin:/bin:/usr/bin:/sbin:/usr/sbin:/opt/ant/bin:/opt/jdk/bin:/opt/qt5/bin*
So while everything but that one error with libdbus looks back to
normal for the moment, I am afraid to try and install (or reinstall)
anything or change any file locations or settings until I know for
sure this issue is resolved.
What would you recommend my next steps going forward should be to fix
libdbus and ensure this issue has been fixed? Furthermore, as I have
made it this far and you have the experience, what should I do to
finish the transition from System V to systemd smoothly to avoid
another potential catastrophe such as this?
As for the dbus problem, try running:
ln -sv ../../lib/libdbus-1.so.3.19.11 /usr/lib/libdbus-1.so
Make sure that you have that library in /lib first
As for some further advice on the sysv to systemd transition, be
prepared to rebuild X from scratch. You might encounter problems if
ConsoleKit is installed too. If you have elogind installed, please
uninstall it. You'll want to rebuild Xorg Libraries, Xorg Applications,
and xorg-server at minimum (and that should do the trick...)
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
