[openbeos] Re: The storage kit

>
>Some questions, forgive me if they've been asked before, but I've only 
>just subscribed to the mailing list:
>

Then welcome to the OpenBeOS community :)

>1) What is NewOS & how does it fit in with the project?

NewOS is (mostly) a kernel developed by an Ex-Be, Inc Kernel Engineer, 
called Travis. This kernel implements a threading model pretty simular 
to the BeOS kernel. After looking around in the kernel market at the 
start of the OpenBeOS project, NewOS was chosen as the kernel for 
OpenBeOS.

Travis himself is a member of the Kernel Team these days and is very 
busy bringing the NewOS kernel to the point where we can actually start 
building userspace programs on top of that. All the current teams 
(except for the Kernel Team, who are assisting Travis in his job to 
enhance and document NewOS) are building their software on top of the 
current BeOS R5, "simply" replacing parts of it one module at a time 
(tm).

>
>2) What are the responsibilities of the storage kit part of the 
project? 
> Is it a front-end for the file systems in the kernel? Does it 
encompass 
>the file systems, with the kernel handling the devices?  Or something 
else?
>

The storage kit encompasses all APIs as described in the BeBook under 
"Storage Kit". For a list of those, see file:///boot/beos/documentation
/Be Book/The%20Interface%20Kit/index.html if you're reading this from a 
BeOS installation, or http://www-classic.be.com/documentation/be_book/
The%20Storage%20Kit/index.html if you're not.

Mostly, it are the C++ classes for file/directory/symbolic link 
handling, including attributes, queries, and the like.

>3)  Have we got any standards for coding, directory structure, and 
>makefiles?  If not, should we start a project to define them before we 
>end up with conflicting projects?
>

We've said in the beginning that we're trying to keep close to the 
coding standards as described for OpenTracker (see http://
www.opentracker.org), and a start of a discussion was made today on 
directory structure. However, I think we're at a point that starting a 
seperate project to guide this all into one decent document describing 
it all would be _extremely_ usefull

Are you volunteering? If so, I'm happy to help with that too :)

> I'm not being negative, but I just wanted to ask

No problem, good questions :)

>                    Keith
>
>

Regards,

Ithamar
(PrintKit team lead)

Other related posts: