On Tue, Dec 22, 2009 at 5:59 PM, Jerome Vuarand
<jerome.vuarand@gmail.com> wrote:
2009/12/22 Timothy Baldridge <tbaldridge@gmail.com>:
>> Also, since almost everything in the eCos kernel is optional, we can
>> get rid of the filesystem and other 'legacy' concepts. Just a Lua API
>> to manage the creation of Lua processes (or tasks, or actors...), the
>> TCP/IP network and some form of persistence (only if you have
>> persistent storage; if not, just use the same remote API through the
>> network)
>
> The killer of almost all hobbyist OSes is device support. This is why
> SkyOS recently switched over to using the Linux kernel. So the
> question becomes, do we want a more flexible, simpler kernel with less
> driver support, or a more complex kernel with better driver support,
> but less "hackability"?
Maybe the solution here is to use drivers for existing platforms.
Rather than running the nice OS in a VM in a driver soup (be it
Windows or Linux), one can run the binary drivers themselves in a VM,
on top of the nice OS. You would only need very basic drivers
built-in, for the memory manager, and some bus controllers.
