The reason that "echo" works while other commands doesn't is that
"echo" is a part of your shell - think of "echo" in the same way you
would the "*" wildcard character for path expansion. There's no binary
executable file on your system for either command/character.
To solve your problem, running ldconfig is the first thing that I (and
apparently you!) thought of. Other potential ideas/solutions:
Check the contents of $LD_LIBRARY_PATH - it's a "considered harmful"
means of adding paths on which dynamic libraries can reside. Check for
anything that looks funky/out of place (eg a path to some temporary
directory left-over from upgrades).
Check for duplicate binaries in your system - changes in the
environment could be causing some of your terminals to pick up the
correct binary, and other terminals to be grabbing a bad/outdated
binary that's still hanging around in your $PATH.
Actually, before doing that, check out your $PATH in an xterm and in a
virtual terminal. Are they identical?
Try to figure out which shell is being run as another possible problem
point. Is xterm firing up bash while your virtual terminal is digging
up a fossilized /bin/sh?
On 5/6/07, Dave Edwards <dle [ at ] sympatico [ dot ] ca> wrote:
I am experiencing strange buggy behaviour after some upgrading. I'll use points
for the sake of brevity.
- upgraded Dapper -> Edgy -> Feisty
o Dapper -> Edgy via network
o Edgy -> Feisty reinstall with desktop CD
o in Edgy -> Feisty reinstall, I preserved my home partition and data
- most everything is fine, *except*
- I found when I ssh from work to home, most commands return complaints re
missing libraries
- Examples:
$ ls
ls: error while loading shared libraries: librt.so.1: cannot open shared object
file: No such file or directory
$ locate librt.so.1
locate: error while loading shared libraries: libc.so.6: cannot open shared
object file: No such file or directory
$ strace ls
strace: error while loading shared libraries: libc.so.6: cannot open shared
object file: No such file or directory
$ cat .bashrc
cat: error while loading shared libraries: libc.so.6: cannot open shared object
file: No such file or directory
- not *all* commands
$ echo This is weird.
This is weird.
- this problem also occurs in virtual terminals, Ctrl-Alt-F1 etc.
- those files *do* exist, as can be discovered from a local GUI terminal, e.g.
gnome-terminal or xterm, in which everything runs sans problem
- this occurred after both Dapper -> Edgy via the network,
and after Edgy -> Feisty reinstall
- have manually run ldconfig, but it does not clear up the problem
- have also rebooted a couple times since reinstall. no help.
I will appreciate any advice or insight you might have.
Cheers,
Dave.
--
Dave Edwards <dle @ sympatico.ca>
Freelance and Technical Writer,
With Special Interest in Open Source Software
http://bigStory.homelinux.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGPjD8sLIVno42AyARApiGAJ4kSTeEWBe0SL7fXOF51aKBIHNgzACglffv
D1Ux+Vxm8IE6khr4oCnORzw=
=M9e7
-----END PGP SIGNATURE-----
_______________________________________________
Linux mailing list
Linux [ at ] lists [ dot ] oclug [ dot ] on [ dot ] ca
http://www.oclug.on.ca/mailman/listinfo/linux
--
Evil will always triumph, because good is dumb