Re: [PATCH] VMware balloon: force compiling as a module

From: Bruno PrÃmont
Date: Tue Jun 29 2010 - 12:29:44 EST

On Tue, 29 June 2010 Alexander Clouter <alex@xxxxxxxxxxxxx> wrote:
> Dmitry Torokhov <dtor@xxxxxxxxxx> wrote:
> >
> > VMware Tools installer requires the upstream driver to be compiled
> > as a module in order to detect its presence and avoid installing
> > our own version on top of it. To avoid surprises with 2 versions
> > of the driver being installed and fighting with each other, let's
> > force the driver to be compiled as a module unless user selects
> >
> *barf*
> This surely is a problem in the installer and not the kernel? Can you
> not nosey around in /sys/class/misc or where-ever your driver appears?
> If it does not, then I would probably suggest a patch to your balloon
> driver that dumps some details in there, including module version
> information.
> Eugh.

In addition, the installer may check under /sys/module/ for it (as for
any/most code that can be built as a module), even for built-in code.
(if balloon driver does not show up there when built-in it would be
better to get it to show up there)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at