Re: Google summer code 2016 project ideas

[Charles Cui <charles.cui1984%gmail.com@localhost>]

here is the link:
https://docs.google.com/document/d/1zUd2LRm9vj-NgwLzKGcdOZ9Cd1YGpSmdBF0KLp_8Eek/edit?usp=sharing

2016-03-17 20:48 GMT-07:00 Charles Cui <charles.cui1984%gmail.com@localhost>:
> Hi Christos,
>
>    I have uploaded my proposal, you guys should be able to see it now.
> Please feel free to comment it.
>
>
> Thanks, Charles
>
> 2016-03-14 15:37 GMT-07:00 Charles Cui <charles.cui1984%gmail.com@localhost>:
>> Got it, thanks.
>>
>> 2016-03-12 21:31 GMT-08:00 Christos Zoulas <christos%zoulas.com@localhost>:
>>> On Mar 12,  8:28pm, charles.cui1984%gmail.com@localhost (Charles Cui) wrote:
>>> -- Subject: Re: Google summer code 2016 project ideas
>>>
>>> | Hi Christos,
>>> |
>>> |    My current focus is to classify the errors when building posix test
>>> | suite on netbsd.
>>> | Basically, there is
>>> | 1. easy to fix error, likes formatting, lack of necessary headers, etc.
>>> | 2. errors that can convert to netbsd implementation. Some systems (ex linux)
>>> | actually define the same function name with netbsd, but they may have
>>> | different parameters.
>>> | 3. netbsd miss the implementation of some features.
>>> |
>>> | Problem 1 and 2 can be solved by some kind of converting and minor fixes.
>>> | For problem 3, which needs the implementation in kernel, or libraries,
>>> | can we use the implementation of existing system (like linux) and
>>> | tailor to fit netbsd?
>>>
>>> That sounds like a good classification and in your plan you should
>>> allocate some time (first perhaps) to cleanup 1 and 2. For 3 you
>>> are better off looking at FreeBSD instead because the code is a lot
>>> more similar.
>>>
>>> Best,
>>>
>>> christos