Opened 16 years ago
Closed 16 years ago
#2051 closed defect (fixed)
vboxdrv and vboxnet don't automatically start with SabayonLinux
Reported by: | dave_p_b | Owned by: | |
---|---|---|---|
Component: | installer | Version: | VirtualBox 1.6.6 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Linux |
Description
The files /etc/init.d/vboxdrv and /etc/init.d/vboxnet don't work with SabayonLinux. SabayonLinux contains both /etc/gentoo-release and /etc/sabayon-release files which confuses the vboxdrv and vboxnet scripts so they think that the OS is gentoo instead of sabayonlinux. The error produced by running either of these scripts is /etc/init.d/vboxdrv: line 97: /sbin/functions.sh: No such file or directory. This is because the functions.sh file, which in gentoo is placed in the /sbin/ folder, in SabayonLinux it is contained in the /lib/rc/sh/ folder, with a link from the /etc/init.d/ folder. E.g. /etc/init.d/functions.sh -> /lib/rc/sh/functions.sh.
When the file VirtualBox-1.6.6-Linux_amd64.run is run, it reports that the vboxdrv module failed to be built. However, this is incorrect. It is built, but to load the modules you have to do it manually E.g modprobe vboxdrv. The /etc/init.d/vboxnet script, however, cannot be run manually.
I have attached the vboxdrv and vboxnet scripts that I changed to recognize the SabayonLinux OS. However, they still don't launch automatically, even after adding them by using the rc-update add command. I don't think that either /etc/init.d/vboxdrv or /etc/init.d/vboxnet scripts work with openrc-0.2.5-r1 or baselayout-2.0.0 that SabayonLinux uses in it's latest 3.5 release.
Hope this can be fixed soon.
Attachments (1)
Change History (4)
by , 16 years ago
Attachment: | SabLinuxInitScripts.tar.gz added |
---|
comment:1 by , 16 years ago
Component: | other → installer |
---|
Compressed file containing modified vboxdrv and vboxnet init scripts