https://bugzilla.redhat.com/show_bug.cgi?id=1481630 --- Comment #72 from Hans de Goede <hdegoede@xxxxxxxxxx> --- Hi, (In reply to Sergio Monteiro Basto from comment #71) > Hello , > > Would be an honor if you give commit access to this package, I could do the > builds and updates of this package. I would be happy to have you as a co-maintainer, I've given commit rights to you now. > I miss one word in my previous comment (*) please _build_ > virtualbox-guest-additions for F28, new version 5.2.8 is not built yet in > F28. Good point, fixed now. > I started to test virtualbox-guest-additions package from Fedora stack (I > built it on copr) and here is the result of `modprobe vboxsf` [1] That looks like your building from the virtualbox-upstream sources, as mentioned in comment 65, you need a modified version of vboxsf to work with the upstream-kernel version of the vboxguest module. This modified version is available here: https://github.com/jwrdegoede/vboxsf/ This is the version of the vboxsf sources which the rpmfusion akmod package should use for F28+. > 2 points: one, we also may build VirtualBox-kmodsrc sub-package in Fedora > package No that is not possible, Fedora does not allow out-of-tree kernel modules / kmod packages as part of Fedora. > Second point, how we load vboxsf module, is need add the file > /usr/lib/modules-load.d/VirtualBox.conf with "vboxsf" to load automatically > vboxsf.ko ? You don't need to do anything as soon as someone does "mount -t vboxsf" or the virtualbox.service tries to do the equivalent for a folder selected for automount, then the module will autoload. My vboxsf sources/module contains: "MODULE_ALIAS_FS("vboxsf");" which will make the module autoload whenever necessary. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
