CentOS - Nov 2008 - kmod-xfs and weak-updates

I installed kmod-xfs-0.4-2 back with kernel-2.6.18-92.1.13. I have  
updated kernels but there have been no new kmod-xfs. It still works  
because of weak-updates (I guess). Currently:

# find /lib/modules -name xfs.ko
/lib/modules/2.6.18-92.1.13.el5/extra/xfs/xfs.ko
/lib/modules/2.6.18-92.1.13.el5/weak-updates/xfs/xfs.ko
/lib/modules/2.6.18-92.1.17.el5/weak-updates/xfs/xfs.ko
/lib/modules/2.6.18-92.1.18.el5/weak-updates/xfs/xfs.ko


My question is: kernel 2.6.18-92.1.13 is now the oldest one present  
on my system and will be removed next update. Do I need to worry  
about that? Will it take the remaining kmod-xfs with it?

Tony Schreiner

Tony Schreiner wrote:
> I installed kmod-xfs-0.4-2 back with kernel-2.6.18-92.1.13. I have 
> updated kernels but there have been no new kmod-xfs. It still works 
> because of weak-updates (I guess). Currently:
> 
> # find /lib/modules -name xfs.ko
> /lib/modules/2.6.18-92.1.13.el5/extra/xfs/xfs.ko
> /lib/modules/2.6.18-92.1.13.el5/weak-updates/xfs/xfs.ko
> /lib/modules/2.6.18-92.1.17.el5/weak-updates/xfs/xfs.ko
> /lib/modules/2.6.18-92.1.18.el5/weak-updates/xfs/xfs.ko
> 
> 
> My question is: kernel 2.6.18-92.1.13 is now the oldest one present on 
> my system and will be removed next update. Do I need to worry about 
> that? Will it take the remaining kmod-xfs with it?
> 
No, you don't need to worry. Anything installed in 
/lib/modules/2.6.18-92.1.13.el5/extra/ will be left on the system when 
that kernel is uninstalled so the links in weak-updates will still be 
functional.

Tony Schreiner wrote:
> My question is: kernel 2.6.18-92.1.13 is now the oldest one present on 
> my system and will be removed next update. Do I need to worry about 
> that? Will it take the remaining kmod-xfs with it?
Only files directly owned by the kernel will get removed when the kernel 
rpm is removed from your machine; which, as a policy holds true for any 
rpm. This is one of the many reasons why packagers are encouraged to 
list-and-own specific components and not complete directory tree's when 
they setup the spec files.

-- 
Karanbir Singh : http://www.karan.org/  : 2522219 at icq