Re: [Trion-kernel-dev] Due to popular demand (?), Trion now has a wiki

[Daniel R. <cos...@gm...>]

> Stephen wrote:
> Anyways, I've set up an out-of-the-box wiki at http://trion.sf.net/wiki
> for anyone who is (a) still alive but not in a permanent vegetative
> state and (b) out there looking to do something with Trion.

Alright, I got the hint: You set-up this wiki and now you expect me to  
fill it with some documentation about my obscure code. Neat trick ;)

> Stephen wrote:
> Ja ja, it needs work to look sliXXors, but I'm soliciting content at
> this point.

Just make the trion logo transparent and I'll be fine with the design.

> Jeff wrote:
> I know since I last contributed, the architecture has changed quite a  
> fair bit.  Hopefully someone can point me in the right direction to
> update myself on what has happened as of late, and I'll begin my
> re-education, and hopefully start contributing again.

It's probably best if you just start by reading the latest trion design  
paper. Although it's unfortunatelly still quite superficial and  
incomplete, I still hope that it at least includes the most important  
aspects of the nano-kernel design. I've really spent ages on developing  
this design and it certainly is way more elaborated than the document may  
imply. If you have any questions that are not answered by the draft, just  
ask and I'll do my best to explain it. In my opinion such a public  
discussion is much more efficient than any full blown paper could ever be..

> Jeff wrote:
> I've had a lot of time to think, lately, about OS design, and am  
> currently working on a meta-based file system for my own OS, which
> might also be useful for Trion.

Before adding a custom file-system, we should in my opinion at least have  
some fat12 support for backwards compatibility. Once that is done I  
however don't see any reason why we shouldn't try out new designs. The  
nanokernel approach should actually make it quite easy to add support for  
new file-systems.

> Jeff wrote:
> I'm also trying to flesh out an inheritance-based hierarchical (ie,  
> OO-like) driver system... some of this research might be useful to
> Trion (admitedly, I don't recall if Trion decided upon a driver system).

Most probably we would have to adapt your design quite a bit to make it  
compatible with the rest of the nanokernel design. It's really hard to say  
to what extend it could be used without knowing any details of your driver  
system.

> Stephen wrote:
> The architecture docs are available from
> <http://trion.sourceforge.net/downloads.php>, um, er, okay it used to
> work.  Dang SourceForge and their constant tinkering.

Hmm, that's actually the old draft. The latest version is called "trion  
design draft.pdf" and can be found in the same CVS directory  
(http://trion.cvs.sourceforge.net/trion/docs/).

regards,
cosmo86