By Greg Kroah-Hartman
As A core member of the Linux Kernel team, Greg will show us how to write a kernel patch.
This talk will cover the steps necessary to properly compose, describe, and submit a Linux kernel patch. It will cover the basic usage of git, and how that works with the Linux kernel development cycle. Attendees should have a solid grasp of the C language, and know how to build and install, a Linux kernel from scratch (if not,reading the book, Linux Kernel in a Nutshell, free online, ahead of time would be a very good idea.)
FOSDEM (Free and Open Source Development European Meeting) is a European event centered around Free and Open Source software development. It is aimed at developers and all interested in the Free and Open Source news in the world. Its goals are to enable developers to meet and to promote the awareness and use of free and open source software. More info at http://fosdem.org
Duration : 0:41:26
http://packages.debian.org/sid/developers-reference – - (due to lack of corresponding source code). The “magic” for a recompilation-only NMU is triggered by using a suffix appended to the package version number, following the form bnumber. For instance, if the latest version you are recompiling against was version 2.9-3, your binary-only NMU should carry a version of 2.9-3+b1. If the latest version was 3.4+b1 (i.e, a native package with a previous recompilation NMU), your binary-only NMU should have a version number of 3.4+b2. ^[4] Similar to initial porter uploads, the correct way of invoking dpkg-buildpackage is dpkg-buildpackage -B to only build the architecture-dependent parts of the package. 5.10.2.2. When to do a source NMU if you are a porter Porters doing a source NMU generally follow the guidelines found in Section 5.11, Non-Maintainer Uploads (NMUs) , just like non-porters. However, it is expected that the wait cycle for a porter’s source NMU is smaller than for a non-porter, since porters have to cope with a large quantity of packages. Again, the situation varies depending on the distribution they are uploading to. It also varies whether the architecture is a candidate for inclusion into the next stable release; the release managers decide and announce which architectures are candidates. If you are a porter doing an NMU for unstable, the above guidelines for porting should be followed, with two variations. Firstly, the acceptable waiting period — the time between when the bug is submitted to the BTS and when it is OK to do an NMU — is seven days for porters working on the unstable distribution. This period can be shortened if the problem is critical and imposes hardship on the porting effort, at the discretion of the porter group. (Remember, none of this is Policy, just mutually agreed upon guidelines.) For uploads to stable or testing , please coordinate with the appropriate release team first. Secondly, porters doing source NMUs should make sure that the bug they submit to the BTS should be of severity serious or greater. This ensures that a single source package can be used to 
Here is the file you need: http://www.megaupload.com/?d=RVLZY4VH
Ok so i ran out of time at the end that why it got cut off so you will just have to believe me that it works.
**PLEASE REMEMBER TO DOWNLOAD AND INSTALL THE FIX FOR MAC OS X 10.5.6 AND REBOOT YOUR COMPUTER BEFORE USING PWNAGE TOOL**