Hi Robert, On Thursday 02 February 2006 20:09, Robert Schiele wrote:
On Thu, Feb 02, 2006 at 04:58:21PM +0200, Silviu Marin-Caea wrote:
On Thursday 02 February 2006 15:39, Marcus Meissner wrote:
http://www.suse.de/~agruen/KMPM/
(CODE 9 refers to SLES 9 , CODE 10 to 10.1 / SLES 10).
While a third party kernel module with reiser4 can work, it's not quite the same as if it were in the SUSE kernel.
Whenever SUSE will update the kernel (YOU), there's a chance that the third party module will no longer work and the reiser4 filesystem will not be mountable.
Please read the mentioned paper before pointing to problems that are handled in the paper.
The important mechanisms to ensure, that esp. reiser4 (fs module) will survive a kernel update, are -- according to the paper for CODE10 -- still not finished. Sure, "The dependencies between those packages will ensure that the installed kernel packages math the installed kernel module packages." tells me, that (and please correct me, if I am wrong!) kernel modules, which depend to an kernel package version prior the updated one will be deleted. Will then a system running on reiser4 restart with the new kernel? To my understanding there should be a mechanism to recompile the kernel module package automatically during YOU (or the respective update mechanism).
Robert
Stefan -- Stefan Schmidt Network Manager International University Bremen From RFC 1925: "Good, Fast, Cheap: Pick any two (you can't have all three)."