[S.u.S.E. Linux] Kernel-patching
Hi! Is ist true, that when updating a suse-kernel, you need the original kernel, clean, than patch this to the new version, and then apply only one suse-patch to the latest original kernel? thanks arnulf -- know my poetry? - c...k -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Seems to be what someone posted, recently when the last stable patch came out. I did this....and it worked o.k. On Sat, 20 Jun 1998, tulf wrote:
Hi!
Is ist true, that when updating a suse-kernel, you need the original kernel, clean, than patch this to the new version, and then apply only one suse-patch to the latest original kernel?
thanks arnulf -- know my poetry? - c...k -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Seems to be what someone posted, recently when the last stable patch came out. I did this....and it worked o.k.
Is ist true, that when updating a suse-kernel, you need the original kernel, clean, than patch this to the new version, and then apply only one suse-patch to the latest original kernel?
I believe that SuSE Kernal source is differant that the original kernal source. SuSE's Kernal source have various patches alreadly applied to them and patching SuSE Kernal source with regular kernal patches sometimes results in a error. I've found the best thing to do is to either wait til SuSE comes out with a patch for their source code(s), or download their entire source code and compile for scratch. Jonathan -- =========== =========== Jonathan Paul Cowherd jpcowh01@slug.louisville.edu <A HREF="http://www.slug.louisville.edu/~jpcowh01"><A HREF="http://www.slug.louisville.edu/~jpcowh01</A">http://www.slug.louisville.edu/~jpcowh01 This is my world and I am... World Leader Pretend =========== =========== -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Sat, 20 Jun 1998, tulf wrote:
Is ist true, that when updating a suse-kernel, you need the original kernel, clean, than patch this to the new version, and then apply only one suse-patch to the latest original kernel?
Seems there are some irritations regarding the "S.u.S.E. Kernel" ;-) First of all: There's nothing magic about the S.u.S.E. kernel. The release cycles of the "official" kernel are so long that we keep our own version of the kernel. But this version essentially is the official kernel plus bugfixes plus new drivers plus updated drivers. So, as soon as 2.0.34 is released, simply forget about 2.0.33-suse. Just consider the S.u.S.E. kernel an interims release. As many of the patches in patch-2.0.34 have already been contained in 2.0.33-suse, you cannot apply the official patch from Linus against a S.u.S.E. kernel. The correct way is to uninstall the patched kernel and install the official one. After that you can apply the official patch from Linus. The current 2.0.34-suse only has updates for the aic7xxx driver and for the NCR53c8xx driver. I forgot to include the drivers for parallel port CD-ROM drives which are still not in the official kernel.
thanks arnulf
Hubert -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi,
On Sat, 20 Jun 1998, tulf wrote:
Is ist true, that when updating a suse-kernel, you need the original kernel, clean, than patch this to the new version, and then apply only one suse-patch to the latest original kernel?
Seems there are some irritations regarding the "S.u.S.E. Kernel" ;-)
First of all: There's nothing magic about the S.u.S.E. kernel. The release cycles of the "official" kernel are so long that we keep our own version of the kernel. But this version essentially is the official kernel plus bugfixes plus new drivers plus updated drivers. So, as soon as 2.0.34 is released, simply forget about 2.0.33-suse. Just consider the S.u.S.E. kernel an interims release. As many of the patches in patch-2.0.34 have already been contained in 2.0.33-suse, you cannot apply the official patch from Linus against a S.u.S.E. kernel. The correct way is to uninstall the patched kernel and install the official one. After that you can apply the official patch from Linus.
The current 2.0.34-suse only has updates for the aic7xxx driver and for the NCR53c8xx driver. I forgot to include the drivers for parallel port CD-ROM drives which are still not in the official kernel.
thanks arnulf
Hubert
Thanks Hubert! This cleared it up for me. But then I really suggest, to put all suse-patches on your server for the reason of being able to upadte over more than one release and to keep your traffic down on your server. (kernel = 7 MB!) (It seems to be quite busy except for Sunday mornings Eurpean Time zones.) That would help a lot. This info should also be as precise as this in your sdb.rpm . arnulf -- know my poetry? - c...k -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Tue, 23 Jun 1998, Arnulf Striepecke wrote:
Thanks Hubert!
This cleared it up for me.
But then I really suggest, to put all suse-patches on your server for the reason of being able to upadte over more than one release and to keep your traffic down on your server. (kernel = 7 MB!)
Have a look at /unsorted/patches/kernel-patches.tgz on CD#1. It contains all the patches we used for our kernel. Plus several additional ones. So, if you need the parallel port CD-ROM drivers in 2.0.34, simply do cd /usr/src/linux-2.0.34-orig (or whatever you named it) patch -p1 -s < /<wherever>/ppcd-2.0.31
participants (5)
-
arnulf＠neokom.geo.uni-bonn.de -
hekate＠intergate.bc.ca -
jpcowh01＠ox.slug.louisville.edu -
mantel＠suse.de -
striepe＠neokom.geo.uni-bonn.de