<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Am 01.07.2009 18:44, schrieb Bill McGonigle:<br>
<span style="white-space: pre;">> Because Fedora has several
kernel update in the<br>
>> lifetime, you have to create a ksplice kernelpatch for each<br>
>> kernel release which is available on Fedora.<br>
> <br>
> Since you quoted my post with criteria to avoid this, I have to<br>
> assume I'm missing your point here. Could you clarify?<br>
> </span><br>
Ok, lets assume, that we have a security kernel patch for Fedora-10.<br>
<br>
On Fedora we have kernels from the 2.6.27 and from the 2.6.28 series.<br>
This means, that you have to create seperates kernel patch modules for<br>
each kernel release which was submitted for Fedora-10.<br>
<br>
The reseason to do it, is that ksplice is not able to handled patches,<br>
which may change global data structures.<br>
<br>
Best Regards:<br>
<br>
Jochen Schmitt<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.9 (GNU/Linux)<br>
Comment: Using GnuPG with Fedora - <a class="moz-txt-link-freetext" href="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</a><br>
<br>
iEYEARECAAYFAkpLoVkACgkQT2AHK6txfgzmFACgrhko8Pnppq48txUYl3HS6/QE<br>
J+8AoNhj2aSfI5jW4UGTuQQb6x+TD9Tm<br>
=0KZA<br>
-----END PGP SIGNATURE-----<br>
<br>
</body>
</html>