Comment 15 for bug 177439

I was hit by this as well, fortunately I only did the kernel update on my desktop machine and not other machines I am responsible for.

Please don't take this as a flame but Canonical really needs to catch a problem like this in QA. If someone breaks their machine screwing around with the betas or running dozens of Compiz plugins or using beta proprietary drivers that is one thing. But rendering a machine with common hardware unbootable because it installed a security related kernel update from an official repo for the current stable version of the distro is not good.

Fortunately NFS is probably not used by a huge percentage of Ubuntu home users, but it's pretty common fundamental software in organizations using Linux. If someone had trusted the update enough to push it out to a computer lab with NFS mounted home directories, or servers using NFS shares it would cause quite a mess.