
|
[openbeos]
||
[Date Prev]
[09-2001 Date Index]
[Date Next]
||
[Thread Prev]
[09-2001 Thread Index]
[Thread Next]
[openbeos] Re: Operating System Source Request
- From: "Vitaliy Mikitchenko" <vitviper@xxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Tue, 4 Sep 2001 22:45:26 -0700
Just one question: how do I sign-up to be a developer?
> openbeos@xxxxxxxxxxxxx [openbeos] Re: Operating System Source Request
> "Michael Phipps" <mphipps1@xxxxxxxxxxxxxxxx>Date: Tue, 04 Sep 2001 12:36:14
> -0400
>Reply-To: openbeos@xxxxxxxxxxxxx
>
>
>Two new birds with one stone! :-)
>
>Welcome, both of you.
>Rather than taking a "start at ground zero and everybody pile on to the same
>task" approach, we are trying something different.
>Basically, it works like this:
>
>The kernel group is the only group that gets concerned about NewOS. Everyone
>else forgets about it and builds their servers/kits under BeOS as it exists
>today.
>Just use a different name (say, print_server2, or libgamekit2.so, for
>example). You can test with it day and night on a standard Be R5 release.
>You don't have to depend on/worry about what the Kernel group is doing. That
>way, everyone can make progress without worrying about one small aspect that
>will be a while, anyway. Plus, you have the whole rest of BeOS to test with.
>You can use a complete Interface kit before there is an Open one. You can code
>knowing that the kernel is stable. Etc.
>
>Then, as pieces start to come together, we can test with each other's pieces
>parts and it should be much easier.
>
>Of course, if you want to be part of the kernel group, that is another story.
>But there are many kits, no kit is better or worse than any other. Some need
>more help than others.
>Goto our web site (www.obedn.com) and sign up! :-)
>
>And welcome aboard.
>
>PS - Phyte - could you put this in the FAQs? Thanks!
>
>
>>Oh, yeah. I downloaded the NewOs kernel source as well to look it over. Have
>>you guys added anything to it? I don't know much about kernel-level coding,
>>but I'm sure I'd be some help elsewhere. I've run NewOS on my computer, and
>>it runs fine (with both my processors!).
>>
>>
>>> "p willis" <p.willis@xxxxxxxxx> <openbeos@xxxxxxxxxxxxx> [openbeos]
>>> Operating System Source RequestDate: Tue, 4 Sep 2001 20:25:31 -0700
>>>Reply-To: openbeos@xxxxxxxxxxxxx
>>>
>>>
>>>Hello Everyone,
>>>
>>>I just subscribed to the email list. (Oh, NO! Not *him*...!)
>>>
>>>I downloaded the source for NewOS and was looking it over.
>>>I was wondering whether there was anything different in the
>>>the floppy image vs. the most current source code....?
>>>
>>>I notice a thread_test() routine called in main2() and wondered if this
>>>is active in the floppy image. I didn't see any messages but perhaps
>>>my hardware is antiquated.
>>>
>>>I guess I'm wondering 'where are you at and how can I help' ?
>>>
>>>Are you implementing anything like XFS for a journaling file system?
>>>I have the docs for that and a spare HD.
>>>I am also big on memory management and hardware drivers
>>>(paging directories, page tables, page table entries...etc.)
>>>Does the memory management need to be changed for BeOS?
>>>Demand paged virtual....maybe? I have LRU code around here
>>>somewhere.
>>>
>>>Let me know what you want done.
>>>
>>>Peter
>>
>>------------------------------------------------------------
>>Free, BeOS-friendly email accounts: http://BeMail.org/
>>BeOS News and Community: http://www.BeGroovy.com/
>>
>>
------------------------------------------------------------
Free, BeOS-friendly email accounts: http://BeMail.org/
BeOS News and Community: http://www.BeGroovy.com/
|

|