This is a major problem. I work with an entire team of developers that
regularly use VirtualBox and _need_ this to be working properly... This
is really unacceptable for an LTS release that is geared toward
production environments. It's ridiculous to have to tell members of this
dev team "hey, don't install those security updates because you won't be
able to get your work done if you do". Yes I know that all you need to
do is reboot and select the previous kernel, and yes I know for a
production environment, updates should probably be handled through a
single local server where all updates are verified first before being
released to the production systems. Even still, these seem like poor
workarounds instead of just coordinating these kinds of updates
properly.

-- 
virtualbox cannot initiate due to vboxdrv missing from kernel modules 
[x86/hardy]
https://bugs.launchpad.net/bugs/179807
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to