hi,
On Fri, 2007-03-16 at 23:51 +0000, VMware Build Team wrote:
> Why do you want to install the player when the modules aren't available
> for it to work after it's installed? Am I missing entirely what you're
> trying to accomplish?
the modules for the running kernel are not available, but the running
kernel is just a temporary netboot kernel used by the FAI installer.
when the system reboots it will boot into the default/latest ubuntu
kernel, with the vmware modules available, and thus a working vmware
setup.
so the problem is that sometimes there may be situations where you don't
want the vmware services to start, or at least can tolerate failures in
the vmware services to start. as i said previously my opinion init
script failures should never cause the package installation to fail, but
i'm not going to spend the effort to try and convince you of this.
another alternative to the option i mentioned in last night's email:
if during the post-installation script there is an error loading the
vmware modules (or running the init script), you could use debconf to
show a message like:
"vmware services failed to start: see the following documentation"
and let the installation finish. or even:
"vmware services failed to start: abort/ignore/retry?"
with a default of ignore and act accordingly.
if you're interested i could provide you with some sample code for how
to do that with debconf.
sean
--
vmware-player uninstallable running default kernel
https://launchpad.net/bugs/69509
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
