Re: [coLinux-devel] BSOD, DDK dependency

[Ian L. <Ian...@mq...>]

> 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.

I just had one of the Windoze gurus here show me the bridging
option under XP - I hadn't seen that before, very cool.  Works a 
treat.


> On the plus side: no BSODs yet. ;)

Running the coLinux with the deb 1gig yesterday I had two
successful startups.  Today, I got an error -15 from the daemon/exe
telling me that a version was running (I'd just rebooted) .. running it
again it worked fine, but the console/exe showed that I had the 
fsck error.  Interesting.  But still no BSODs.


> PS. I hate Windows, Windows' dialog boxes, and the pain that must be
> taken to describe such trivial procedures. 

There's got to be a tool that performs this via the command line
someplace ... maybe in one of their SDK's ...  I'll see what I can 
find - I'd like to automate the install process (so that it can be
installed from CDROM).




--
Ian Latter
Internet and Networking Security Officer
Macquarie University

 Meet me at the Australian Unix and open systems
   User Group (AUUG) Security Symposium; 2004
  http://www.auug.org.au/events/2004/security/