Re: some question about the patches

Andrew C. Esh (
Thu, 5 Sep 1996 16:55:56 -0500

>>>>> "Squiz" == Squiz <> writes:

Squiz> On Wed, 4 Sep 1996, Stergiou Dimitris wrote:

>> hi fellows linuxers, i have the following question. lets say i
>> download the kernel 2.0.4 in its "full" source (talkin about
>> 5.9 MB). lets say i install the

Squiz> Then it would be a bit silly, since you can download the
Squiz> full source to 2.0.17....

>> kernel. now the question. if i decide to go to kernel 2.0.10
>> lets say but not downloading it completely but going through
>> patches what is the correct way to do it?

Squiz> You'd download all the patches between 2.0.5 to 2.0.10 and
Squiz> then something like this...

Squiz> cd /usr/src patch <patch-2.0.5 patch <patch-2.0.6 [..etc..]
Squiz> patch <patch-2.0.10 cd linux make dep; make clean; make
Squiz> zlilo; make modules; make modules_install

A better way to patch the kernel is this:

# /usr/src/linux - Linux Kernel source Directory
chmod u+x /usr/src/linux/scripts/patch-kernel # (if you haven't done this yet)
/usr/src/linux/scripts/patch-kernel /usr/src/linux /patch_file_directory

This will check your current kernel version, and apply all of the
available patches in order until it reaches the end of the sequence,
or detects an error. If an error is detected, the .orig and .rej files
for the source are left in place so you can determine the problem and
hopefully fix it. I've never had to do this, except when I've tried to
apply patches to source code which has been hand modified (read: my fault).

Suggestion: Should we "ship" scripts/patch-kernel already chmod-ed u+x?

Andrew C. Esh
Computer Network Technology (finger for PGP key)
6500 Wedgwood Road		612.550.8000 (main)
Maple Grove MN 55311		612.550.8229 (direct) - CNT Inc. Home Page - ACE Home Page