News for hackers. Stuff that matters.
Re:Learn How to Contribute to the Linux Kernel: Take the Eud... by teacup50 on Sunday April 20, 2014 @03:56PM (#7618260)
The BSDs are far more approachable, and I recommend starting there for anyone interested in kernel development.

There are books, such as The Design and Implementation of the FreeBSD Operating System (by McKusick): http://www.amazon.com/Design-Implementation-FreeBSD-Operatin...

There are papers, such as Jonathan Lemon's "Kqueue: A generic and scalable event notification facility" presented at Usenix 2001: http://people.freebsd.org/~jlemon/papers/kqueue.pdf

There are kernel interface man pages:

http://www.freebsd.org/cgi/man.cgi?query=SYSCALL_MODULE&sekt...

http://www.freebsd.org/cgi/man.cgi?query=hhook&apropos=0&sek...

There are examples referenced by the man pages:

http://svnweb.freebsd.org/base/head/share/examples/

Re:Learn How to Contribute to the Linux Kernel: Take the Eud... by justincormack on Sunday April 20, 2014 @05:16PM (#7618513)
Indeed and there is a new edition of the Design and Implementation updated for FreeBSD 10/11 http://www.freebsdnews.net/2014/04/02/design-implementation-...

NetBSD is pretty approachable too. With the rump kernel you can run drivers in userspace, so you can use a normal debugger and so on, and not crash the OS you are running.

Re:Learn How to Contribute to the Linux Kernel: Take the Eud... by songgao on Monday April 21, 2014 @02:21PM (#7622668)
Thanks for the references!

I actually started to look into FreeBSD kernel code recently. I've found that FreeBSD's ath driver code is cleaner and more straightforward compared to the ath/ath*k drivers in Linux. Not sure if this is coincidence or due to different philosophy between FreeBSD and Linux communities.

Re:Learn How to Contribute to the Linux Kernel: Take the Eud... by teacup50 on Monday April 21, 2014 @07:20PM (#7624647)
I've found similar across the board; I think it boils down to different philosophies/development cultures.