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#27373 - [virtualbox-source] - modify /usr/bin/vboxbuild to put modules in Arch's default dir

Attached to Project: Community Packages
Opened by John (graysky) - Wednesday, 30 November 2011, 22:02 GMT
Last edited by Ionut Biru (wonder) - Saturday, 03 December 2011, 18:06 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Why? Consistency since /lib/modules/$(uname -r)/extramodules is the new home for extra modules and since the main package places its modules there. Thoughts?

The following should do it but I'm sure you can write a more elegant solution :)

find /lib/modules/$(uname -r)/misc -name 'vbox*.ko' -exec gzip -9 {} \;
mv /lib/modules/$(uname -r)/misc/vbox*.ko.gz /lib/modules/$(uname -r)/extramodules
depmod -a
This task depends upon

Closed by  Ionut Biru (wonder)
Saturday, 03 December 2011, 18:06 GMT
Reason for closing:  Implemented
Additional comments about closing:  4.1.6-4
Comment by Ionut Biru (wonder) - Thursday, 01 December 2011, 07:26 GMT
the problem is that /lib/modules/$(uname -r)/extramodules is not a valid path.

stock kernels have /lib/modules/$(uname -r)/extramodules-MAJOR_VERSION and i don't know if all unsupported kernels really use this schema

Loading...