Re: [coLinux-devel] coLinux 0.5.2

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

> Use the DDK that closely matches the running system, i.e, the last one.

Ok, I'll see what I can organise.

> Note that the console implementation is incomplete.

Noted :)  So the virtual system "boots" as soon as the coloinux
daemon is executed?  And, if your virtual system didn't require
input, you would not need the console at all?

 
> Was the console still attached after the virtual system shutdown?

The shutdown I did was the "shutdown -g0 -y -i0" ... hmm maybe
I did i6 ...    I'll check these and get back to you tomorrow some
time.


> If Linux terminates, the driver sleeps uninterruptedly until you 
> detach the console, that could be the reason why you couldn't
> kill the driver or restart the system.

Ok - I'll do more testing and get back to you with real data.

One other thing that I've found ... I was in a "cmd" prompt when
I first started the daemon, last time.  This time I ran it from explorer
and I just flashes a window up and disappears again.  I think there's
an error message in there,  but I can't see it - its too fast.  Running
the daemon from the cmd prompt again, it works without a hitch.

Hope that helps others.



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