I want to know which fuse version do I have, when attempting to execute:
locate -i -r /fuse
I get:
/lib/modules/3.0.0-12-generic/kernel/fs/fuse
/lib/modules/3.0.0-12-generic/kernel/fs/fuse/cuse.ko
/lib/modules/3.0.0-32-generic/kernel/fs/fuse
/lib/modules/3.0.0-32-generic/kernel/fs/fuse/cuse.ko
/usr/include/fuse
/usr/include/fuse.h
/usr/include/fuse/cuse_lowlevel.h
/usr/include/fuse/fuse.h
/usr/include/fuse/fuse_common.h
/usr/include/fuse/fuse_common_compat.h
/usr/include/fuse/fuse_compat.h
/usr/include/fuse/fuse_lowlevel.h
/usr/include/fuse/fuse_lowlevel_compat.h
/usr/include/fuse/fuse_opt.h
/usr/include/linux/fuse.h
/usr/lib/pkgconfig/fuse.pc
/usr/share/app-install/desktop/fuse-emulator-gtk:fuse-gtk.desktop
/usr/share/app-install/desktop/fuse-emulator-sdl:fuse-sdl.desktop
/usr/share/app-install/icons/fuse.png
/usr/share/doc/fuse-utils
/usr/share/doc/libfuse-dev/examples/fusexmp.c
/usr/share/doc/libfuse-dev/examples/fusexmp_fh.c
/usr/share/initramfs-tools/hooks/fuse_utils
/usr/share/lintian/overrides/fuse-utils
/usr/share/man/man1/fuser.1.gz
/usr/share/man/man1/fusermount.1.gz
/usr/src/linux-headers-3.0.0-12/fs/fuse
/usr/src/linux-headers-3.0.0-12/fs/fuse/Kconfig
/usr/src/linux-headers-3.0.0-12/fs/fuse/Makefile
/usr/src/linux-headers-3.0.0-12/include/linux/fuse.h
/usr/src/linux-headers-3.0.0-12-generic/include/config/fuse
/usr/src/linux-headers-3.0.0-12-generic/include/config/aufs/br/fuse.h
/usr/src/linux-headers-3.0.0-12-generic/include/config/fuse/fs.h
/usr/src/linux-headers-3.0.0-12-generic/include/linux/fuse.h
/usr/src/linux-headers-3.0.0-32/fs/fuse
/usr/src/linux-headers-3.0.0-32/fs/fuse/Kconfig
/usr/src/linux-headers-3.0.0-32/fs/fuse/Makefile
/usr/src/linux-headers-3.0.0-32/include/linux/fuse.h
/usr/src/linux-headers-3.0.0-32-generic/include/config/fuse
/usr/src/linux-headers-3.0.0-32-generic/include/config/aufs/br/fuse.h
/usr/src/linux-headers-3.0.0-32-generic/include/config/fuse/fs.h
/usr/src/linux-headers-3.0.0-32-generic/include/linux/fuse.h
/var/lib/dpkg/info/fuse-utils.conffiles
/var/lib/dpkg/info/fuse-utils.list
/var/lib/dpkg/info/fuse-utils.md5sums
/var/lib/dpkg/info/fuse-utils.postinst
/var/lib/dpkg/info/fuse-utils.postrm
/var/lib/dpkg/info/fuse-utils.preinst
Any idea where the information I need is located ?
You can get the version of the fusermount utility like this:
fusermount -V
The selected answer should be jdlourenco's one.
Boh's anwser isn't bad, but not clear enough for newbies and the shell line is too specific (in my case, Ubuntu 16.04, no results)
On Debian / Ubuntu, check using dpkg
dpkg --get-selections | grep fuse
In addition to fusermount -V, as presented by #jdlourenco, you can also run sshfs -V. It shows the fusermount -V output as the last line.
Example runs and output on my Ubuntu 20.04 machine:
$ fusermount -V
fusermount3 version: 3.9.0
and:
$ sshfs -V
SSHFS version 3.7.1
FUSE library version 3.9.0
using FUSE kernel interface version 7.31
fusermount3 version: 3.9.0
Other References:
My answer here: Ask Ubuntu: How to prevent SSHFS mount freeze after changing connection after suspend?
Related
I met this error when compiling a modified caffe version.
OpenCV static library was compiled with CUDA 7.5 support. Please, use the same version or rebuild OpenCV with CUDA 8.0
I have some old code may not compatible with CUDA8.0, so I want to change my cuda version for this error.
I modified my ~/.bash_profile like this
# export PYTHONPATH=$PYTHONPATH:/usr/local/cuda-8.0/lib64/
# export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-8.0/lib64
export PYTHONPATH=$PYTHONPATH:/usr/local/cuda-7.5/targets/x86_64-linux/lib/
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-7.5/targets/x86_64-linux/lib/
But it did't work. Still the same error. What should I do? Thanks.
Change your CUDA soft link to point on your desired CUDA version. For example:
ll /usr/local/cuda
lrwxrwxrwx 1 root root 19 Sep 06 2017 /usr/local/cuda -> /usr/local/cuda-8.0/
Simply relink it with
Update:
If the symlink already exists, use this other command:
[jalal#goku ~]$ ls /usr/local/cuda
lrwxrwxrwx. 1 root root 20 Sep 14 08:03 /usr/local/cuda -> /usr/local/cuda-10.2
[jalal#goku ~]$ sudo ln -sfT /usr/local/cuda/cuda-11.1/ /usr/local/cuda
[jalal#goku ~]$ ls /usr/local/cuda
lrwxrwxrwx. 1 root root 26 Sep 14 13:25 /usr/local/cuda -> /usr/local/cuda/cuda-11.1/
ln -s /usr/local/cuda-7.5 /usr/local/cuda
(With the proper installation location)
Perhaps cleaner:
sudo update-alternatives --display cuda
sudo update-alternatives --config cuda
Maybe a bit late, but I thought it might still be helpful for anyone who comes across this question. I wrote a simple bash script for switching to a different version of CUDA within the current bash session: https://github.com/phohenecker/switch-cuda
This solution explains how you can have multiple different cuda versions installed, i.e. 10.2, 11.3 and 11.6 and switch between them. It's an extension of #w.t and makes use of update-alternatives.
Afaik, after cuda 11.x the installations on Ubuntu 20.04 cuda installations will be added to the update-alternatives maintenance automatically.
Let's say you installed cuda 10.2, cuda 11.3 and cuda 11.6 (following the official nvidia installation guide: https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html). They will all reside in:
/usr/local/cuda-10.2/...
/usr/local/cuda-11.3/...
/usr/local/cuda-11.6/...
Your update-alternatives will have two entries:
$ sudo update-alternatives --query cuda
...
/usr/local/cuda-11-3 - priority 113
/usr/local/cuda-11-6 - priority 116
Solution 1: If you want to make use of the update-alternatives make sure that your cuda symbolic link points to /etc/alternatives/cuda.
# Change the symbolic link target.
$ sudo ln -sfT /etc/alternatives/cuda /usr/local/cuda
# Check the path.
$ ll /usr/local/cuda
lrwxrwrwrwx 1 root root /usr/local/cuda -> /etc/alternatives/cuda/
Now, all that is left is to make sure /etc/alternatives/cuda points to the version you want to use, e.g. 11.3.
You can make that update with:
$ sudo update-alternatives --config cuda
and follow the instructions to change the version.
Check the path:
$ ll /etc/alternatives/cuda
lrwrwrwrwx root root /etc/alternatives -> /usr/local/cuda-11.3
almost done.
And always make sure to load the correct library PATHs in your ~/.bashrc.
Solution 2:
Directly set your /usr/local/cuda symbolic link to the correct version.
$ ln -sfT /usr/local/cuda-11.3 /usr/local/cuda
Reboot your machine and double check everything is set properly:
$ nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2021 NVIDIA Corporation
Built on Mon_May3 19:15:14_PDT_2021
Cuda compilation tools, release 11.3 V11.3.109
Build cuda 11.3.r11.3/compiler.29920130_0
I solved the problem finally.
Modifying ~/.bash_profile to change the path to CUDA is the correct way. But when you changed the file, you need to relaunch the bash.
Simply source ~/.bash_profile won't work. Because source will only append the content in the file to the already existed path rather than cover it.
I switched from cuda 10.2 to 11.7. export PATH=/etc/alternatives/cuda/bin:$PATH did the trick for me. I found the solution in this thread: https://stackoverflow.com/a/40599478/7924573
I run this command:
sudo dkms autoinstall -k 3.11.6-1-ARCH
and have error:
Error! echo
Your kernel headers for kernel 3.11.6-1-ARCH cannot be found at
/usr/lib/modules/3.11.6-1-ARCH/build or /usr/lib/modules/3.11.6-1-ARCH/source.
Error! echo
Your kernel headers for kernel 3.11.6-1-ARCH cannot be found at
/usr/lib/modules/3.11.6-1-ARCH/build or /usr/lib/modules/3.11.6-1-ARCH/source.
what should I do?
Do you actually have kernel headers for the stock repo kernel installed? They're not installed by default, so unless you explicitly did, you probably don't. Try running:
pacman -Sy linux-headers
and see what happens.
Also, does the kernel version you have match with what you're trying to run against it? If the above doesn't fix the problem, please post the output of
uname -a
I'm compiling erlang otp from source like following:
./configure --with-dynamic-trace=systemtap
But it reports error:
checking for dtrace... no
configure: error: No dtrace utility found.
I think systemtap is for linux usage and it is different from dtrace, am I right?
After installed dtrace Now the error is:
dtrace: failed to compile script emulator/beam/erlang_dtrace.d: Preprocessor not found
configure: error: Could not precompile erlang_dtrace.d: dtrace -h failed
configure: error: /root/otp/erts/configure failed for erts
Which distro are you using? I'd forget using DTRACE, it will be a bit harder to make it to work than Systemtap (at least it was for me). I'm using Systemtap and it works perfectly.
If you are not using Fedora/RH you should patch your kernel with UTRACE or use a kernel >= 3.5 with UPBOBES enabled.
To verify if your kernel has UTRACE/UPROBE enabled run this:
grep UTRACE /boot/config-$(uname -r)
or
grep PROBES /boot/config-$(uname -r)
For example, in my machine (Ubuntu 12.04 with Mainline kernel 3.5):
$ grep UTRACE /boot/config-$(uname -r)
$
$ grep UPROBES /boot/config-$(uname -r)
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_UPROBES=y
You should also have systemtap installed. The version shipped with Ubuntu (my case) is quite old, so I compiled it from source (traditional configure/make/make install). You can get it here:
http://sourceware.org/systemtap/ftp/releases/
I'm using version 1.8.
Then try to recompile it again. It should work.
Regards
After installing systemtap(sudo apt-get install systemtap), exiting or logging out from the current shell session then logging in may help.
Also, you may try using kerl.
I cant tell if openmp is installed in this fresh install of centos I just put on with the developer tools.
I tried to run ldconfig -p | grep openmp and I dont see it listed.
Is it available for centos with that version of gcc?
Thanks
/sbin/ldconfig -p | grep gomp
library is call libgomp
Try:
$ ldconfig -p | grep -i "gomp"
libgomp.so.1 (libc6,x86-64) => /usr/lib64/libgomp.so.1
Basically, it's called gomp... GCC's OpenMP.
The alternative is to compile a hello world openmp program; if it doesn't work, it isn't installed.
Search "yum search gomp" this way on a Red Hat distro. To find out what the groups are use "yum grouplist | less". This pages the output so you can see the complete list. You will notice which groups are installed and available. Of course you can always use "yum help".
Not familiar with CentOS or yum, but take a stab with this:
yum list installed | grep "penmp"
Good luck!
How can i determine the Linux version (distribution) for which was compiled rpm packet?
I believe this is what you are after.
$ rpm -q gnome-speech --queryformat '%10{NAME} %20{VENDOR} %20{RELEASE} %20{ARCH}\n'
gnome-speech Red Hat, Inc. 1.fc6 i386
$ rpm -q hwdata --queryformat '%10{NAME} %20{VENDOR} %20{RELEASE} %20{ARCH}\n'
hwdata Red Hat, Inc. 1.el5 noarch
There are lots of nifty bits you can go after with queryformat, see this guide for a reference.
General reference on rpm-philosophy-multi-architecture.
There is no such ways to determine the OS name and version from the content of the file.
Normally a RPM file name contains all these details. According to the RPM file naming convention the file name must be like :
name-version-release.architecture.rpm
Please check this link for details.
You can use rpm -q to get the OS data from the OS tag in the RPM, but you need to specify a queryformat as it is not in the normal -i output. You can use -p to refer to a specific RPM file for the testing.
$ rpm -q -p myfiletotest.rpm --queryformat '%10{NAME} %10{OS} %10{VERSION} %10{RELEASE} %10{ARCH}\n'
mypackage linux 2.2.10 1_14.el6 x86_64
The OS name is the second field in this output. The RPM does not distinguish between releases of the OS though; you will only see 'linux', 'aix', 'darwin', and so on - not 'centos-6'.