Tag Info

New answers tagged

0

I do not know Kali, so my answer is for vanilla Debian systems. I hope it is more or less the same for you. In order to install packages from foreign architectures, you have to enable the new architecture with the command dpkg --add-architecture i386 Then you update the lists of packages: apt-get update And then you should be able to install multiarch ...


1

Solved. I had export LD_LIBRARY_PATH="/usr/lib/plexmediaserver" in my .bashrc. /usr/lib/plexmediaserver had lots of dynamic libs, including libssl.so.1.0.0 and libexpat.so.1. So they were loaded instead of ones from /usr/lib and were causing problems. This problem has nothing to do with python actually, it would equally cause problems for any other program ...


1

For Redhat based systems do this: ldd [file you want to run] | > needed-packages Check out needed-packages file, make sure there are no path names in the library file names. If so remove them, so "/bin/lib/libx.so.1" change to "libx.so.1" Find out what package contains the library yum -y provides [lib name] Or put this into a script or run from cmd ...


2

The gem that used to be packaged as libusb-ruby or similar in distributions is most likely ruby-usb. At least your code worked fine when I used that gem. I would suggest that you add a Gemfile to your project and use RubyGems to manage those gems, as some of the less popular gems are often likely to drop out of distributions when no maintainer for the ...


7

For moving one program to other computer you have to move: 1) Executable file A simple way to finding commands path is type command. For example: type cal cal is /usr/bin/cal 2) Library dependencies You can find library dependencies with ldd command, But remember if you compiled a program from source the CPU Architecture of both server must be the ...


1

Basically, udev was brought into the whole systemd revolution, and became part of a larger, more complex system. Various changes incremented the interface, and required a jump from .so.0 to .so.1. Rather than supporting both the old interface and the new interface by providing both .so.0 and .so.1, the developers opted to say "fuck it, we'll make them all ...



Top 50 recent answers are included