FreeLists / openbeos / [openbeos] Re: Some useful thinkings and ideas...

["Erik Jakowatz" <erik@xxxxxxxxxxxxxx>]

I, for one, would love to see OpenBeOS used on embedded platforms.  
PalmOS, in spite of its archaic and crufty memory management, is OK to 
work with -- but doesn't hold a candle to doing BeAPI development.  
WinCE (PocketPC, whatever), if I may be so bold, positively sucks *ass*. 
 It's just like Win32 (which is two strikes right up front), except not 
-- and the differences are niggling little things that will drive you to 
insanity in a surprisingly short period of time. ~8P

Unfortunately, I don't have any useful suggestions for how we might 
accomplish this beyond a) keeping everything very modular (which is 
already mostly accomplished for us by way of the existing design) and b) 
keep the modules very small (which, for some things, may not be very 
do-able).

Anyway, I think embedded OpenBeOS would be super keen. =)

e

>    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...)


Data is not information, and information is not knowledge: knowledge is 
not understanding, and understanding is not wisdom.
        - Philip Adams