1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
|
Starting with kdb v2.0 there is a common patch against each kernel which
contains all the architecture independent code plus separate architecture
dependent patches. Apply the common patch for your kernel plus at least
one architecture dependent patch, the architecture patches activate kdb.
The naming convention for kdb patches is :-
vx.y The version of kdb. x.y is updated as new features are added to kdb.
-v.p.s The kernel version that the patch applies to. 's' may include -pre,
-rc or whatever numbering system the kernel keepers have thought up this
week.
-common The common kdb code. Everybody needs this.
-ia64 Architecture dependent code for ia64, etc.
-x86 Architecture dependent code for x86 (32 bits and 64 bits)
(The x86 architecture replaces i386 and x86_64 since 2.6.24-rc1.)
-n If there are multiple kdb patches against the same kernel version then
the last number is incremented.
To build kdb for your kernel, apply the common kdb patch which is less
than or equal to the kernel v.p.s, taking the highest value of '-n'
if there is more than one. Apply the relevant arch dependent patch
with the same value of 'vx.y-v.p.s-', taking the highest value of '-n'
if there is more than one.
For example, to use kdb for i386 on kernel 2.6.6, apply
kdb-v4.4-2.6.6-common-<n> (use highest value of <n>)
kdb-v4.4-2.6.6-i386-<n> (use highest value of <n>)
in that order. To use kdb for ia64 with patch 040521 on kernel 2.6.6, apply
kdb-v4.4-2.6.6-common-<n> (use highest value of <n>)
kdb-v4.4-2.6.6-ia64-040521-<n> (use highest value of <n>)
in that order.
Use patch -p1 for all patches.
|
