Hi All,
I initially started writing a response to my previous post, but this
makes more sense in a new one. Sorry for so many posts :P.
How about writing a CIL bootSTRAPPER? I.e. not a drop-in replacement
for GRUB, but something that would allow us to at least get the boring
stuff out of the way (GDT and whatnot). This the boot process would
be:
GRUB [Loads]
o MOSA CIL Bootstrapper (Native) [Loads via cfg]
x Bootstrap Drivers (Native)
x JIT (Native)
x Scheduler (Managed)
x GC (Managed)
x Kernel (Managed) [Loads]
:: HAL (Managed) [Loads]
o Drivers (Managed)
:: ...
:: Userland (Managed)
I am sure you get the idea.
Each team could then make their own JITters, GCers, and Kernels while
keeping the mundane at bay: instead of writing a unified kernel. Is
that a win-win situation for everyone?
--
Jonathan
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
