Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#25810 - [virtualbox] Loading vbox modules with /etc/rc.d/vboxdrv

Attached to Project: Community Packages
Opened by Oleg aka Blake-R (Blake-R) - Monday, 29 August 2011, 14:47 GMT
Last edited by Ionut Biru (wonder) - Monday, 10 October 2011, 20:23 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Ionut Biru (wonder)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

How about include loading mobules vboxdrv and vboxnetXXX in 'start' action of /etc/rc.d/vboxdrv?
This task depends upon

Closed by  Ionut Biru (wonder)
Monday, 10 October 2011, 20:23 GMT
Reason for closing:  Won't implement
Additional comments about closing:  vboxdrv dropped from rc.d
Comment by Jakob Matthes (jakobm) - Monday, 29 August 2011, 15:06 GMT
What would be the advantage over specifing them in the MODULES array?
Comment by Ionut Biru (wonder) - Monday, 29 August 2011, 15:20 GMT
i intend to move this script out from rc.d. there is no point of adding this feature
Comment by Uli (Army) - Monday, 29 August 2011, 15:24 GMT
or, if you only want the modules to be loaded, when you need them: modprobe vboxdrv => done, not more complicated than rc.d start vboxdrv, it's even shorter! ;)
Comment by Oleg aka Blake-R (Blake-R) - Monday, 29 August 2011, 16:20 GMT
Advantage is don't keep in mind modules names and requiring for beginners - just add vboxdrv as daemon in rc.conf. At start also modules can be checked for outdating...

Loading...