Re: [coLinux-devel] Upgraded packages crashing system.

[Robert S. <rj...@ze...>]

> Installing the packages:
> procps (offending program: /sbin/sysctl)
> util-linux (offending program: /sbin/hwclock)
>
> Effects:
> They cause the system to completly hault. I started
> from scratch and updated each package one at a time to
> find the problems.

Hi All,

I have been lurking reading this list for a while.
I looked at this project because I wanted a way to run a linux only binary
on a cluster of windows boxes where I work (I was thinking of using Sun
Gridware to distribute the jobs, or Boinc - the SET@Home framework)

I think it is an amzing idea to run linux and windows cooperatively.
Thanks Dan

What worries me though is the stability (and security) of such a system.
I admit there have been few cases of people reporting windows to crash -
but there is this report where it looks like the cooperative multitasking
between windows and linux is not working and there was someone who tried
to start X and got the machine to bluescreen.

I admit that if these devices were compiled out of the kernel then it
would be more stable but would it ever be possible to not run the linux
kernel in ring-0?
I realise that a windows driver running in ring-0 will always be necessary
but it would be nice if the linux kernel (or any loaded kernel module) did
not have access to the entire memory space of the machine.

Could someone explain the architecure of colinux to me in terms of the
different components and what priviledge level they run in?

Also I would like to know how the cooperation between colinux and windows
works. Does colinux yield to windows in the idle loop? the timer
interrupt? any system call
Running a process that can consume 100% CPU in both colinux and windows
simulateneously seems to share.

I did have a look at the code but I have to admit I am not much wiser and
it makes sense to ask rather than guess

Thanks

---
Robert Stonehouse