Comment 1 for bug 47623

Xavier Claessens wrote:
> The problem seems that it tries to install the modules in the running
> kernel folder (from fai-kernels) but it doesn't exists because the
> installation runs in a chroot environment and that's the linux-686
> kernel from ubuntu dapper which is installed in the chroot env.
>

No, FAI uses a socecial kernel at install time, so if the kernel modules
from the lkernelk running at install time _would_ be in the chroot, the
vmware player package would install the wrong modules, because there's
another kernel running on the installed system, the one you chose in the
FAI config.

> I don't know if that's a FAI or a vmware-player-kernel-modules bug ...

I see two possible solutions:

1) FAI needs to use the same kernel for installation as for runtime.
This is complicated to do, because it would also mean that you need a
different install kernel for each architecture/each different kernel you
want to run on your machines.

2) Make the vmware-player module package to not look into the kernel
that's currently running, but give a possibility to chose which kernel
modules to install manually, or via debconf, or just by having an
explicit package for each kernel.

How do similiar packages handle this? There are other packages with
kernel modules, which are specific for a kernel version, and there are
multiple, one for each kernel version? Do they also try to automatically
fugure the right kernek version at runtime?
I think not, they let the user chose the right package for their kernel
version. But I am not sure.

Henning