https://bugzilla.redhat.com/show_bug.cgi?id=1481630 --- Comment #79 from Sergio Monteiro Basto <sergio@xxxxxxxxxx> --- (In reply to Evangelos Foutras from comment #76) > @Hans Do you know if the upstream fix for VBoxServiceAutoMount and > vboxsf.mount will support both pre-4.16 and current kernels? (Or if it's > going to support mainline vboxsf only.) > > Supporting both in VBoxServiceAutoMount seems somewhat straightforward > (current Arch Linux workaround at [1]), but mount.vboxsf is more tricky. In > my hacky patch linked below, I just print a message to use `mount -cit` > instead. A problem with this approach, however, is that there's no way (that > I can see) to disable the helper from within fstab entries. > > If the upstream solution is going to be in line with Fedora's (only > supporting option strings for mounting), then we might as well roll with > that in Arch Linux. Seems like it was an easy decision for Fedora 28 since > only Linux 4.16 has to be supported, but we also ship the latest LTS kernel > (and Manjaro even ships almost all kernels found on kernel.org :O). > > [1] > https://git.archlinux.org/svntogit/community.git/tree/trunk/010-linux-4.16- > mount-fixes.patch?h=packages/virtualbox I may add the patch mention if it fixes something ... Note that we remove binary mount.vboxsf (on Fedora 28+). If you want share folders, you need build vboxsf.ko with akmods and after `mount -t vboxsf bla bla` will work out of the box. I checked the archlinux package (all patches and build parameters), RPMFusion package is based on Debian , opensSUSE etc but I wasn't aware of archlinux packaging and I may include some little improvements based on archlinux package, but I have to test it first. Best regards, -- 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
