Linked by Thom Holwerda on Fri 22nd Feb 2008 09:16 UTC, submitted by obsethryl
"Previously, we have presented one of the two opensource licensed projects related to creating a C# kernel. Now it's the time to complete the set by rightfully presenting SharpOS, an effort to build a GPL version 3 + runtime exception licensed system, around a C# kernel of their own design. It is my pleasure and priviledge to host a set of questions and answers from four active developers of SharpOS, that is William Lahti, Bruce Markham, Mircea - Cristian Racasan and Sander van Rossen in order to get some insight into what they are doing with SharpOS, their goals, their different design and inspiration."
Thread beginning with comment 302000
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-03-01
Using a Managed Language, you can verify your assemblies and essentially guarantee it will never spill over into another process.
Additionally, if that's not enough (At least in Singularity) you can selectively isolate the processes in Hardware as well.
Additionally, if that's not enough (At least in Singularity) you can selectively isolate the processes in Hardware as well.
That is one thing I dislike about singularity. A great part of the attraction of an OS using software isolated processes is its simplicity. The only security-critical part of such an OS is the MSIL->native JIT/AOT compiler.
If you provide an additional mode of process isolation, a large part of that simplicity goes out of the window. But microsoft never got the whole KISS approach anyway. Just look at the bloat in the C# language specification.
Member since:2005-11-29
Well, it's to take into account that humans make mistakes and therefore the Software Isolation could be compromised in theory.
Not that it's at all likely, but even for things that don't conform to the philosophies of managed code (Sandboxing Native code using a VM for example), this is a very good compromise.
That way you can run "Trusted" applications using only a SIP, and untrusted or native applications using a SIP with additional hardware protection.
I think it would work if used sparingly, but that remains to be seen.
Member since:2005-07-06
Member since:
2005-11-29
Using a Managed Language, you can verify your assemblies and essentially guarantee it will never spill over into another process.
Additionally, if that's not enough (At least in Singularity) you can selectively isolate the processes in Hardware as well.
But really, it's all about zero-copy process communication and ease of development.