Differences

This shows you the differences between two versions of the page.

--- patching [2009/03/15 14:40] – fixed typos. darkaudax
+++ patching [2018/10/05 22:57] (current) – Updated links mister_x
@@ Line 25: / Line 25: @@
   * Where do I get the patch?
-The [[http://aircrack-ng.org/doku.php|aircrack-ng wiki]] typically indicates which patches are required for particular drivers.  And the appropriate pages contain detailed installation and patching instructions.  See the [[drivers|drivers page]] for links to the various detailed pages.
+The [[main|aircrack-ng wiki]] typically indicates which patches are required for particular drivers.  And the appropriate pages contain detailed installation and patching instructions.  See the [[install_drivers|drivers installation page]] for links to the various detailed pages.
+You can obtain the patch in a variety of ways.  The wiki page normally provides a download link.  As well, patches are included in the aircrack-ng source package in the "patches" directory.  Many times patches are under development and you can find links to them on the [[https://forum.aircrack-ng.org|Forum]].
-You can obtain the patch in a variety of ways.  The wiki page normally provides a download link.  As well, patches are included in the aircrack-ng source package in the "patches" directory.  Many times patches are under development and you can find links to them on the [[http://forum.tinyshell.be|Forum]].
@@ Line 40: / Line 41: @@
    wget "URL to patch"
-   wget http://patches.aircrack-ng.org/rtl8187_2.6.24v3.patch
+   wget https://patches.aircrack-ng.org/rtl8187_2.6.24v3.patch
 Then you need to move the patch to the appropriate directory using the "mv" command.  The question arises as to which is the "appropriate directory"?  There is no correct answer to the question.  It depends on what you are patching and how the patch was created.   Looking at the directories referenced in the patch itself usually gives you a good indication of where it should go.  You might need to try a few locations.  Here are some typical locations:
@@ Line 60: / Line 61: @@
 If you want to test applying the patch:
-   patch -Np0 --dryrun --verbose -i <name of the patch file>
+   patch -Np0 --dry-run --verbose -i <name of the patch file>
-NOTE: There is double dash in front of "dryrun" and "verbose".
+NOTE: There is double dash in front of "dry-run" and "verbose".
 It is always a good idea to perform a test prior to applying it for real.  This way you can avoid problems.
@@ Line 104: / Line 105: @@
   * Play with the "-pX" value.  This allows you to strip directories off of the referenced files in the patch.  Try -p0, -p1, -p2, etc.
   * The version of the patch may be wrong for your kernel version.  Check to ensure that the patch you are using is known to work properly against the kernel you are running.
@@ Line 125: / Line 127: @@
   * In some rare cases, a few failures may still be ignored.   You can try compiling the program and see if it works.  Not a high probability but worth a try.
   * The version of the patch may be wrong for your kernel version.  Check to ensure that the patch you are using is known to work properly against the kernel you are running.  Most likely, you need an older or new version of the patch.
+  * If all hunks fail: The patch may be whitespace-damaged. Try adding the -l option to the patch command line.
+  * Try applying the patch with the "fuzz" option: add "-F3" to the patch command line. (The number specifies the maximal fuzz allowed - 3 is a value that works well.)
   * If all else fails, you can try manually updating the source code by reviewing the patch and applying the changes by hand.