using the latest binaries provided colinux is working for me
I got the 'fsck' problem on startup but i've hacked the
scripts so the check is ignored, and linux starts up nicely.
however, the linux machine doesn't seem to be able to
communicate to the win2k through tcp/ip. the tap-win32 driver
becomes 'connected' when the linux daemon is started, and
windows reports that it gets a autoconfig ip address
the colinux instance think's it's interface is up, and is
configured the private ip of 192.168.0.40. pinging this ip
causes ping to report:
ping: sendto: Invalid argument
ping: wrote 192.168.0.40 64 chars, ret=-1
have i missed a configuration step of the Tap-win32 driver ?
From: Dan Aloni <da-x@gm...> - 2004-02-01 05:35:39
On Sat, Jan 31, 2004 at 11:29:54PM +0000, Nigel Spowage wrote:
> the colinux instance think's it's interface is up, and is
> configured the private ip of 192.168.0.40. pinging this ip
> causes ping to report:
> ping: sendto: Invalid argument
> ping: wrote 192.168.0.40 64 chars, ret=-1
> have i missed a configuration step of the Tap-win32 driver ?
In Windows, if you configure an IP address for your TAP-Win32
driver it would fix this. 192.168.0.1 netmask 255.255.255.0.
Or optionally, if you enable Internet Connection Sharing this
subnet will automatically be used and you will able to access
the Internet from within coLinux. (apt-get !).