diff --git a/LKMPG-3.16.html b/LKMPG-3.16.html
index 3ef20b2..7d18d8f 100644
--- a/LKMPG-3.16.html
+++ b/LKMPG-3.16.html
@@ -3,7 +3,7 @@
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
 <head>
-<!-- 2016-03-10 Thu 10:51 -->
+<!-- 2016-03-21 Mon 10:54 -->
 <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <title>The Linux Kernel Module Programming Guide</title>
@@ -97,10 +97,9 @@
     { background-color: #ffff00; color: #000000; font-weight: bold; }
   /*]]>*/-->
 </style>
-<link rel="stylesheet" type="text/css"
-href="http://sachachua.com/blog/wp-content/themes/sacha-v3/foundation/css/foundation.min.css"></link>
-<link rel="stylesheet" type="text/css" href="http://sachachua.com/org-export.css"></link>
-<link rel="stylesheet" type="text/css" href="http://sachachua.com/blog/wp-content/themes/sacha-v3/style.css"></link>
+<link rel="stylesheet" type="text/css" href="http://robotics.uk.to/css/foundation.min.css"></link>
+<link rel="stylesheet" type="text/css" href="http://robotics.uk.to/css/org-export.css"></link>
+<link rel="stylesheet" type="text/css" href="http://robotics.uk.to/css/style.css"></link>
 <script type="text/javascript">
 /*
 @licstart  The following is the entire license notice for the
@@ -180,173 +179,180 @@ for the JavaScript code in this tag.
 <h2>Table of Contents</h2>
 <div id="text-table-of-contents">
 <ul>
-<li><a href="#orgheadline11">Introduction</a>
+<li><a href="#orgheadline1">Introduction</a>
 <ul>
-<li><a href="#orgheadline1">What Is A Kernel Module?</a></li>
-<li><a href="#orgheadline2">Kernel module package</a></li>
-<li><a href="#orgheadline3">What Modules are in my Kernel?</a></li>
-<li><a href="#orgheadline4">Do I need to download and compile the kernel?</a></li>
-<li><a href="#orgheadline5">How Do I Install Modules Into The Kernel?</a>
+<li><a href="#orgheadline2">Authorship</a></li>
+<li><a href="#orgheadline3">Versioning and Notes</a></li>
+<li><a href="#orgheadline4">Acknowledgements</a></li>
+<li><a href="#orgheadline5">What Is A Kernel Module?</a></li>
+<li><a href="#orgheadline6">Kernel module package</a></li>
+<li><a href="#orgheadline7">What Modules are in my Kernel?</a></li>
+<li><a href="#orgheadline8">Do I need to download and compile the kernel?</a></li>
+<li><a href="#orgheadline9">How Do I Install Modules Into The Kernel?</a>
 <ul>
-<li><a href="#orgheadline6">Header files</a></li>
-<li><a href="#orgheadline7">Before We Begin</a></li>
+<li><a href="#orgheadline10">Header files</a></li>
+<li><a href="#orgheadline11">Before We Begin</a></li>
 </ul>
 </li>
 </ul>
 </li>
-<li><a href="#orgheadline30">Hello World</a>
+<li><a href="#orgheadline33">Hello World</a>
 <ul>
-<li><a href="#orgheadline12">Hello, World (part 1): The Simplest Module</a>
+<li><a href="#orgheadline15">Hello, World (part 1): The Simplest Module</a>
 <ul>
-<li><a href="#orgheadline13">Example: hello-1.c</a></li>
+<li><a href="#orgheadline16">Example: hello-1.c</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline16">Hello World (part 2): Hello and Goodbye</a>
+<li><a href="#orgheadline19">Hello World (part 2): Hello and Goodbye</a>
 <ul>
-<li><a href="#orgheadline17">Example: hello-2.c</a></li>
-<li><a href="#orgheadline18">Example: Makefile for both our modules</a></li>
+<li><a href="#orgheadline20">Example: hello-2.c</a></li>
+<li><a href="#orgheadline21">Example: Makefile for both our modules</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline19">Hello World (part 3): The __init and __exit Macros</a>
+<li><a href="#orgheadline22">Hello World (part 3): The __init and __exit Macros</a>
 <ul>
-<li><a href="#orgheadline20">Example: hello-3.c</a></li>
+<li><a href="#orgheadline23">Example: hello-3.c</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline21">Hello World (part 4): Licensing and Module Documentation</a>
+<li><a href="#orgheadline24">Hello World (part 4): Licensing and Module Documentation</a>
 <ul>
-<li><a href="#orgheadline22">Example: hello-4.c</a></li>
+<li><a href="#orgheadline25">Example: hello-4.c</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline23">Passing Command Line Arguments to a Module</a>
+<li><a href="#orgheadline26">Passing Command Line Arguments to a Module</a>
 <ul>
-<li><a href="#orgheadline24">Example: hello-5.c</a></li>
+<li><a href="#orgheadline27">Example: hello-5.c</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline25">Modules Spanning Multiple Files</a>
+<li><a href="#orgheadline28">Modules Spanning Multiple Files</a>
 <ul>
-<li><a href="#orgheadline26">Example: start.c</a></li>
-<li><a href="#orgheadline27">Example: stop.c</a></li>
-<li><a href="#orgheadline28">Example: Makefile</a></li>
+<li><a href="#orgheadline29">Example: start.c</a></li>
+<li><a href="#orgheadline30">Example: stop.c</a></li>
+<li><a href="#orgheadline31">Example: Makefile</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline29">Building modules for a precompiled kernel</a></li>
+<li><a href="#orgheadline32">Building modules for a precompiled kernel</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline38">Preliminaries</a>
+<li><a href="#orgheadline41">Preliminaries</a>
 <ul>
-<li><a href="#orgheadline31">How modules begin and end</a></li>
-<li><a href="#orgheadline32">Functions available to modules</a></li>
-<li><a href="#orgheadline33">User Space vs Kernel Space</a></li>
-<li><a href="#orgheadline34">Name Space</a></li>
-<li><a href="#orgheadline35">Code space</a></li>
-<li><a href="#orgheadline36">Device Drivers</a></li>
+<li><a href="#orgheadline34">How modules begin and end</a></li>
+<li><a href="#orgheadline35">Functions available to modules</a></li>
+<li><a href="#orgheadline36">User Space vs Kernel Space</a></li>
+<li><a href="#orgheadline37">Name Space</a></li>
+<li><a href="#orgheadline38">Code space</a></li>
+<li><a href="#orgheadline39">Device Drivers</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline46">Character Device drivers</a>
+<li><a href="#orgheadline49">Character Device drivers</a>
 <ul>
-<li><a href="#orgheadline39">The file_operations Structure</a></li>
-<li><a href="#orgheadline40">The file structure</a></li>
-<li><a href="#orgheadline41">Registering A Device</a></li>
-<li><a href="#orgheadline42">Unregistering A Device</a></li>
-<li><a href="#orgheadline43">chardev.c</a>
+<li><a href="#orgheadline42">The file_operations Structure</a></li>
+<li><a href="#orgheadline43">The file structure</a></li>
+<li><a href="#orgheadline44">Registering A Device</a></li>
+<li><a href="#orgheadline45">Unregistering A Device</a></li>
+<li><a href="#orgheadline46">chardev.c</a>
 <ul>
-<li><a href="#orgheadline44">Example: chardev.c</a></li>
+<li><a href="#orgheadline47">Example: chardev.c</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline45">Writing Modules for Multiple Kernel Versions</a></li>
+<li><a href="#orgheadline48">Writing Modules for Multiple Kernel Versions</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline47">The /proc File System</a>
+<li><a href="#orgheadline50">The /proc File System</a>
 <ul>
 <li>
 <ul>
-<li><a href="#orgheadline48">Example: procfs1.c</a></li>
+<li><a href="#orgheadline51">Example: procfs1.c</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline49">Read and Write a /proc File</a>
+<li><a href="#orgheadline52">Read and Write a /proc File</a>
 <ul>
-<li><a href="#orgheadline50">Example: procfs2.c</a></li>
+<li><a href="#orgheadline53">Example: procfs2.c</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline51">Manage /proc file with standard filesystem</a>
+<li><a href="#orgheadline54">Manage /proc file with standard filesystem</a>
 <ul>
-<li><a href="#orgheadline52">Example: procfs3.c</a></li>
+<li><a href="#orgheadline55">Example: procfs3.c</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline53">Manage /proc file with seq_file</a>
+<li><a href="#orgheadline56">Manage /proc file with seq_file</a>
 <ul>
-<li><a href="#orgheadline54">Figure: How seq_file works</a></li>
-<li><a href="#orgheadline55">Example: procfs4.c</a></li>
+<li><a href="#orgheadline57">Figure: How seq_file works</a></li>
+<li><a href="#orgheadline58">Example: procfs4.c</a></li>
 </ul>
 </li>
 </ul>
 </li>
-<li><a href="#orgheadline56">sysfs: Interacting with your module</a>
+<li><a href="#orgheadline59">sysfs: Interacting with your module</a>
 <ul>
-<li><a href="#orgheadline57">Example: hello-sysfs.c</a></li>
+<li><a href="#orgheadline60">Example: hello-sysfs.c</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline58">Talking To Device Files</a>
+<li><a href="#orgheadline61">Talking To Device Files</a>
 <ul>
-<li><a href="#orgheadline59">Example: chardev.c</a></li>
-<li><a href="#orgheadline60">Example: chardev.h</a></li>
-<li><a href="#orgheadline61">Example: ioctl.c</a></li>
+<li><a href="#orgheadline62">Example: chardev.c</a></li>
+<li><a href="#orgheadline63">Example: chardev.h</a></li>
+<li><a href="#orgheadline64">Example: ioctl.c</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline62">System Calls</a>
+<li><a href="#orgheadline65">System Calls</a>
 <ul>
-<li><a href="#orgheadline63">Example: syscall.c</a></li>
+<li><a href="#orgheadline66">Example: syscall.c</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline64">Blocking Processes</a>
+<li><a href="#orgheadline67">Blocking Processes</a>
 <ul>
-<li><a href="#orgheadline65">Example: sleep.c</a></li>
-<li><a href="#orgheadline66">Example: cat_noblock.c</a></li>
+<li><a href="#orgheadline68">Example: sleep.c</a></li>
+<li><a href="#orgheadline69">Example: cat_noblock.c</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline71">Replacing Printks</a>
+<li><a href="#orgheadline74">Replacing Printks</a>
 <ul>
-<li><a href="#orgheadline67">Replacing printk</a>
+<li><a href="#orgheadline70">Replacing printk</a>
 <ul>
-<li><a href="#orgheadline68">Example: print_string.c</a></li>
+<li><a href="#orgheadline71">Example: print_string.c</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline69">Flashing keyboard LEDs</a>
+<li><a href="#orgheadline72">Flashing keyboard LEDs</a>
 <ul>
-<li><a href="#orgheadline70">Example: kbleds.c</a></li>
+<li><a href="#orgheadline73">Example: kbleds.c</a></li>
 </ul>
 </li>
 </ul>
 </li>
-<li><a href="#orgheadline72">Scheduling Tasks</a>
+<li><a href="#orgheadline75">Scheduling Tasks</a>
 <ul>
-<li><a href="#orgheadline73">Example: sched.c</a></li>
+<li><a href="#orgheadline76">Example: sched.c</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline77">Interrupt Handlers</a>
+<li><a href="#orgheadline80">Interrupt Handlers</a>
 <ul>
-<li><a href="#orgheadline74">Interrupt Handlers</a></li>
-<li><a href="#orgheadline75">Keyboards on the Intel Architecture</a>
+<li><a href="#orgheadline77">Interrupt Handlers</a></li>
+<li><a href="#orgheadline78">Keyboards on the Intel Architecture</a>
 <ul>
-<li><a href="#orgheadline76">Example: intrpt.c</a></li>
+<li><a href="#orgheadline79">Example: intrpt.c</a></li>
 </ul>
 </li>
 </ul>
 </li>
-<li><a href="#orgheadline78">Common Pitfalls</a>
+<li><a href="#orgheadline81">Common Pitfalls</a>
 <ul>
-<li><a href="#orgheadline79">Using standard libraries</a></li>
-<li><a href="#orgheadline80">Disabling interrupts</a></li>
-<li><a href="#orgheadline81">Sticking your head inside a large carnivore</a></li>
+<li><a href="#orgheadline82">Using standard libraries</a></li>
+<li><a href="#orgheadline83">Disabling interrupts</a></li>
+<li><a href="#orgheadline84">Sticking your head inside a large carnivore</a></li>
 </ul>
 </li>
-<li><a href="#orgheadline82">Appendix A. Changes: 2.4 To 2.6</a></li>
-<li><a href="#orgheadline83">Appendix B. Where To Go From Here?</a></li>
-<li><a href="#orgheadline84">Notes</a></li>
-<li><a href="#orgheadline85">Edits</a></li>
+<li><a href="#orgheadline85">Appendix A. Changes: 2.4 To 2.6</a></li>
+<li><a href="#orgheadline86">Appendix B. Where To Go From Here?</a></li>
+<li><a href="#orgheadline87">Notes</a></li>
+<li><a href="#orgheadline88">Edits</a></li>
 </ul>
 </div>
 </div>
+
+<div id="outline-container-orgheadline1" class="outline-2">
+<h2 id="orgheadline1">Introduction</h2>
+<div class="outline-text-2" id="text-orgheadline1">
 <p>
 The Linux Kernel Module Programming Guide is a free book; you may reproduce and/or modify it under the terms of the Open Software License, version 1.1. You can obtain a copy of this license at <a href="http://opensource.org/licenses/osl.php"><a href="http://opensource.org/licenses/osl.php">http://opensource.org/licenses/osl.php</a></a>.
 </p>
@@ -366,23 +372,20 @@ Derivative works and translations of this document must be placed under the Open
 <p>
 If you publish or distribute this book commercially, donations, royalties, and/or printed copies are greatly appreciated by the author and the <a href="http://www.tldp.org/">Linux Documentation Project</a> (LDP). Contributing in this way shows your support for free software and the LDP. If you have questions or comments, please contact the address above.
 </p>
+</div>
 
-<p>
-<b>Foreword</b>
-</p>
-
-<p>
-<b>Authorship</b>
-</p>
-
+<div id="outline-container-orgheadline2" class="outline-3">
+<h3 id="orgheadline2">Authorship</h3>
+<div class="outline-text-3" id="text-orgheadline2">
 <p>
 The Linux Kernel Module Programming Guide was originally written for the 2.2 kernels by Ori Pomerantz. Eventually, Ori no longer had time to maintain the document. After all, the Linux kernel is a fast moving target. Peter Jay Salzman took over maintenance and updated it for the 2.4 kernels. Eventually, Peter no longer had time to follow developments with the 2.6 kernel, so Michael Burian became a co-maintainer to update the document for the 2.6 kernels.  Bob Mottram updated the examples for 3.8 and 3.16 kernels and modified or updated some chapters.
 </p>
+</div>
+</div>
 
-<p>
-<b>Versioning and Notes</b>
-</p>
-
+<div id="outline-container-orgheadline3" class="outline-3">
+<h3 id="orgheadline3">Versioning and Notes</h3>
+<div class="outline-text-3" id="text-orgheadline3">
 <p>
 The Linux kernel is a moving target. There has always been a question whether the LKMPG should remove deprecated information or keep it around for historical sake. Michael Burian and I decided to create a new branch of the LKMPG for each new stable kernel version. So version LKMPG 3.16.x will address Linux kernel 3.16 and LKMPG 2.6.x will address Linux kernel 2.6. No attempt will be made to archive historical information; a person wishing this information should read the appropriately versioned LKMPG.
 </p>
@@ -390,21 +393,21 @@ The Linux kernel is a moving target. There has always been a question whether th
 <p>
 The source code and discussions should apply to most architectures, but I can't promise anything. One exception is Chapter 12, Interrupt Handlers, which should not work on any architecture except for x86.
 </p>
+</div>
+</div>
 
-<p>
-<b>Acknowledgements</b>
-</p>
-
+<div id="outline-container-orgheadline4" class="outline-3">
+<h3 id="orgheadline4">Acknowledgements</h3>
+<div class="outline-text-3" id="text-orgheadline4">
 <p>
 The following people have contributed corrections or good suggestions: Ignacio Martin, David Porter, Daniele Paolo Scarpazza, Dimo Velev, Francois Audeon, Horst Schirmeier and Bob Mottram.
 </p>
+</div>
+</div>
 
-<div id="outline-container-orgheadline11" class="outline-2">
-<h2 id="orgheadline11">Introduction</h2>
-<div class="outline-text-2" id="text-orgheadline11">
-</div><div id="outline-container-orgheadline1" class="outline-3">
-<h3 id="orgheadline1">What Is A Kernel Module?</h3>
-<div class="outline-text-3" id="text-orgheadline1">
+<div id="outline-container-orgheadline5" class="outline-3">
+<h3 id="orgheadline5">What Is A Kernel Module?</h3>
+<div class="outline-text-3" id="text-orgheadline5">
 <p>
 So, you want to write a kernel module. You know C, you've written a few normal programs to run as processes, and now you want to get to where the real action is, to where a single wild pointer can wipe out your file system and a core dump means a reboot.
 </p>
@@ -415,9 +418,9 @@ What exactly is a kernel module? Modules are pieces of code that can be loaded a
 </div>
 </div>
 
-<div id="outline-container-orgheadline2" class="outline-3">
-<h3 id="orgheadline2">Kernel module package</h3>
-<div class="outline-text-3" id="text-orgheadline2">
+<div id="outline-container-orgheadline6" class="outline-3">
+<h3 id="orgheadline6">Kernel module package</h3>
+<div class="outline-text-3" id="text-orgheadline6">
 <p>
 Linux distros provide the commands <i>modprobe</i>, <i>insmod</i> and <i>depmod</i> within a package.
 </p>
@@ -434,9 +437,9 @@ On Debian:
 </div>
 </div>
 
-<div id="outline-container-orgheadline3" class="outline-3">
-<h3 id="orgheadline3">What Modules are in my Kernel?</h3>
-<div class="outline-text-3" id="text-orgheadline3">
+<div id="outline-container-orgheadline7" class="outline-3">
+<h3 id="orgheadline7">What Modules are in my Kernel?</h3>
+<div class="outline-text-3" id="text-orgheadline7">
 <p>
 To discover what modules are already loaded within your current kernel use the command <b>lsmod</b>.
 </p>
@@ -469,17 +472,17 @@ This can be a long list, and you might prefer to search for something particular
 </div>
 </div>
 
-<div id="outline-container-orgheadline4" class="outline-3">
-<h3 id="orgheadline4">Do I need to download and compile the kernel?</h3>
-<div class="outline-text-3" id="text-orgheadline4">
+<div id="outline-container-orgheadline8" class="outline-3">
+<h3 id="orgheadline8">Do I need to download and compile the kernel?</h3>
+<div class="outline-text-3" id="text-orgheadline8">
 <p>
 For the purposes of following this guide you don't necessarily need to do that. However, it would be wise to run the examples within a test distro running on a virtual machine in order to avoid any possibility of messing up your system.
 </p>
 </div>
 </div>
-<div id="outline-container-orgheadline5" class="outline-3">
-<h3 id="orgheadline5">How Do I Install Modules Into The Kernel?</h3>
-<div class="outline-text-3" id="text-orgheadline5">
+<div id="outline-container-orgheadline9" class="outline-3">
+<h3 id="orgheadline9">How Do I Install Modules Into The Kernel?</h3>
+<div class="outline-text-3" id="text-orgheadline9">
 <p>
 When the kernel needs a feature that is not currently resident in the kernel, the kernel module daemon kmod[1] runs the <b>modprobe</b> command to load it. modprobe is passed a string in one of two forms:
 </p>
@@ -537,9 +540,9 @@ Now you know how modules get into the kernel. There's a bit more to the story if
 </p>
 </div>
 
-<div id="outline-container-orgheadline6" class="outline-4">
-<h4 id="orgheadline6">Header files</h4>
-<div class="outline-text-4" id="text-orgheadline6">
+<div id="outline-container-orgheadline10" class="outline-4">
+<h4 id="orgheadline10">Header files</h4>
+<div class="outline-text-4" id="text-orgheadline10">
 <p>
 Before you can compile anything you'll need the header files for your current kernel.
 </p>
@@ -563,21 +566,21 @@ This will tell you what kernel header files are available. Then for example:
 </div>
 </div>
 
-<div id="outline-container-orgheadline7" class="outline-4">
-<h4 id="orgheadline7">Before We Begin</h4>
-<div class="outline-text-4" id="text-orgheadline7">
+<div id="outline-container-orgheadline11" class="outline-4">
+<h4 id="orgheadline11">Before We Begin</h4>
+<div class="outline-text-4" id="text-orgheadline11">
 <p>
 Before we delve into code, there are a few issues we need to cover. Everyone's system is different and everyone has their own groove. Getting your first "hello world" program to compile and load correctly can sometimes be a trick. Rest assured, after you get over the initial hurdle of doing it for the first time, it will be smooth sailing thereafter.
 </p>
 </div>
 
-<ul class="org-ul"><li><a id="orgheadline8"></a>Modversioning<br  /><div class="outline-text-5" id="text-orgheadline8">
+<ul class="org-ul"><li><a id="orgheadline12"></a>Modversioning<br  /><div class="outline-text-5" id="text-orgheadline12">
 <p>
 A module compiled for one kernel won't load if you boot a different kernel unless you enable CONFIG_MODVERSIONS in the kernel. We won't go into module versioning until later in this guide. Until we cover modversions, the examples in the guide may not work if you're running a kernel with modversioning turned on. However, most stock Linux distro kernels come with it turned on. If you're having trouble loading the modules because of versioning errors, compile a kernel with modversioning turned off.
 </p>
 </div></li>
 
-<li><a id="orgheadline9"></a>Using X<br  /><div class="outline-text-5" id="text-orgheadline9">
+<li><a id="orgheadline13"></a>Using X<br  /><div class="outline-text-5" id="text-orgheadline13">
 <p>
 It is highly recommended that you type in, compile and load all the examples this guide discusses. It's also highly recommended you do this from a console. You should not be working on this stuff in X.
 </p>
@@ -587,7 +590,7 @@ Modules can't print to the screen like printf() can, but they can log informatio
 </p>
 </div></li>
 
-<li><a id="orgheadline10"></a>Compiling Issues and Kernel Version<br  /><div class="outline-text-5" id="text-orgheadline10">
+<li><a id="orgheadline14"></a>Compiling Issues and Kernel Version<br  /><div class="outline-text-5" id="text-orgheadline14">
 <p>
 Very often, Linux distros will distribute kernel source that has been patched in various non-standard ways, which may cause trouble.
 </p>
@@ -608,12 +611,12 @@ Ironically, this can also cause a problem. By default, gcc on your system may lo
 </div>
 </div>
 
-<div id="outline-container-orgheadline30" class="outline-2">
-<h2 id="orgheadline30">Hello World</h2>
-<div class="outline-text-2" id="text-orgheadline30">
-</div><div id="outline-container-orgheadline12" class="outline-3">
-<h3 id="orgheadline12">Hello, World (part 1): The Simplest Module</h3>
-<div class="outline-text-3" id="text-orgheadline12">
+<div id="outline-container-orgheadline33" class="outline-2">
+<h2 id="orgheadline33">Hello World</h2>
+<div class="outline-text-2" id="text-orgheadline33">
+</div><div id="outline-container-orgheadline15" class="outline-3">
+<h3 id="orgheadline15">Hello, World (part 1): The Simplest Module</h3>
+<div class="outline-text-3" id="text-orgheadline15">
 <p>
 When the first caveman programmer chiseled the first program on the walls of the first cave computer, it was a program to paint the string `Hello, world' in Antelope pictures. Roman programming textbooks began with the `Salut, Mundi' program. I don't know what happens to people who break with this tradition, but I think it's safer not to find out. We'll start with a series of hello world programs that demonstrate the different aspects of the basics of writing a kernel module.
 </p>
@@ -623,9 +626,9 @@ Here's the simplest module possible.
 </p>
 </div>
 
-<div id="outline-container-orgheadline13" class="outline-4">
-<h4 id="orgheadline13">Example: hello-1.c</h4>
-<div class="outline-text-4" id="text-orgheadline13">
+<div id="outline-container-orgheadline16" class="outline-4">
+<h4 id="orgheadline16">Example: hello-1.c</h4>
+<div class="outline-text-4" id="text-orgheadline16">
 <p>
 Make a test directory:
 </p>
@@ -770,7 +773,7 @@ Lastly, every kernel module needs to include linux/module.h. We needed to includ
 </p>
 </div>
 
-<ul class="org-ul"><li><a id="orgheadline14"></a>Introducing printk()<br  /><div class="outline-text-5" id="text-orgheadline14">
+<ul class="org-ul"><li><a id="orgheadline17"></a>Introducing printk()<br  /><div class="outline-text-5" id="text-orgheadline17">
 <p>
 Despite what you might think, <b>printk()</b> was not meant to communicate information to the user, even though we used it for exactly this purpose in hello-1! It happens to be a logging mechanism for the kernel, and is used to log information or give warnings. Therefore, each printk() statement comes with a priority, which is the &lt;1&gt; and KERN_ALERT you see. There are 8 priorities and the kernel has macros for them, so you don't have to use cryptic numbers, and you can view them (and their meanings) in <b>linux/kernel.h</b>. If you don't specify a priority level, the default priority, DEFAULT_MESSAGE_LOGLEVEL, will be used.
 </p>
@@ -784,7 +787,7 @@ If the priority is less than int console_loglevel, the message is printed on you
 </p>
 </div></li>
 
-<li><a id="orgheadline15"></a>About Compiling<br  /><div class="outline-text-5" id="text-orgheadline15">
+<li><a id="orgheadline18"></a>About Compiling<br  /><div class="outline-text-5" id="text-orgheadline18">
 <p>
 Kernel modules need to be compiled a bit differently from regular userspace apps. Former kernel versions required us to care much about these settings, which are usually stored in Makefiles. Although hierarchically organized, many redundant settings accumulated in sublevel Makefiles and made them large and rather difficult to maintain. Fortunately, there is a new way of doing these things, called kbuild, and the build process for external loadable modules is now fully integrated into the standard kernel build mechanism. To learn more on how to compile modules which are not part of the official kernel (such as all the examples you'll find in this guide), see file <b>linux/Documentation/kbuild/modules.txt</b>.
 </p>
@@ -802,17 +805,17 @@ Here's another exercise for the reader. See that comment above the return statem
 </div>
 </div>
 
-<div id="outline-container-orgheadline16" class="outline-3">
-<h3 id="orgheadline16">Hello World (part 2): Hello and Goodbye</h3>
-<div class="outline-text-3" id="text-orgheadline16">
+<div id="outline-container-orgheadline19" class="outline-3">
+<h3 id="orgheadline19">Hello World (part 2): Hello and Goodbye</h3>
+<div class="outline-text-3" id="text-orgheadline19">
 <p>
 In early kernel versions you had to use the <b>init_module</b> and <b>cleanup_module</b> functions, as in the first hello world example, but these days you can name those anything you want by using the <b>module_init</b> and <b>module_exit</b> macros. These macros are defined in <b>linux/init.h</b>. The only requirement is that your init and cleanup functions must be defined before calling the those macros, otherwise you'll get compilation errors. Here's an example of this technique:
 </p>
 </div>
 
-<div id="outline-container-orgheadline17" class="outline-4">
-<h4 id="orgheadline17">Example: hello-2.c</h4>
-<div class="outline-text-4" id="text-orgheadline17">
+<div id="outline-container-orgheadline20" class="outline-4">
+<h4 id="orgheadline20">Example: hello-2.c</h4>
+<div class="outline-text-4" id="text-orgheadline20">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/*</span>
@@ -845,9 +848,9 @@ So now we have two real kernel modules under our belt. Adding another module is
 </div>
 </div>
 
-<div id="outline-container-orgheadline18" class="outline-4">
-<h4 id="orgheadline18">Example: Makefile for both our modules</h4>
-<div class="outline-text-4" id="text-orgheadline18">
+<div id="outline-container-orgheadline21" class="outline-4">
+<h4 id="orgheadline21">Example: Makefile for both our modules</h4>
+<div class="outline-text-4" id="text-orgheadline21">
 <div class="org-src-container">
 
 <pre class="src src-makefile"><span class="org-variable-name">obj-m</span> += hello-1.o
@@ -869,9 +872,9 @@ you can see, some things get hardwired into the kernel (obj-y) but where are all
 </div>
 </div>
 
-<div id="outline-container-orgheadline19" class="outline-3">
-<h3 id="orgheadline19">Hello World (part 3): The __init and __exit Macros</h3>
-<div class="outline-text-3" id="text-orgheadline19">
+<div id="outline-container-orgheadline22" class="outline-3">
+<h3 id="orgheadline22">Hello World (part 3): The __init and __exit Macros</h3>
+<div class="outline-text-3" id="text-orgheadline22">
 <p>
 This demonstrates a feature of kernel 2.2 and later. Notice the change in the definitions of the init and cleanup functions. The <b>__init</b> macro causes the init function to be discarded and its memory freed once the init function finishes for built-in drivers, but not loadable modules. If you think about when the init function is invoked, this makes perfect sense.
 </p>
@@ -889,9 +892,9 @@ These macros are defined in <b>linux/init.h</b> and serve to free up kernel memo
 </p>
 </div>
 
-<div id="outline-container-orgheadline20" class="outline-4">
-<h4 id="orgheadline20">Example: hello-3.c</h4>
-<div class="outline-text-4" id="text-orgheadline20">
+<div id="outline-container-orgheadline23" class="outline-4">
+<h4 id="orgheadline23">Example: hello-3.c</h4>
+<div class="outline-text-4" id="text-orgheadline23">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/*</span>
@@ -922,9 +925,9 @@ module_exit(hello_3_exit);
 </div>
 </div>
 
-<div id="outline-container-orgheadline21" class="outline-3">
-<h3 id="orgheadline21">Hello World (part 4): Licensing and Module Documentation</h3>
-<div class="outline-text-3" id="text-orgheadline21">
+<div id="outline-container-orgheadline24" class="outline-3">
+<h3 id="orgheadline24">Hello World (part 4): Licensing and Module Documentation</h3>
+<div class="outline-text-3" id="text-orgheadline24">
 <p>
 Honestly, who loads or even cares about proprietary modules? If you do then you might have seen something like this:
 </p>
@@ -947,9 +950,9 @@ To reference what license you're using a macro is available called <b>MODULE_LIC
 </p>
 </div>
 
-<div id="outline-container-orgheadline22" class="outline-4">
-<h4 id="orgheadline22">Example: hello-4.c</h4>
-<div class="outline-text-4" id="text-orgheadline22">
+<div id="outline-container-orgheadline25" class="outline-4">
+<h4 id="orgheadline25">Example: hello-4.c</h4>
+<div class="outline-text-4" id="text-orgheadline25">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/*</span>
@@ -983,9 +986,9 @@ module_exit(cleanup_hello_4);
 </div>
 </div>
 
-<div id="outline-container-orgheadline23" class="outline-3">
-<h3 id="orgheadline23">Passing Command Line Arguments to a Module</h3>
-<div class="outline-text-3" id="text-orgheadline23">
+<div id="outline-container-orgheadline26" class="outline-3">
+<h3 id="orgheadline26">Passing Command Line Arguments to a Module</h3>
+<div class="outline-text-3" id="text-orgheadline26">
 <p>
 Modules can take command line arguments, but not with the argc/argv you might be used to.
 </p>
@@ -1030,9 +1033,9 @@ Lastly, there's a macro function, <b>MODULE_PARM_DESC()</b>, that is used to doc
 </div>
 
 
-<div id="outline-container-orgheadline24" class="outline-4">
-<h4 id="orgheadline24">Example: hello-5.c</h4>
-<div class="outline-text-4" id="text-orgheadline24">
+<div id="outline-container-orgheadline27" class="outline-4">
+<h4 id="orgheadline27">Example: hello-5.c</h4>
+<div class="outline-text-4" id="text-orgheadline27">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/*</span>
@@ -1145,9 +1148,9 @@ hello-5.o: invalid argument syntax for mylong: 'h'
 </div>
 </div>
 
-<div id="outline-container-orgheadline25" class="outline-3">
-<h3 id="orgheadline25">Modules Spanning Multiple Files</h3>
-<div class="outline-text-3" id="text-orgheadline25">
+<div id="outline-container-orgheadline28" class="outline-3">
+<h3 id="orgheadline28">Modules Spanning Multiple Files</h3>
+<div class="outline-text-3" id="text-orgheadline28">
 <p>
 Sometimes it makes sense to divide a kernel module between several source files.
 </p>
@@ -1157,9 +1160,9 @@ Here's an example of such a kernel module.
 </p>
 </div>
 
-<div id="outline-container-orgheadline26" class="outline-4">
-<h4 id="orgheadline26">Example: start.c</h4>
-<div class="outline-text-4" id="text-orgheadline26">
+<div id="outline-container-orgheadline29" class="outline-4">
+<h4 id="orgheadline29">Example: start.c</h4>
+<div class="outline-text-4" id="text-orgheadline29">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/*</span>
@@ -1184,9 +1187,9 @@ The next file:
 </div>
 
 
-<div id="outline-container-orgheadline27" class="outline-4">
-<h4 id="orgheadline27">Example: stop.c</h4>
-<div class="outline-text-4" id="text-orgheadline27">
+<div id="outline-container-orgheadline30" class="outline-4">
+<h4 id="orgheadline30">Example: stop.c</h4>
+<div class="outline-text-4" id="text-orgheadline30">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/*</span>
@@ -1210,9 +1213,9 @@ And finally, the makefile:
 </div>
 
 
-<div id="outline-container-orgheadline28" class="outline-4">
-<h4 id="orgheadline28">Example: Makefile</h4>
-<div class="outline-text-4" id="text-orgheadline28">
+<div id="outline-container-orgheadline31" class="outline-4">
+<h4 id="orgheadline31">Example: Makefile</h4>
+<div class="outline-text-4" id="text-orgheadline31">
 <div class="org-src-container">
 
 <pre class="src src-makefile"><span class="org-variable-name">obj-m</span> += hello-1.o
@@ -1238,9 +1241,9 @@ This is the complete makefile for all the examples we've seen so far. The first
 </div>
 </div>
 
-<div id="outline-container-orgheadline29" class="outline-3">
-<h3 id="orgheadline29">Building modules for a precompiled kernel</h3>
-<div class="outline-text-3" id="text-orgheadline29">
+<div id="outline-container-orgheadline32" class="outline-3">
+<h3 id="orgheadline32">Building modules for a precompiled kernel</h3>
+<div class="outline-text-3" id="text-orgheadline32">
 <p>
 Obviously, we strongly suggest you to recompile your kernel, so that you can enable a number of useful debugging features, such as forced module unloading (<b>MODULE_FORCE_UNLOAD</b>): when this option is enabled, you can force the kernel to unload a module even when it believes it is unsafe, via a <b>sudo rmmod -f module</b> command. This option can save you a lot of time and a number of reboots during the development of a module. If you don't want to recompile your kernel then you should consider running the examples within a test distro on a virtual machine. If you mess anything up then you can easily reboot or restore the VM.
 </p>
@@ -1337,12 +1340,12 @@ If you do not desire to actually compile the kernel, you can interrupt the build
 </div>
 </div>
 
-<div id="outline-container-orgheadline38" class="outline-2">
-<h2 id="orgheadline38">Preliminaries</h2>
-<div class="outline-text-2" id="text-orgheadline38">
-</div><div id="outline-container-orgheadline31" class="outline-3">
-<h3 id="orgheadline31">How modules begin and end</h3>
-<div class="outline-text-3" id="text-orgheadline31">
+<div id="outline-container-orgheadline41" class="outline-2">
+<h2 id="orgheadline41">Preliminaries</h2>
+<div class="outline-text-2" id="text-orgheadline41">
+</div><div id="outline-container-orgheadline34" class="outline-3">
+<h3 id="orgheadline34">How modules begin and end</h3>
+<div class="outline-text-3" id="text-orgheadline34">
 <p>
 A program usually begins with a <b>main()</b> function, executes a bunch of instructions and terminates upon completion of those instructions. Kernel modules work a bit differently. A module always begin with either the init_module or the function you specify with module_init call. This is the entry function for modules; it tells the kernel what functionality the module provides and sets up the kernel to run the module's functions when they're needed. Once it does this, entry function returns and the module does nothing until the kernel wants to do something with the code that the module provides.
 </p>
@@ -1357,9 +1360,9 @@ Every module must have an entry function and an exit function. Since there's mor
 </div>
 </div>
 
-<div id="outline-container-orgheadline32" class="outline-3">
-<h3 id="orgheadline32">Functions available to modules</h3>
-<div class="outline-text-3" id="text-orgheadline32">
+<div id="outline-container-orgheadline35" class="outline-3">
+<h3 id="orgheadline35">Functions available to modules</h3>
+<div class="outline-text-3" id="text-orgheadline35">
 <p>
 Programmers use functions they don't define all the time. A prime example of this is <b>printf()</b>. You use these library functions which are provided by the standard C library, libc. The definitions for these functions don't actually enter your program until the linking stage, which insures that the code (for printf() for example) is available, and fixes the call instruction to point to that code.
 </p>
@@ -1394,9 +1397,9 @@ You can even write modules to replace the kernel's system calls, which we'll do
 </div>
 </div>
 
-<div id="outline-container-orgheadline33" class="outline-3">
-<h3 id="orgheadline33">User Space vs Kernel Space</h3>
-<div class="outline-text-3" id="text-orgheadline33">
+<div id="outline-container-orgheadline36" class="outline-3">
+<h3 id="orgheadline36">User Space vs Kernel Space</h3>
+<div class="outline-text-3" id="text-orgheadline36">
 <p>
 A kernel is all about access to resources, whether the resource in question happens to be a video card, a hard drive or even memory. Programs often compete for the same resource. As I just saved this document, updatedb started updating the locate database. My vim session and updatedb are both using the hard drive concurrently. The kernel needs to keep things orderly, and not give users access to resources whenever they feel like it. To this end, a CPU can run in different modes. Each mode gives a different level of freedom to do what you want on the system. The Intel 80386 architecture had 4 of these modes, which were called rings. Unix uses only two rings; the highest ring (ring 0, also known as `supervisor mode' where everything is allowed to happen) and the lowest ring, which is called `user mode'.
 </p>
@@ -1407,9 +1410,9 @@ Recall the discussion about library functions vs system calls. Typically, you us
 </div>
 </div>
 
-<div id="outline-container-orgheadline34" class="outline-3">
-<h3 id="orgheadline34">Name Space</h3>
-<div class="outline-text-3" id="text-orgheadline34">
+<div id="outline-container-orgheadline37" class="outline-3">
+<h3 id="orgheadline37">Name Space</h3>
+<div class="outline-text-3" id="text-orgheadline37">
 <p>
 When you write a small C program, you use variables which are convenient and make sense to the reader. If, on the other hand, you're writing routines which will be part of a bigger problem, any global variables you have are part of a community of other peoples' global variables; some of the variable names can clash. When a program has lots of global variables which aren't meaningful enough to be distinguished, you get namespace pollution. In large projects, effort must be made to remember reserved names, and to find ways to develop a scheme for naming unique variable names and symbols.
 </p>
@@ -1424,9 +1427,9 @@ The file <b>/proc/kallsyms</b> holds all the symbols that the kernel knows about
 </div>
 </div>
 
-<div id="outline-container-orgheadline35" class="outline-3">
-<h3 id="orgheadline35">Code space</h3>
-<div class="outline-text-3" id="text-orgheadline35">
+<div id="outline-container-orgheadline38" class="outline-3">
+<h3 id="orgheadline38">Code space</h3>
+<div class="outline-text-3" id="text-orgheadline38">
 <p>
 Memory management is a very complicated subject&#x2014;the majority of O'Reilly's "<i>Understanding The Linux Kernel</i>" is just on memory management! We're not setting out to be experts on memory managements, but we do need to know a couple of facts to even begin worrying about writing real modules.
 </p>
@@ -1445,15 +1448,15 @@ By the way, I would like to point out that the above discussion is true for any
 </div>
 </div>
 
-<div id="outline-container-orgheadline36" class="outline-3">
-<h3 id="orgheadline36">Device Drivers</h3>
-<div class="outline-text-3" id="text-orgheadline36">
+<div id="outline-container-orgheadline39" class="outline-3">
+<h3 id="orgheadline39">Device Drivers</h3>
+<div class="outline-text-3" id="text-orgheadline39">
 <p>
 One class of module is the device driver, which provides functionality for hardware like a TV card or a serial port. On unix, each piece of hardware is represented by a file located in /dev named a device file which provides the means to communicate with the hardware. The device driver provides the communication on behalf of a user program. So the es1370.o sound card device driver might connect the /dev/sound device file to the Ensoniq IS1370 sound card. A userspace program like mp3blaster can use /dev/sound without ever knowing what kind of sound card is installed.
 </p>
 </div>
 
-<ul class="org-ul"><li><a id="orgheadline37"></a>Major and Minor Numbers<br  /><div class="outline-text-5" id="text-orgheadline37">
+<ul class="org-ul"><li><a id="orgheadline40"></a>Major and Minor Numbers<br  /><div class="outline-text-5" id="text-orgheadline40">
 <p>
 Let's look at some device files. Here are device files which represent the first three partitions on the primary master IDE hard drive:
 </p>
@@ -1519,12 +1522,12 @@ By now you can look at these two device files and know instantly that they are b
 </div>
 </div>
 
-<div id="outline-container-orgheadline46" class="outline-2">
-<h2 id="orgheadline46">Character Device drivers</h2>
-<div class="outline-text-2" id="text-orgheadline46">
-</div><div id="outline-container-orgheadline39" class="outline-3">
-<h3 id="orgheadline39">The file_operations Structure</h3>
-<div class="outline-text-3" id="text-orgheadline39">
+<div id="outline-container-orgheadline49" class="outline-2">
+<h2 id="orgheadline49">Character Device drivers</h2>
+<div class="outline-text-2" id="text-orgheadline49">
+</div><div id="outline-container-orgheadline42" class="outline-3">
+<h3 id="orgheadline42">The file_operations Structure</h3>
+<div class="outline-text-3" id="text-orgheadline42">
 <p>
 The file_operations structure is defined in <b>linux/fs.h</b>, and holds pointers to functions defined by the driver that perform various operations on the device. Each field of the structure corresponds to the address of some function defined by the driver to handle a requested operation.
 </p>
@@ -1612,9 +1615,9 @@ An instance of struct file_operations containing pointers to functions that are
 </div>
 </div>
 
-<div id="outline-container-orgheadline40" class="outline-3">
-<h3 id="orgheadline40">The file structure</h3>
-<div class="outline-text-3" id="text-orgheadline40">
+<div id="outline-container-orgheadline43" class="outline-3">
+<h3 id="orgheadline43">The file structure</h3>
+<div class="outline-text-3" id="text-orgheadline43">
 <p>
 Each device is represented in the kernel by a file structure, which is defined in <b>linux/fs.h</b>. Be aware that a file is a kernel level structure and never appears in a user space program. It's not the same thing as a FILE, which is defined by glibc and would never appear in a kernel space function. Also, its name is a bit misleading; it represents an abstract open `file', not a file on a disk, which is represented by a structure named inode.
 </p>
@@ -1629,9 +1632,9 @@ Go ahead and look at the definition of file. Most of the entries you see, like s
 </div>
 </div>
 
-<div id="outline-container-orgheadline41" class="outline-3">
-<h3 id="orgheadline41">Registering A Device</h3>
-<div class="outline-text-3" id="text-orgheadline41">
+<div id="outline-container-orgheadline44" class="outline-3">
+<h3 id="orgheadline44">Registering A Device</h3>
+<div class="outline-text-3" id="text-orgheadline44">
 <p>
 As discussed earlier, char devices are accessed through device files, usually located in /dev[7]. The major number tells you which driver handles which device file. The minor number is used only by the driver itself to differentiate which device it's operating on, just in case the driver handles more than one device.
 </p>
@@ -1660,9 +1663,9 @@ If you pass a major number of 0 to register_chrdev, the return value will be the
 </div>
 </div>
 
-<div id="outline-container-orgheadline42" class="outline-3">
-<h3 id="orgheadline42">Unregistering A Device</h3>
-<div class="outline-text-3" id="text-orgheadline42">
+<div id="outline-container-orgheadline45" class="outline-3">
+<h3 id="orgheadline45">Unregistering A Device</h3>
+<div class="outline-text-3" id="text-orgheadline45">
 <p>
 We can't allow the kernel module to be rmmod'ed whenever root feels like it. If the device file is opened by a process and then we remove the kernel module, using the file would cause a call to the memory location where the appropriate function (read/write) used to be. If we're lucky, no other code was loaded there, and we'll get an ugly error message. If we're unlucky, another kernel module was loaded into the same location, which means a jump into the middle of another function within the kernel. The results of this would be impossible to predict, but they can't be very positive.
 </p>
@@ -1682,9 +1685,9 @@ It's important to keep the counter accurate; if you ever do lose track of the co
 </div>
 </div>
 
-<div id="outline-container-orgheadline43" class="outline-3">
-<h3 id="orgheadline43">chardev.c</h3>
-<div class="outline-text-3" id="text-orgheadline43">
+<div id="outline-container-orgheadline46" class="outline-3">
+<h3 id="orgheadline46">chardev.c</h3>
+<div class="outline-text-3" id="text-orgheadline46">
 <p>
 The next code sample creates a char driver named chardev. You can cat its device file.
 </p>
@@ -1700,9 +1703,9 @@ The next code sample creates a char driver named chardev. You can cat its device
 </p>
 </div>
 
-<div id="outline-container-orgheadline44" class="outline-4">
-<h4 id="orgheadline44">Example: chardev.c</h4>
-<div class="outline-text-4" id="text-orgheadline44">
+<div id="outline-container-orgheadline47" class="outline-4">
+<h4 id="orgheadline47">Example: chardev.c</h4>
+<div class="outline-text-4" id="text-orgheadline47">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/*</span>
@@ -1877,9 +1880,9 @@ The next code sample creates a char driver named chardev. You can cat its device
 </div>
 </div>
 
-<div id="outline-container-orgheadline45" class="outline-3">
-<h3 id="orgheadline45">Writing Modules for Multiple Kernel Versions</h3>
-<div class="outline-text-3" id="text-orgheadline45">
+<div id="outline-container-orgheadline48" class="outline-3">
+<h3 id="orgheadline48">Writing Modules for Multiple Kernel Versions</h3>
+<div class="outline-text-3" id="text-orgheadline48">
 <p>
 The system calls, which are the major interface the kernel shows to the processes, generally stay the same across versions. A new system call may be added, but usually the old ones will behave exactly like they used to. This is necessary for backward compatibility &#x2013; a new kernel version is not supposed to break regular processes. In most cases, the device files will also remain the same. On the other hand, the internal interfaces within the kernel can and do change between versions.
 </p>
@@ -1903,9 +1906,9 @@ You might already have noticed that recent kernels look different. In case you h
 </div>
 </div>
 
-<div id="outline-container-orgheadline47" class="outline-2">
-<h2 id="orgheadline47">The /proc File System</h2>
-<div class="outline-text-2" id="text-orgheadline47">
+<div id="outline-container-orgheadline50" class="outline-2">
+<h2 id="orgheadline50">The /proc File System</h2>
+<div class="outline-text-2" id="text-orgheadline50">
 <p>
 In Linux, there is an additional mechanism for the kernel and kernel modules to send information to processes &#x2014; the <b>/proc</b> file system. Originally designed to allow easy access to information about processes (hence the name), it is now used by every bit of the kernel which has something interesting to report, such as <b>/proc/modules</b> which provides the list of modules and <b>/proc/meminfo</b> which stats memory usage statistics.
 </p>
@@ -1942,9 +1945,9 @@ HelloWorld!
 </div>
 </div>
 
-<div id="outline-container-orgheadline48" class="outline-4">
-<h4 id="orgheadline48">Example: procfs1.c</h4>
-<div class="outline-text-4" id="text-orgheadline48">
+<div id="outline-container-orgheadline51" class="outline-4">
+<h4 id="orgheadline51">Example: procfs1.c</h4>
+<div class="outline-text-4" id="text-orgheadline51">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-preprocessor">#include</span> <span class="org-string">&lt;linux/module.h&gt;</span>
@@ -1998,9 +2001,9 @@ HelloWorld!
 </div>
 </div>
 
-<div id="outline-container-orgheadline49" class="outline-3">
-<h3 id="orgheadline49">Read and Write a /proc File</h3>
-<div class="outline-text-3" id="text-orgheadline49">
+<div id="outline-container-orgheadline52" class="outline-3">
+<h3 id="orgheadline52">Read and Write a /proc File</h3>
+<div class="outline-text-3" id="text-orgheadline52">
 <p>
 We have seen a very simple example for a /proc file where we only read the file /proc/helloworld. It's also possible to write in a /proc file. It works the same way as read, a function is called when the /proc file is written. But there is a little difference with read, data comes from user, so you have to import data from user space to kernel space (with copy_from_user or get_user)
 </p>
@@ -2014,9 +2017,9 @@ The only memory segment accessible to a process is its own, so when writing regu
 </p>
 </div>
 
-<div id="outline-container-orgheadline50" class="outline-4">
-<h4 id="orgheadline50">Example: procfs2.c</h4>
-<div class="outline-text-4" id="text-orgheadline50">
+<div id="outline-container-orgheadline53" class="outline-4">
+<h4 id="orgheadline53">Example: procfs2.c</h4>
+<div class="outline-text-4" id="text-orgheadline53">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-doc">/**</span>
@@ -2123,9 +2126,9 @@ The only memory segment accessible to a process is its own, so when writing regu
 </div>
 </div>
 
-<div id="outline-container-orgheadline51" class="outline-3">
-<h3 id="orgheadline51">Manage /proc file with standard filesystem</h3>
-<div class="outline-text-3" id="text-orgheadline51">
+<div id="outline-container-orgheadline54" class="outline-3">
+<h3 id="orgheadline54">Manage /proc file with standard filesystem</h3>
+<div class="outline-text-3" id="text-orgheadline54">
 <p>
 We have seen how to read and write a /proc file with the /proc interface. But it's also possible to manage /proc file with inodes. The main concern is to use advanced functions, like permissions.
 </p>
@@ -2143,9 +2146,9 @@ It's important to note that the standard roles of read and write are reversed in
 </p>
 </div>
 
-<div id="outline-container-orgheadline52" class="outline-4">
-<h4 id="orgheadline52">Example: procfs3.c</h4>
-<div class="outline-text-4" id="text-orgheadline52">
+<div id="outline-container-orgheadline55" class="outline-4">
+<h4 id="orgheadline55">Example: procfs3.c</h4>
+<div class="outline-text-4" id="text-orgheadline55">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/*</span>
@@ -2354,9 +2357,9 @@ Still hungry for procfs examples? Well, first of all keep in mind, there are rum
 </div>
 </div>
 
-<div id="outline-container-orgheadline53" class="outline-3">
-<h3 id="orgheadline53">Manage /proc file with seq_file</h3>
-<div class="outline-text-3" id="text-orgheadline53">
+<div id="outline-container-orgheadline56" class="outline-3">
+<h3 id="orgheadline56">Manage /proc file with seq_file</h3>
+<div class="outline-text-3" id="text-orgheadline56">
 <p>
 As we have seen, writing a /proc file may be quite "complex". So to help
 people writting /proc file, there is an API named seq_file that helps
@@ -2373,9 +2376,9 @@ BE CARREFUL: when a sequence is finished, another one starts. That means that at
 </p>
 </div>
 
-<div id="outline-container-orgheadline54" class="outline-4">
-<h4 id="orgheadline54">Figure: How seq_file works</h4>
-<div class="outline-text-4" id="text-orgheadline54">
+<div id="outline-container-orgheadline57" class="outline-4">
+<h4 id="orgheadline57">Figure: How seq_file works</h4>
+<div class="outline-text-4" id="text-orgheadline57">
 
 <div class="figure">
 <p><img src="img/seq_file.png" alt="seq_file.png" />
@@ -2396,9 +2399,9 @@ Seq_file provides basic functions for file_operations, as seq_read, seq_lseek, a
 </div>
 </div>
 
-<div id="outline-container-orgheadline55" class="outline-4">
-<h4 id="orgheadline55">Example: procfs4.c</h4>
-<div class="outline-text-4" id="text-orgheadline55">
+<div id="outline-container-orgheadline58" class="outline-4">
+<h4 id="orgheadline58">Example: procfs4.c</h4>
+<div class="outline-text-4" id="text-orgheadline58">
 <p>
 TODO: this will be out of date because of create_proc_entry
 </p>
@@ -2557,9 +2560,9 @@ You can also read the code of fs/seq_file.c in the linux kernel.
 </div>
 </div>
 
-<div id="outline-container-orgheadline56" class="outline-2">
-<h2 id="orgheadline56">sysfs: Interacting with your module</h2>
-<div class="outline-text-2" id="text-orgheadline56">
+<div id="outline-container-orgheadline59" class="outline-2">
+<h2 id="orgheadline59">sysfs: Interacting with your module</h2>
+<div class="outline-text-2" id="text-orgheadline59">
 <p>
 <i>sysfs</i> allows you to interact with the running kernel by reading or setting variables inside of modules. This can be useful for debugging purposes, or just as an interface for userland applications or scripts.
 </p>
@@ -2569,9 +2572,9 @@ An example of a hello world module which includes a variable accessible via sysf
 </p>
 </div>
 
-<div id="outline-container-orgheadline57" class="outline-3">
-<h3 id="orgheadline57">Example: hello-sysfs.c</h3>
-<div class="outline-text-3" id="text-orgheadline57">
+<div id="outline-container-orgheadline60" class="outline-3">
+<h3 id="orgheadline60">Example: hello-sysfs.c</h3>
+<div class="outline-text-3" id="text-orgheadline60">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/*</span>
@@ -2700,9 +2703,9 @@ Finally, remove the test module:
 </div>
 </div>
 
-<div id="outline-container-orgheadline58" class="outline-2">
-<h2 id="orgheadline58">Talking To Device Files</h2>
-<div class="outline-text-2" id="text-orgheadline58">
+<div id="outline-container-orgheadline61" class="outline-2">
+<h2 id="orgheadline61">Talking To Device Files</h2>
+<div class="outline-text-2" id="text-orgheadline61">
 <p>
 Device files are supposed to represent physical devices. Most physical devices are used for output as well as input, so there has to be some mechanism for device drivers in the kernel to get the output to send to the device from processes. This is done by opening the device file for output and writing to it, just like writing to a file. In the following example, this is implemented by device_write.
 </p>
@@ -2724,9 +2727,9 @@ If you want to use ioctls in your own kernel modules, it is best to receive an o
 </p>
 </div>
 
-<div id="outline-container-orgheadline59" class="outline-3">
-<h3 id="orgheadline59">Example: chardev.c</h3>
-<div class="outline-text-3" id="text-orgheadline59">
+<div id="outline-container-orgheadline62" class="outline-3">
+<h3 id="orgheadline62">Example: chardev.c</h3>
+<div class="outline-text-3" id="text-orgheadline62">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/*</span>
@@ -3009,9 +3012,9 @@ If you want to use ioctls in your own kernel modules, it is best to receive an o
 </div>
 </div>
 
-<div id="outline-container-orgheadline60" class="outline-3">
-<h3 id="orgheadline60">Example: chardev.h</h3>
-<div class="outline-text-3" id="text-orgheadline60">
+<div id="outline-container-orgheadline63" class="outline-3">
+<h3 id="orgheadline63">Example: chardev.h</h3>
+<div class="outline-text-3" id="text-orgheadline63">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/*</span>
@@ -3085,9 +3088,9 @@ If you want to use ioctls in your own kernel modules, it is best to receive an o
 </div>
 </div>
 
-<div id="outline-container-orgheadline61" class="outline-3">
-<h3 id="orgheadline61">Example: ioctl.c</h3>
-<div class="outline-text-3" id="text-orgheadline61">
+<div id="outline-container-orgheadline64" class="outline-3">
+<h3 id="orgheadline64">Example: ioctl.c</h3>
+<div class="outline-text-3" id="text-orgheadline64">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/*</span>
@@ -3196,9 +3199,9 @@ If you want to use ioctls in your own kernel modules, it is best to receive an o
 </div>
 </div>
 
-<div id="outline-container-orgheadline62" class="outline-2">
-<h2 id="orgheadline62">System Calls</h2>
-<div class="outline-text-2" id="text-orgheadline62">
+<div id="outline-container-orgheadline65" class="outline-2">
+<h2 id="orgheadline65">System Calls</h2>
+<div class="outline-text-2" id="text-orgheadline65">
 <p>
 So far, the only thing we've done was to use well defined kernel mechanisms to register <b>/proc</b> files and device handlers. This is fine if you want to do something the kernel programmers thought you'd want, such as write a device driver. But what if you want to do something unusual, to change the behavior of the system in some way? Then, you're mostly on your own.
 </p>
@@ -3244,9 +3247,9 @@ Note that all the related problems make syscall stealing unfeasiable for product
 </p>
 </div>
 
-<div id="outline-container-orgheadline63" class="outline-3">
-<h3 id="orgheadline63">Example: syscall.c</h3>
-<div class="outline-text-3" id="text-orgheadline63">
+<div id="outline-container-orgheadline66" class="outline-3">
+<h3 id="orgheadline66">Example: syscall.c</h3>
+<div class="outline-text-3" id="text-orgheadline66">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/*</span>
@@ -3412,9 +3415,9 @@ asmlinkage <span class="org-type">int</span> <span class="org-function-name">our
 </div>
 </div>
 
-<div id="outline-container-orgheadline64" class="outline-2">
-<h2 id="orgheadline64">Blocking Processes</h2>
-<div class="outline-text-2" id="text-orgheadline64">
+<div id="outline-container-orgheadline67" class="outline-2">
+<h2 id="orgheadline67">Blocking Processes</h2>
+<div class="outline-text-2" id="text-orgheadline67">
 <p>
 What do you do when somebody asks you for something you can't do right away? If you're a human being and you're bothered by a human being, the only thing you can say is: <i>"Not right now, I'm busy. Go away!"</i>. But if you're a kernel module and you're bothered by a process, you have another possibility. You can put the process to sleep until you can service it. After all, processes are being put to sleep by the kernel and woken up all the time (that's the way multiple processes appear to run on the same time on a single CPU).
 </p>
@@ -3466,9 +3469,9 @@ hostname:~/lkmpg-examples/09-BlockingProcesses#
 </div>
 </div>
 
-<div id="outline-container-orgheadline65" class="outline-3">
-<h3 id="orgheadline65">Example: sleep.c</h3>
-<div class="outline-text-3" id="text-orgheadline65">
+<div id="outline-container-orgheadline68" class="outline-3">
+<h3 id="orgheadline68">Example: sleep.c</h3>
+<div class="outline-text-3" id="text-orgheadline68">
 <p>
 TODO: this will be out of date because of create_proc_entry
 </p>
@@ -3791,9 +3794,9 @@ DECLARE_WAIT_QUEUE_HEAD(WaitQ);
 </div>
 </div>
 
-<div id="outline-container-orgheadline66" class="outline-3">
-<h3 id="orgheadline66">Example: cat_noblock.c</h3>
-<div class="outline-text-3" id="text-orgheadline66">
+<div id="outline-container-orgheadline69" class="outline-3">
+<h3 id="orgheadline69">Example: cat_noblock.c</h3>
+<div class="outline-text-3" id="text-orgheadline69">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/* </span><span class="org-comment">cat_noblock.c - open a file and display its contents, but exit rather than</span>
@@ -3870,12 +3873,12 @@ DECLARE_WAIT_QUEUE_HEAD(WaitQ);
 </div>
 </div>
 
-<div id="outline-container-orgheadline71" class="outline-2">
-<h2 id="orgheadline71">Replacing Printks</h2>
-<div class="outline-text-2" id="text-orgheadline71">
-</div><div id="outline-container-orgheadline67" class="outline-3">
-<h3 id="orgheadline67">Replacing printk</h3>
-<div class="outline-text-3" id="text-orgheadline67">
+<div id="outline-container-orgheadline74" class="outline-2">
+<h2 id="orgheadline74">Replacing Printks</h2>
+<div class="outline-text-2" id="text-orgheadline74">
+</div><div id="outline-container-orgheadline70" class="outline-3">
+<h3 id="orgheadline70">Replacing printk</h3>
+<div class="outline-text-3" id="text-orgheadline70">
 <p>
 In Section 1.2.1.2, I said that X and kernel module programming don't mix. That's true for developing kernel modules, but in actual use, you want to be able to send messages to whichever tty[15] the command to load the module came from.
 </p>
@@ -3885,9 +3888,9 @@ The way this is done is by using current, a pointer to the currently running tas
 </p>
 </div>
 
-<div id="outline-container-orgheadline68" class="outline-4">
-<h4 id="orgheadline68">Example: print_string.c</h4>
-<div class="outline-text-4" id="text-orgheadline68">
+<div id="outline-container-orgheadline71" class="outline-4">
+<h4 id="orgheadline71">Example: print_string.c</h4>
+<div class="outline-text-4" id="text-orgheadline71">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/*</span>
@@ -4004,9 +4007,9 @@ module_exit(print_string_exit);
 </div>
 </div>
 
-<div id="outline-container-orgheadline69" class="outline-3">
-<h3 id="orgheadline69">Flashing keyboard LEDs</h3>
-<div class="outline-text-3" id="text-orgheadline69">
+<div id="outline-container-orgheadline72" class="outline-3">
+<h3 id="orgheadline72">Flashing keyboard LEDs</h3>
+<div class="outline-text-3" id="text-orgheadline72">
 <p>
 In certain conditions, you may desire a simpler and more direct way to communicate to the external world. Flashing keyboard LEDs can be such a solution: It is an immediate way to attract attention or to display a status condition. Keyboard LEDs are present on every hardware, they are always visible, they do not need any setup, and their use is rather simple and non-intrusive, compared to writing to a tty or a file.
 </p>
@@ -4016,9 +4019,9 @@ The following source code illustrates a minimal kernel module which, when loaded
 </p>
 </div>
 
-<div id="outline-container-orgheadline70" class="outline-4">
-<h4 id="orgheadline70">Example: kbleds.c</h4>
-<div class="outline-text-4" id="text-orgheadline70">
+<div id="outline-container-orgheadline73" class="outline-4">
+<h4 id="orgheadline73">Example: kbleds.c</h4>
+<div class="outline-text-4" id="text-orgheadline73">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/*</span>
@@ -4138,9 +4141,9 @@ it does not show up in production code.
 </div>
 </div>
 
-<div id="outline-container-orgheadline72" class="outline-2">
-<h2 id="orgheadline72">Scheduling Tasks</h2>
-<div class="outline-text-2" id="text-orgheadline72">
+<div id="outline-container-orgheadline75" class="outline-2">
+<h2 id="orgheadline75">Scheduling Tasks</h2>
+<div class="outline-text-2" id="text-orgheadline75">
 <p>
 Very often, we have "housekeeping" tasks which have to be done at a certain time, or every so often. If the task is to be done by a process, we do it by putting it in the crontab file. If the task is to be done by a kernel module, we have two possibilities. The first is to put a process in the crontab file which will wake up the module by a system call when necessary, for example by opening a file. This is terribly inefficient, however &#x2013; we run a new process off of crontab, read a new executable to memory, and all this just to wake up a kernel module which is in memory anyway.
 </p>
@@ -4154,9 +4157,9 @@ There's one more point we need to remember here. When a module is removed by rmm
 </p>
 </div>
 
-<div id="outline-container-orgheadline73" class="outline-3">
-<h3 id="orgheadline73">Example: sched.c</h3>
-<div class="outline-text-3" id="text-orgheadline73">
+<div id="outline-container-orgheadline76" class="outline-3">
+<h3 id="orgheadline76">Example: sched.c</h3>
+<div class="outline-text-3" id="text-orgheadline76">
 <p>
 TODO: test this out. Not sure about the proc creation
 </p>
@@ -4337,12 +4340,12 @@ MODULE_LICENSE(<span class="org-string">"GPL"</span>);
 </div>
 </div>
 
-<div id="outline-container-orgheadline77" class="outline-2">
-<h2 id="orgheadline77">Interrupt Handlers</h2>
-<div class="outline-text-2" id="text-orgheadline77">
-</div><div id="outline-container-orgheadline74" class="outline-3">
-<h3 id="orgheadline74">Interrupt Handlers</h3>
-<div class="outline-text-3" id="text-orgheadline74">
+<div id="outline-container-orgheadline80" class="outline-2">
+<h2 id="orgheadline80">Interrupt Handlers</h2>
+<div class="outline-text-2" id="text-orgheadline80">
+</div><div id="outline-container-orgheadline77" class="outline-3">
+<h3 id="orgheadline77">Interrupt Handlers</h3>
+<div class="outline-text-3" id="text-orgheadline77">
 <p>
 Except for the last chapter, everything we did in the kernel so far we've done as a response to a process asking for it, either by dealing with a special file, sending an ioctl(), or issuing a system call. But the job of the kernel isn't just to respond to process requests. Another job, which is every bit as important, is to speak to the hardware connected to the machine.
 </p>
@@ -4369,9 +4372,9 @@ Then, from within the interrupt handler, we communicate with the hardware and th
 </div>
 </div>
 
-<div id="outline-container-orgheadline75" class="outline-3">
-<h3 id="orgheadline75">Keyboards on the Intel Architecture</h3>
-<div class="outline-text-3" id="text-orgheadline75">
+<div id="outline-container-orgheadline78" class="outline-3">
+<h3 id="orgheadline78">Keyboards on the Intel Architecture</h3>
+<div class="outline-text-3" id="text-orgheadline78">
 <p>
 The rest of this chapter is completely Intel specific. If you're not running on an Intel platform, it will not work. Don't even try to compile the code here. Move right along, nothing to see.
 </p>
@@ -4386,9 +4389,9 @@ used (the first seven bits of the scan code) and whether it has been pressed (if
 </p>
 </div>
 
-<div id="outline-container-orgheadline76" class="outline-4">
-<h4 id="orgheadline76">Example: intrpt.c</h4>
-<div class="outline-text-4" id="text-orgheadline76">
+<div id="outline-container-orgheadline79" class="outline-4">
+<h4 id="orgheadline79">Example: intrpt.c</h4>
+<div class="outline-text-4" id="text-orgheadline79">
 <div class="org-src-container">
 
 <pre class="src src-c"><span class="org-comment-delimiter">/*</span>
@@ -4511,35 +4514,35 @@ MODULE_LICENSE(<span class="org-string">"GPL"</span>);
 </div>
 </div>
 
-<div id="outline-container-orgheadline78" class="outline-2">
-<h2 id="orgheadline78">Common Pitfalls</h2>
-<div class="outline-text-2" id="text-orgheadline78">
+<div id="outline-container-orgheadline81" class="outline-2">
+<h2 id="orgheadline81">Common Pitfalls</h2>
+<div class="outline-text-2" id="text-orgheadline81">
 <p>
 Before I send you on your way to go out into the world and write kernel modules, there are a few things I need to warn you about. If I fail to warn you and something bad happens, please report the problem to me for a full refund of the amount I was paid for your copy of the book.
 </p>
 </div>
 
-<div id="outline-container-orgheadline79" class="outline-3">
-<h3 id="orgheadline79">Using standard libraries</h3>
-<div class="outline-text-3" id="text-orgheadline79">
+<div id="outline-container-orgheadline82" class="outline-3">
+<h3 id="orgheadline82">Using standard libraries</h3>
+<div class="outline-text-3" id="text-orgheadline82">
 <p>
 You can't do that. In a kernel module you can only use kernel functions, which are the functions you can see in /proc/kallsyms.
 </p>
 </div>
 </div>
 
-<div id="outline-container-orgheadline80" class="outline-3">
-<h3 id="orgheadline80">Disabling interrupts</h3>
-<div class="outline-text-3" id="text-orgheadline80">
+<div id="outline-container-orgheadline83" class="outline-3">
+<h3 id="orgheadline83">Disabling interrupts</h3>
+<div class="outline-text-3" id="text-orgheadline83">
 <p>
 You might need to do this for a short time and that is OK, but if you don't enable them afterwards, your system will be stuck and you'll have to power it off.
 </p>
 </div>
 </div>
 
-<div id="outline-container-orgheadline81" class="outline-3">
-<h3 id="orgheadline81">Sticking your head inside a large carnivore</h3>
-<div class="outline-text-3" id="text-orgheadline81">
+<div id="outline-container-orgheadline84" class="outline-3">
+<h3 id="orgheadline84">Sticking your head inside a large carnivore</h3>
+<div class="outline-text-3" id="text-orgheadline84">
 <p>
 I probably don't have to warn you about this, but I figured I will anyway, just in case.
 </p>
@@ -4547,18 +4550,18 @@ I probably don't have to warn you about this, but I figured I will anyway, just
 </div>
 </div>
 
-<div id="outline-container-orgheadline82" class="outline-2">
-<h2 id="orgheadline82">Appendix A. Changes: 2.4 To 2.6</h2>
-<div class="outline-text-2" id="text-orgheadline82">
+<div id="outline-container-orgheadline85" class="outline-2">
+<h2 id="orgheadline85">Appendix A. Changes: 2.4 To 2.6</h2>
+<div class="outline-text-2" id="text-orgheadline85">
 <p>
 I don't know the entire kernel well enough to document all of the changes. Some hints for porting can be found by comparing this version of the LKMPG with it's counterpart for kernel 2.4. Apart from that, anybody who needs to port drivers from 2.4 to 2.6 kernels might want to visit <a href="http://lwn.net/%20Articles/driver-porting">http://lwn.net/%20Articles/driver-porting</a>. If you still can't find an example that exactly meets your needs there, find a driver that's similar to your driver and present in both kernel versions. File comparison tools like xxdiff or meld can be a great help then. Also check if your driver is covered by docs in linux/Documentation/ . Before starting with porting and in case you're stuck it's a good idea to find an appropiate mailinglist and ask people there for pointers.
 </p>
 </div>
 </div>
 
-<div id="outline-container-orgheadline83" class="outline-2">
-<h2 id="orgheadline83">Appendix B. Where To Go From Here?</h2>
-<div class="outline-text-2" id="text-orgheadline83">
+<div id="outline-container-orgheadline86" class="outline-2">
+<h2 id="orgheadline86">Appendix B. Where To Go From Here?</h2>
+<div class="outline-text-2" id="text-orgheadline86">
 <p>
 I could easily have squeezed a few more chapters into this book. I could have added a chapter about creating new file systems, or about adding new protocol stacks (as if there's a need for that &#x2013; you'd have to dig underground to find a protocol stack not supported by Linux). I could have added explanations of the kernel mechanisms we haven't touched upon, such as bootstrapping or the disk interface.
 </p>
@@ -4581,9 +4584,9 @@ If you'd like to contribute to this guide, please contact one the maintainers fo
 </div>
 </div>
 
-<div id="outline-container-orgheadline84" class="outline-2">
-<h2 id="orgheadline84">Notes</h2>
-<div class="outline-text-2" id="text-orgheadline84">
+<div id="outline-container-orgheadline87" class="outline-2">
+<h2 id="orgheadline87">Notes</h2>
+<div class="outline-text-2" id="text-orgheadline87">
 <p>
 [1]  In earlier versions of linux, this was known as kerneld.
 [2]  If such a file exists. Note that the acual behavoir might be
@@ -4652,9 +4655,9 @@ If you'd like to contribute to this guide, please contact one the maintainers fo
 </p>
 </div>
 </div>
-<div id="outline-container-orgheadline85" class="outline-2">
-<h2 id="orgheadline85">Edits</h2>
-<div class="outline-text-2" id="text-orgheadline85">
+<div id="outline-container-orgheadline88" class="outline-2">
+<h2 id="orgheadline88">Edits</h2>
+<div class="outline-text-2" id="text-orgheadline88">
 <p>
 linux/fs.h updated file_operations structure (see <a href="http://lwn.net/Articles/119652/">http://lwn.net/Articles/119652/</a>)
 unregister_chrdev returns void
diff --git a/LKMPG-3.16.org b/LKMPG-3.16.org
index b683a10..91e8fec 100644
--- a/LKMPG-3.16.org
+++ b/LKMPG-3.16.org
@@ -3,8 +3,8 @@
 #+KEYWORDS: linux, kernel, kernel module, kernel programming
 #+DESCRIPTION: How to make kernel modules for Linux
 #+OPTIONS: ^:nil
-#+STYLE: <link rel="stylesheet" type="text/css" href="index.css" />
 
+* Introduction
 The Linux Kernel Module Programming Guide is a free book; you may reproduce and/or modify it under the terms of the Open Software License, version 1.1. You can obtain a copy of this license at [[http://opensource.org/licenses/osl.php][http://opensource.org/licenses/osl.php]].
 
 This book is distributed in the hope it will be useful, but without any warranty, without even the implied warranty of merchantability or fitness for a particular purpose.
@@ -15,23 +15,20 @@ Derivative works and translations of this document must be placed under the Open
 
 If you publish or distribute this book commercially, donations, royalties, and/or printed copies are greatly appreciated by the author and the [[http://www.tldp.org][Linux Documentation Project]] (LDP). Contributing in this way shows your support for free software and the LDP. If you have questions or comments, please contact the address above.
 
-*Foreword*
-
-*Authorship*
+** Authorship
 
 The Linux Kernel Module Programming Guide was originally written for the 2.2 kernels by Ori Pomerantz. Eventually, Ori no longer had time to maintain the document. After all, the Linux kernel is a fast moving target. Peter Jay Salzman took over maintenance and updated it for the 2.4 kernels. Eventually, Peter no longer had time to follow developments with the 2.6 kernel, so Michael Burian became a co-maintainer to update the document for the 2.6 kernels.  Bob Mottram updated the examples for 3.8 and 3.16 kernels and modified or updated some chapters.
 
-*Versioning and Notes*
+** Versioning and Notes
 
 The Linux kernel is a moving target. There has always been a question whether the LKMPG should remove deprecated information or keep it around for historical sake. Michael Burian and I decided to create a new branch of the LKMPG for each new stable kernel version. So version LKMPG 3.16.x will address Linux kernel 3.16 and LKMPG 2.6.x will address Linux kernel 2.6. No attempt will be made to archive historical information; a person wishing this information should read the appropriately versioned LKMPG.
 
 The source code and discussions should apply to most architectures, but I can't promise anything. One exception is Chapter 12, Interrupt Handlers, which should not work on any architecture except for x86.
 
-*Acknowledgements*
+** Acknowledgements
 
 The following people have contributed corrections or good suggestions: Ignacio Martin, David Porter, Daniele Paolo Scarpazza, Dimo Velev, Francois Audeon, Horst Schirmeier and Bob Mottram.
 
-* Introduction
 ** What Is A Kernel Module?
 
 So, you want to write a kernel module. You know C, you've written a few normal programs to run as processes, and now you want to get to where the real action is, to where a single wild pointer can wipe out your file system and a core dump means a reboot.
diff --git a/index.css b/index.css
deleted file mode 100644
index d9b00dd..0000000
--- a/index.css
+++ /dev/null
@@ -1,303 +0,0 @@
-@import url(http://fonts.googleapis.com/css?family=Inconsolata);
-@import url(http://fonts.googleapis.com/css?family=PT+Sans);
-@import url(http://fonts.googleapis.com/css?family=PT+Sans+Narrow:400,700);
-article,
-aside,
-details,
-figcaption,
-figure,
-footer,
-header,
-hgroup,
-nav,
-section,
-summary {
-  display: block;
-}
-audio,
-canvas,
-video {
-  display: inline-block;
-}
-audio:not([controls]) {
-  display: none;
-  height: 0;
-}
-[hidden] {
-  display: none;
-}
-html {
-  font-family: sans-serif;
-  -webkit-text-size-adjust: 100%;
-  -ms-text-size-adjust: 100%;
-}
-body {
-  margin: 0;
-}
-a:focus {
-  outline: thin dotted;
-}
-a:active,
-a:hover {
-  outline: 0;
-}
-h1 {
-  font-size: 2em;
-}
-abbr[title] {
-  border-bottom: 1px dotted;
-}
-b,
-strong {
-  font-weight: bold;
-}
-dfn {
-  font-style: italic;
-}
-mark {
-  background: #ff0;
-  color: #000;
-}
-code,
-kbd,
-pre,
-samp {
-  font-family: monospace, serif;
-  font-size: 1em;
-}
-pre {
-  white-space: pre-wrap;
-  word-wrap: break-word;
-}
-q {
-  quotes: "\201C" "\201D" "\2018" "\2019";
-}
-small {
-  font-size: 80%;
-}
-sub,
-sup {
-  font-size: 75%;
-  line-height: 0;
-  position: relative;
-  vertical-align: baseline;
-}
-sup {
-  top: -0.5em;
-}
-sub {
-  bottom: -0.25em;
-}
-img {
-  border: 0;
-}
-svg:not(:root) {
-  overflow: hidden;
-}
-figure {
-  margin: 0;
-}
-fieldset {
-  border: 1px solid #c0c0c0;
-  margin: 0 2px;
-  padding: 0.35em 0.625em 0.75em;
-}
-legend {
-  border: 0;
-  padding: 0;
-}
-button,
-input,
-select,
-textarea {
-  font-family: inherit;
-  font-size: 100%;
-  margin: 0;
-}
-button,
-input {
-  line-height: normal;
-}
-button,
-html input[type="button"],
-input[type="reset"],
-input[type="submit"] {
-  -webkit-appearance: button;
-  cursor: pointer;
-}
-button[disabled],
-input[disabled] {
-  cursor: default;
-}
-input[type="checkbox"],
-input[type="radio"] {
-  box-sizing: border-box;
-  padding: 0;
-}
-input[type="search"] {
-  -webkit-appearance: textfield;
-  -moz-box-sizing: content-box;
-  -webkit-box-sizing: content-box;
-  box-sizing: content-box;
-}
-input[type="search"]::-webkit-search-cancel-button,
-input[type="search"]::-webkit-search-decoration {
-  -webkit-appearance: none;
-}
-button::-moz-focus-inner,
-input::-moz-focus-inner {
-  border: 0;
-  padding: 0;
-}
-textarea {
-  overflow: auto;
-  vertical-align: top;
-}
-table {
-  border-collapse: collapse;
-  border-spacing: 0;
-}
-html {
-  font-family: 'PT Sans', sans-serif;
-}
-pre,
-code {
-  font-family: 'Inconsolata', sans-serif;
-}
-h1,
-h2,
-h3,
-h4,
-h5,
-h6 {
-  font-family: 'PT Sans Narrow', sans-serif;
-  font-weight: 700;
-}
-html {
-  background-color: #eee8d5;
-  color: #657b83;
-  margin: 1em;
-}
-body {
-  background-color: #fdf6e3;
-  margin: 0 auto;
-  max-width: 23cm;
-  border: 1pt solid #93a1a1;
-  padding: 1em;
-}
-code {
-  background-color: #eee8d5;
-  padding: 2px;
-}
-a {
-  color: #b58900;
-}
-a:visited {
-  color: #cb4b16;
-}
-a:hover {
-  color: #cb4b16;
-}
-h1 {
-  color: #d33682;
-}
-h2,
-h3,
-h4,
-h5,
-h6 {
-  color: #859900;
-}
-pre {
-  background-color: #fdf6e3;
-  color: #657b83;
-  border: 1pt solid #93a1a1;
-  padding: 1em;
-  box-shadow: 5pt 5pt 8pt #eee8d5;
-}
-pre code {
-  background-color: #fdf6e3;
-}
-h1 {
-  font-size: 2.8em;
-}
-h2 {
-  font-size: 2.4em;
-}
-h3 {
-  font-size: 1.8em;
-}
-h4 {
-  font-size: 1.4em;
-}
-h5 {
-  font-size: 1.3em;
-}
-h6 {
-  font-size: 1.15em;
-}
-.tag {
-  background-color: #eee8d5;
-  color: #d33682;
-  padding: 0 0.2em;
-}
-.todo,
-.next,
-.done {
-  color: #fdf6e3;
-  background-color: #dc322f;
-  padding: 0 0.2em;
-}
-.tag {
-  -webkit-border-radius: 0.35em;
-  -moz-border-radius: 0.35em;
-  border-radius: 0.35em;
-}
-.TODO {
-  -webkit-border-radius: 0.2em;
-  -moz-border-radius: 0.2em;
-  border-radius: 0.2em;
-  background-color: #2aa198;
-}
-.NEXT {
-  -webkit-border-radius: 0.2em;
-  -moz-border-radius: 0.2em;
-  border-radius: 0.2em;
-  background-color: #268bd2;
-}
-.ACTIVE {
-  -webkit-border-radius: 0.2em;
-  -moz-border-radius: 0.2em;
-  border-radius: 0.2em;
-  background-color: #268bd2;
-}
-.DONE {
-  -webkit-border-radius: 0.2em;
-  -moz-border-radius: 0.2em;
-  border-radius: 0.2em;
-  background-color: #859900;
-}
-.WAITING {
-  -webkit-border-radius: 0.2em;
-  -moz-border-radius: 0.2em;
-  border-radius: 0.2em;
-  background-color: #cb4b16;
-}
-.HOLD {
-  -webkit-border-radius: 0.2em;
-  -moz-border-radius: 0.2em;
-  border-radius: 0.2em;
-  background-color: #d33682;
-}
-.NOTE {
-  -webkit-border-radius: 0.2em;
-  -moz-border-radius: 0.2em;
-  border-radius: 0.2em;
-  background-color: #d33682;
-}
-.CANCELLED {
-  -webkit-border-radius: 0.2em;
-  -moz-border-radius: 0.2em;
-  border-radius: 0.2em;
-  background-color: #859900;
-}
