Am Samstag, 27. Juli 2019, 19:10:19 CEST schrieb Larry Finger:
On 7/27/19 9:57 AM, Michal Suchánek wrote:
On Sat, 27 Jul 2019 16:15:13 +0200
Michal Suchánek
wrote: On Sat, 27 Jul 2019 14:57:43 +0200
--snip--
At first glance, Stefan Seyfried's suggestion to merge the host and guest kmp packages into a single unit seems intriguing.
Well, from a power virtualbox user POV, this approach feels wrong. (Sorry, Stefan) After all, kernel modules always contain very delicate code. Having both, the guest modules as well as the host modules installed everywhere, whether either host or guest functionality is requested, may open a couple of new issues. What happens, if, for some reason, a mix of these modules is loaded? Any chance, they interfere with each other? DoS.. Especially, the vboxfs module is one, that I don't want to see loaded on any host, that I depend on. To the contrary, I already thought of changes to make this module optional. For the record, I usually add a zypper lock for the guest modules on vbox hosts.
I will explore that locally to see if there are any downsides to this change.
Let's see, how Michals changes to the macros behave. Given the sheer size of virtualbox.spec today, having separate host and guest kmod specs with a simple automated update script sounds like the most attractive approach to me. Cheers, Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org