Man, we already have to write a complete desktop OS. Now we need to write an embedded OS too? Damn, I'm suddenly very tired! Seriously, these are cool ideas. You realize, of course, that most cool ideas are dangerous to project schedules ("can you say 'feature creep'? sure, I knew you could") Not to be a fuddy duddy, but how 'bout we concentrate on the mammoth task already before us and worry about conquering the world a little later? ;) > I have some suggestions: > 1. Couldn't be OpenBeOS developed for the embedded market also? I know that it's something hard to do without the specific hardware to test it on, but right now I have a project to work for, and I need a embedded version of BeOS (I know that it exist and it's called BeIA, but officially BeIA is dead). So what I'm proposing here it's to have two versions of OpenBeOS: > A. Desktop version > B. Embedded version > The embedded version will be a stripped-down version of OBOS, with support for specific hardware. But in order to be possible to do a Emb version, OBOS must be made with this in mind. I think that a very good modularity would help a lot. A very customizable installation for the Desktop OBOS would be very much appreciated. > 2. How about the multiplatform support? If OBOS is designed from the beginning with this in mind, could be easily ported to a platform. A mean, look at NetBSD... It exists for 21 platforms, even for obsolete hardware and they say that it is a viable solution even for the embedded market. The code of NetBSD could be a source of inspiration, right? Just take a look at their goals and the philosophy behind the system (in case you didn't do it already ;-) ).... www.netbsd.org > > Well, that would be all for now.. > > Some question for the kernel guys: for what platforms has been designed OBOS until now? > What are the tools used? (the compiler, debugger, boot-loader, etc...) > >