VMWare Player – Fix Kernel Module Updater Issue After 13.04 Upgrade

To answer the first question Why are there only two packages? or Why aren't there two header files? -- when they're cross compiled, they're packaged up to handle every use case. By splitting the headers into a larger all package and a smaller arch-specific one, you save bandwidth pushing them out to users. When you're doing it yourself, you only need it for one arch so one headers file will do.

As for the symlink through to your source location, I have had the same issue. I have not found a good fix other than to also generate a linux_source package (just add that on after kernel_image kernel_headers) and then fix the symlink manually.

There is actually a question all about this side of things already. The long-term solution seems to be hacking in a script that runs after each kernel installation that just fixes the symink up.

Installing kernel updates will not influence the custom one.

However, the update will update grub. When I installed a mainline kernel, since it had a higher number it was made as the default kernel.

So if your kernel has a higher number you shouldn't worry.

If your kernel is lower than 3.5.0-19, the update will make the newly installed kernel default. You can set the kernel you want as default by changing the GRUB_DEFAULT=0 line to GRUB_DEFAULT="1>2" in /etc/default/grub. 1, means the second option in the first page of the Grub menu and the 2 means the third one on the second page (Counting starts from 0).