Hay, thaaaaaaaaaaaaaaank youuuuuuuuu!
I really glad to receive your message!
It will really shelp.
Again, thanks a lot!
Jeroen Ruigrok/Asmodai wrote:
>
> * Gustavo V G C Rios ([EMAIL PROTECTED]) [990910 04:14]:
> >I use freebsd about +- 12 months ago. I have never did any thing serious
> >at kernel level, nor i know anything about kernel desgin.
>
> Start with:
>
> Modern Operating Systems by Andrew S. Tanenbaum
> The Design and Implementation of 4.4BSD by Marshall Kirk McKusick et al.
> Unix Internals: The New Frontiers
>
> Then you probably need more special in-depth books such as:
>
> TCP/IP Illustrated by (R.I.P.) W. Richard Stevens
> Unix Network Programming by W. Richard Stevens
> The Unix Programming Environment by Rob Pike and Ritchie Kerninghan
> Advanced Programming in the Unix Environment by W. Richard Stevens
>
> >Suppose, i would like to spend time and patience learnig Fbsd internals.
> >If, later, i were able to code something to freebsd, and suppose i do,
> >what (or better, how) should i do to have my source accepted by the core
> >team?
>
> send-pr after you have tested, style(9)'d, documented your code and
> tested you patches against a clean checked out source base.
>
> >What about coding style ?
>
> As Chris said, style(9)
>
> >What are the golden rules to have my sources widely accepted by freebsd
> >community?
>
> Don't go the Linux way which tends to favor bloat over solid code.
> Portability and correctness of code is more important than features.
>
> >PS: This is my first attempt to start touching the kernel, so, don't
> >blame, if i wrote something wrong.
>
> That's ok, it's a long way before you actually will start touching the
> sources though, it involves a lot of RTFM'ing and UTSL'ing first.
>
> --
> Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl
> The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>
> Network/Security Specialist BSD: Technical excellence at its best
> Workers of the world, unite!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
