>> Either as an opt-in or default-on feature. >> Both approaches have arguments that speak for them
> sorry, could you actually list those arguments? Just for clarification To be clear I'm on the "let us enable it" side of things. But I see the two SRU questions: a) but that changes behavior of the system with another mount point being around by default b) but what if people have come up making it no-exec themselves, won't it collide > 3. open discussion with the SRU team what the default should be > 3b. If the discussion ends with default off, do we even need to SRU it then? > yes, without question. > bootstack as well as virtually all people using SRU releases to manage a > cloud will need to > enable this, if you choose to make it default off. Not having the choice at > all doesn't seem > like it actually fixes the problem for anyone on SRU releases. Of course as > you know my opinion > is cloud admins shouldn't need to know about needing to 'enable' this fix. Thanks, so you think even if we can't convince the SRU team of default- on then having the mount unit would be better than having nothing and letting everyone deal with it on their own then - right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913421 Title: Load of pre-upgrade qemu modules needs to avoid noexec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1913421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
