A kernel is just another software module. It provides services and interacts with the rest of the operating system through a defined set of interfaces. As such, a kernel should be plug, reboot and play. Having a PetrOS or BlueOS or BeOS kernel should not be a problem for a clean operating system. The advantages of a commercial OS kernel are 'appearances' to business and an experienced kernel now. As well as all the driver support for that kernel and OpenBeOS combined. PetrOS also supports Win32 programs and with a Win32 App Server (USER.DLL COMMCTRL.DLL etc) it would appeal to people who still use office. An official Open Source OpenBeOS kernel, would still be developed. The user could then choose there kernel, based on use, cost, support etc. We will have to write a boot loader and it can choose the kernel as it loads. No need to downplay the contributions of others, even if its off the map a little. While I'm at it lets not forget BlueOS is also working to create a BeOS derivative. There is a lot of code to share. ( A GPL server is not a licensing issue. ) _______________________________________________________ Get 100% private, FREE email for life from Excite Australia Visit http://inbox.excite.com.au/