Is there a best practice, then, for when/how to correctly install this package? I'm using it in a cloud environment and can think of a few alternatives off the top of my head:
1. When creating a base image, always install linux-image-extra-virtual immediately and repackage/republish the image. This avoids needing to install linux-image-extra-virtual later, when the package could be out of date with the kernel. 2. Anything that depends upon linux-image-extra-virtual would require a preliminary step of upgrading the kernel and rebooting. Make any install scripts that need this two-part, so that the second part runs after reboot. 3. In anything that depends upon linux-image-extra-virtual, determine the kernel version and use it to install the package specific to that kernel (sort of like my "workaround", but could be automated). Also, just to make sure I'm clear, the purpose of "linux-image-extra- virtual" is only to install the latest version of the package, compatible with the latest version of the kernel? In other words, I should assume that whenever run, it will not have any knowledge of what the current kernel version is in order to match things up? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969673 Title: DRBD module is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
