SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
PS I just hope that you are actually running a 64-bit Slackware...
If not please first uninstall VBox then install the program for your arch.
To check, tell us what says:
Code:
uname -m
Also there is no need for a chroot environment. I have a bunch of VBox virtual machines running here, the host is Slackware 14.1 (32-bit), both 32-bit and 64bit guests work with no issue.
Code:
bash-4.2$ VirtualBox
bash: VirtualBox: command not found
Installing Virtualbox using the installerr script is relatively straight forward. All you need to so is to download the script, cd to the download directory, and the run the script as root. I'm not sure what you were trying to do by "Copied it and pasted it in Vi", but it is not needed to install using the script. Also, what you found was not the install script but rather what looks to me like remnants of a prior install. I suggest that you try the following
In a terminal cd to your users Download directory then do the following:
Did you first check that the file sh VirtualBox-5.0.12-104815-Linux_amd64.run was directory from where you typed the command?
Please type
Code:
ls -l |grep VirtualBox
from that directory and post the results.
PS just saw you last post. It's a very bad idea to mix stuff you get from slackbuilds.org with stuff coming directly from Oracle. You are just messing your system.
Last edited by Didier Spaier; 01-16-2016 at 12:01 PM.
bash-4.2# sh VirtualBox-5.0.12-104815-Linux_amd64.run
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.............
VirtualBox Version 5.0.12 r104815 (2015-12-18T16:16:41Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
Building the VirtualBox kernel modules
ln: target 'setup' is not a directory
VirtualBox has been installed successfully.
You will find useful information about using VirtualBox in the user manual
/opt/VirtualBox/UserManual.pdf
and in the user FAQ
http://www.virtualbox.org/wiki/User_FAQ
We hope that you enjoy using VirtualBox.
bash-4.2#
Did you first check that the file sh VirtualBox-5.0.12-104815-Linux_amd64.run was directory from where you typed the command?
Please type
Code:
ls -l |grep VirtualBox
from that directory and post the results.
PS just saw you last post. It's a very bad idea to mix stuff you get from slackbuilds.org with stuff coming directly from Oracle. You are just messing your system.
Running ls -l |grep VirtualBox doesn't return anything.
Either get everything I need from the SlackBuilds or the Vender website....don't mix?
Does that break things on the system?
bash-4.2$ locate whereis virtualbox-5.0.12-104815-linux_amd64.run
locate: fatal error: Could not find user database '/var/lib/slocate/slocate.db': No such file or directory
bash-4.2$
As others pointed out, you needed to run updatedb as root to get the database created.
To give you info on why this had to be done manually, Slackware, by default, will run updatedb (along with a few other upkeep items, namely logrotate and certwatch) at 4:40AM every day. If your computer is normally shut down at night, this prevents cron from running those and the daily maintenance won't occur. If this is the case, you may want to change cron's default time.
To change this, as root, run crontab -e and change the daily time to a time when the computer will normally be up and running (preferably when you're not expecting something disk heavy to be occurring). The first number is minutes and the next is hours, so changing it to 30 10 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null would change it to run the commands in /etc/cron.daily at 10:30AM every day.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.