Re: vmware on debian
On Sat, Aug 14, 1999 at 01:02:45AM +1000, Hamish Moffatt wrote:
> On Fri, Aug 06, 1999 at 05:26:27AM +0300, Alex Shnitman wrote:
> > You have to have the kernel source, or at least the headers part of
> > it, in /usr/src/linux. Sometimes that's not enough (I'm not familiar
> > with the vmware Makefile so I can't tell for vmware) and you have to
> > do this:
> > cd /usr/include
> > mv linux linux.old
> > ln -s /usr/src/linux/include/linux .
> > mv asm asm.old
> > ln -s /usr/src/linux/include/asm .
> Then you should email the authors and tell them not to insist on
> having exact kernel headers in /usr/include/linux. It's an assumption
> which is not true on Debian GNU/Linux. They should allow you to specify
> the location. You should not (and should not need to) do the above
> hack to your /usr/include directory.
And you don't have to (actully the asm headers aren't used by vmware).
I found the following information in the debian-user archives dated
8 Aug 1999 from Alexander Stavitsky, titled "Re: VMware for Debian":
In driver-only/Makefile, change the INCLUDE line to read:
INCLUDE = -I$(TOPDIR)/include -I$(TOPDIR)/common -I$(TOPDIR)/linux \
In vmnet-only/Makefile, add an INCLUDE line:
INCLUDE = -I. -I/usr/src/linux/include
Run make in each of these directories and then copy the vmmon-* and
vmnet-* module files which are created to the vmware top directory and
run ./install.pl. It will correctly identify the modules and install
It would be nice if vmware would include this information in their
documentation (see http://www.vmware.com/support/vmodules.html). I'll
even cc: this message to them, although though they "officially" support
only Red Hat, Suse and Caldera. Vmware works fine with Debian.
Another point to mention:
The vmnet module will not compile with the current gcc 2.95 in potato.
Use gcc272 instead (change the CC = line in Makefile from gcc to
Bob Nielsen Internet: firstname.lastname@example.org
Tucson, AZ AMPRnet: email@example.com