Having Trouble With VBox Script

laprjns · 01-16-2016, 09:52 AM

Quote:

Originally Posted by gauchao

Sorry, but have you made the file executable before running it?

No actually I didn't have to make it executable and I was a bit surprised.

Code:

rich[Downloads]$ ls -al VirtualBox-5.0.12-104815-Linux_amd64.run 
-rw-r--r-- 1 rich users 84592081 Dec 18 11:17 VirtualBox-5.0.12-104815-Linux_amd64.run

I don't normally run the script using "sh" so when it executed I was surprised, but assumed that it had something to do with the sh command

Didier Spaier · 01-16-2016, 10:06 AM

Yes, as an argument of 'sh' or 'bash' a script does not need to be executable. Nor if sourced in another script, of course.

Ztcoracat · 01-16-2016, 11:40 AM

Quote:

Originally Posted by Didier Spaier

Just type as a regular user:

Code:

VirtualBox &

Case matters

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

Code:

bash-4.2$ uname -m
x86_64

Ztcoracat · 01-16-2016, 11:52 AM

Quote:

Originally Posted by laprjns

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:

Code:

rich[Downloads]$ wget http://download.virtualbox.org/virtualbox/5.0.12/VirtualBox-5.0.12-104815-Linux_amd64.run

the as root run the script

Code:

root[Downloads]# sh VirtualBox-5.0.12-104815-Linux_amd64.run

Make sure that you have the kernel-source package installed prior to runing the script.

That should do it (it worked here)

The download worked for me using the wget cmd. Thanks-

I installed the virtaulbox-kernel already.

Didier Spaier · 01-16-2016, 11:56 AM

When you tried to run this command:

Code:

sh VirtualBox-5.0.12-104815-Linux_amd64.run

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.

Ztcoracat · 01-16-2016, 11:57 AM

Progress!

Code:

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#

Ztcoracat · 01-16-2016, 12:03 PM

http://i1052.photobucket.com/albums/...25954%20PM.png

Thank You for the help-

Ztcoracat · 01-16-2016, 12:06 PM

Quote:

Originally Posted by Didier Spaier

When you tried to run this command:

Code:

sh VirtualBox-5.0.12-104815-Linux_amd64.run

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?

bassmadrigal · 01-16-2016, 09:19 PM

Quote:

Originally Posted by Ztcoracat

Code:

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.

Ztcoracat · 01-16-2016, 09:24 PM

Quote:

As others pointed out, you needed to run updatedb as root to get the database created.

I did that:-

Thanks for showing me how to change the cron's default time.