Re: [coLinux-devel] BSOD, DDK dependency

[Ian C. B. <ia...@bl...>]

I've managed to get the Debian3.0 root image and the binary release of
coLinux running on a WinXP/Pro laptop with only minor issues. 

The block device size issue (30448/262144) causes a warning on mount.
You can of course override it with:

	$ mount -o remount,rw /
	$ exec /sbin/init 3

Still, it will be nice to hunt this one down. I was able to generate a
~1G file on the filesystem with no errors with dd - so the block
limitation reported on boot doesn't appear to be breaking writes past
that point.

The win32 Tap interface is working just fine, and works well with
both ICS and bridging. 

Here's a quick guide for some of the unfamiliar users:

For ICS:
1. Give your Tap Local Area Connection interface an IP of 192.168.0.1
2. Go to Network Settings, open your your "external" 
interface (whatever Local Area or Wireless Connection interface
you use as your default route), click on the Advanced tab,
select Internet Connection Sharing, Allow other network users 
to connect through this comput'ers Internet connection, and select 
the Local Area Connection interface assigned to your Tap driver.
3. The default Debian3.0 root image has an IP of 192.168.0.40
preconfigured in its /etc/network/interfaces file: simply do the
following:
	$ ifup eth0
You should now be able to ping out. 

For bridging:
1. Turn off ICS (follow step 2 above, disabling ICS)
2. Select two interfaces (holding down the control key) and right click
a menu to select "Bridge Connections".
3. Configure /etc/network/interfaces on your colinux image, or
ifconfig up your eth0 interface with an IP on your segment and add a
default route through your gateway.
(Note: if you do happen to use a wireless interface in your testing,
don't attempt bridging - it doesn't work).

Both methods above work just fine for me.

You might also try a direct routed approach, if you're more familiar 
with IP networking and able to add routes on a machine upstream from
your windows box (or configure RIP/OSPF/etc to do the same). It should
work with little effort.

On the plus side: no BSODs yet. ;)

- Ian C. Blenke <ia...@bl...>
PS. I hate Windows, Windows' dialog boxes, and the pain that must be
taken to describe such trivial procedures.