# ./VirtualBox-5.0.14-105127-Linux_x86.run
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.............
VirtualBox Version 5.0.14 r105127 (2016-01-19T16:55:41Z) installer
Removing previous installation of VirtualBox from /usr/lib/virtualbox
root[0-virtualbox]#
root[0-virtualbox]# exit
exit
abcde[0-virtualbox]$ virtualbox
bash: virtualbox: command not found
abcde[0-virtualbox]$ ls -l /usr/bin/virtualbox
ls: cannot access /usr/bin/virtualbox: No such file or directory
root[0-virtualbox]# ls -l
total 81900
-rwxr-xr-x 1 cardio users 83865038 Feb 20 09:22 VirtualBox-5.0.14-105127-Linux_x86.run
root[0-virtualbox]# ./VirtualBox-5.0.14-105127-Linux_x86.run
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.............
VirtualBox Version 5.0.14 r105127 (2016-01-19T16:55:41Z) installer
Removing previous installation of VirtualBox from /usr/lib/virtualbox
root[0-virtualbox]# ls -l /opt/VirtualBox/VBox.sh
ls: cannot access /opt/VirtualBox/VBox.sh: No such file or directory
The output is still the same. Why is virtualbox not installing?
I found similar problem with trying to install virtualbox binary installation from slackonly repository into a fresh Salix - mate installation (kernel 3.10.17).
We don't know, you are not giving us enough information.
rsal wrote:The output is still the same
Please post the output that you see in the terminal. This will help us figure out want is going on.
It look as though you initially installed Virtualbox using the slackbuild for Slackbuild. Try uninstalling it using spkg -d. Then tried installing Virtualbox using the installer from Virtualbox
“The past was erased, the erasure was forgotten, the lie became the truth.”
― George Orwell, 1984
rsal wrote:The output is still the same. Why is virtualbox not installing?
I found similar problem with trying to install virtualbox binary installation from slackonly repository into a fresh Salix - mate installation (kernel 3.10.17).
Did you installed the kernel-source of the same kernel version before start the installation? e.g. for kernel-3.10.17, install the kernel-source 3.10.17
# We don't want an init-script building kernel modules.
# Use virtualbox-kernel.SlackBuild for this.
patch -d src/VBox/Installer/linux -i $CWD/vboxdrv.sh-setup.diff
root[etc]# ./rc.d/rc.vboxdrv setup
Not implemented! Please use the virtualbox-kernel.SlackBuild available at SlackBuilds.org instead.
In my opinion the slackbuild make the installation way to complicated. If the slackbuild author would have allow the installation of the vboxdrv.sh script, you would not be in this situation. That's why I always used the VirtualBox installer, much easier!
“The past was erased, the erasure was forgotten, the lie became the truth.”
― George Orwell, 1984