Steve Kemp wrote:
> Use the open-vm-tools package. Edited that would look something like
> this:
> apt-get install module-assistant open-vm-tools open-vm-source
Aptitude sees module assistant, but not the others:
# aptitude search module-assistant open-vm
p module-assistant
debian-user:
Blindly calling ifdown/ifup from /etc/rc.local was cheesy, and sure enough it
didn't work reliably. So I wrote a Bash shell script to ping my gateway and do
ifdown/ifup only if needed (three times maximum). I call that from rc.local
instead:
/root/bin/kick-eth0
David
#!/bin
Steve Kemp wrote:
> When it failed what was the symptoms from the Debian side?
The Debian machine cannot access the network.
> I'd guess that it came up as eth1, eth2, etc. See if that is the
> case by running "ifconfig -a".
$ cat ifconfig-a-eth0-dead.txt
eth0 Link encap:Ethernet HWaddr
On Sun Aug 31, 2008 at 13:52:26 -0700, David Christensen wrote:
> 2. The eth0 network interface would not come up reliably at boot --
>~50% of the time it would work.
When it failed what was the symptoms from the Debian side?
I'd guess that it came up as eth1, eth2, etc. See if that
debian-user:
VMware doesn't seem to offer publicly visible support, so I'm posting here.
I am running VMware Player 2.0.5:
http://www.vmware.com/products/player/
on Windows XP Pro SP3 with a Debian 4.0 client:
http://www.vmware.com/appliances/directory/808
I ran into keybounce, netwo
5 matches
Mail list logo