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!
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!
FS#25179 - [virtualbox] Use the rc.d script instead of the old (generic?) setup.
Attached to Project:
Community Packages
Opened by Karol Błażewicz (karol) - Tuesday, 19 July 2011, 17:59 GMT
Last edited by Ionut Biru (wonder) - Tuesday, 19 July 2011, 19:38 GMT
Opened by Karol Błażewicz (karol) - Tuesday, 19 July 2011, 17:59 GMT
Last edited by Ionut Biru (wonder) - Tuesday, 19 July 2011, 19:38 GMT
|
DetailsAt the moment users see messages like
*** To compile the modules do /etc/rc.d/vboxdrv setup *** Why not use our rc.d script? Yes, I know that 'rc.d setup vboxdrv' is the same as '/etc/rc.d/vboxdrv setup'. My complaint is that the current situation leads to edit wars in the wiki, because some people believe that for the sake of consistency users should be presented with one way of doing things like (re)compiling modules for virtualbox. |
This task depends upon
Closed by Ionut Biru (wonder)
Tuesday, 19 July 2011, 19:38 GMT
Reason for closing: Fixed
Additional comments about closing: 4.1.0
Tuesday, 19 July 2011, 19:38 GMT
Reason for closing: Fixed
Additional comments about closing: 4.1.0
Comment by Ionut Biru (wonder) -
Tuesday, 19 July 2011, 18:23 GMT
ack