On Wed, Apr 14, 2010 at 10:44 AM, Carlos Mennens <carloswill@xxxxxxxxx>wrote: > ############################################## > [code][root@ghost ~]# /etc/rc.d/vboxdrv start > -bash: /etc/rc.d/vboxdrv: No such file or directory[/code] > ############################################## > Actually, vboxdrv is a kernel module, so you have to load it. This can be done (as root) with 'modprobe vboxdrv'. If you're going to use VirtualBox on a regular way, a suggest you put vboxdrv in your MODULES array on /etc/rc.conf Below is what I see after I downloaded the Tarball and ran 'makepkg > -s' against it: > > ############################################## > [cmennens@ghost virtualbox_bin]$ ls -l > total 91336 > drwxr-xr-x 6 cmennens users 4096 Apr 14 09:18 pkg > -rw-r--r-- 1 cmennens users 4694 Jan 1 1970 PKGBUILD > drwxr-xr-x 2 cmennens users 4096 Mar 25 15:10 src > -rw-r--r-- 1 cmennens users 113 Jan 1 1970 vbox_build_module > -rw-r--r-- 1 cmennens users 3269 Jan 1 1970 vbox.install > -rw-r--r-- 1 cmennens users 51834320 Mar 25 15:44 > VirtualBox-3.1.6-59338-Linux_amd64.run > -rw-r--r-- 1 cmennens users 41664600 Apr 14 09:18 > virtualbox_bin-3.1.6-1-x86_64.pkg.tar.xz[/code] > ############################################## > Also, when you update your kernel, you're supposed to run the vbox_build_module again. -- Guilherme M. Nogueira "Any sufficiently advanced technology is indistinguishable from magic." - Arthur C. Clarke
