© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
What are our options for making KSM opt-in rather than opt-out for qemu-system-... packages?
(ksmtuned doing what it does seems fine to me: (a) it's in universe, thus not a default installed tool anywhere (b) the name clearly says what it's going to do. An admin that installs it knows what they want.)
A debconf setting is the first thing that comes to mind, but it's not very discoverable. A systemd service file feels easy, sort-of, but I'm not sure it's that much more discoverable than debconf.
Should we change it only for future releases or also including historical releases? (I'm inclined to say only future releases. Even though I feel strongly that we should disable it by default for safety, I also don't want users with pitchforks at my door for a surprise change that makes their workloads fail.)
Thanks