While i was talking with someone in #centos about drbd, we saw that there was no kmod-drbd82 (nor kmod-drbd) package for the latest and current 5.2 kernel. In fact the last one was for 2.6.18-92.1.10 ... I know that Johnny tested the weak-updates script but what if a new user already using the latest kernel try to install a new module (like for the drbd kmod) ? so it seems a build for every kernel has still to be done but unfortunately that depends on the people who initially build such kmod (for centosplus and extras and that are not in base). Is there a possibility to think about some kind of automated procedure so that each new built kernel (update) package for [updates] triggers a build of corresponding kmods sitting in extras/centosplus ? What do you think ?
On Tue, Nov 18, 2008 at 1:39 PM, Fabian Arrotin fabian.arrotin@arrfab.net wrote:
While i was talking with someone in #centos about drbd, we saw that there was no kmod-drbd82 (nor kmod-drbd) package for the latest and current 5.2 kernel. In fact the last one was for 2.6.18-92.1.10 ...
Actually, the latest version is kmod-drbd-8.0.13-2 (and kmod-drbd82-8.2.6-2). It uses weak-updates, so...
Akemi
Akemi Yagi wrote:
On Tue, Nov 18, 2008 at 1:39 PM, Fabian Arrotin fabian.arrotin@arrfab.net wrote:
While i was talking with someone in #centos about drbd, we saw that there was no kmod-drbd82 (nor kmod-drbd) package for the latest and current 5.2 kernel. In fact the last one was for 2.6.18-92.1.10 ...
Actually, the latest version is kmod-drbd-8.0.13-2 (and kmod-drbd82-8.2.6-2). It uses weak-updates, so...
So what ? ;-) Simple example : i'm a new sysadmin and i've recently installed a clean CentOS 5.2 on which i've directly made updates. So (at this time) i'm running with kernel-2.6.18-92.1.18. Two days after i'm interested in installing kmod-drbd82 and , surprise, there is not kmod-drbd82-`uname -r` available in the centos extras repo .. weak-updates is 'invoked' after each kernel update so that kmod installed (and correctly located in the 'extras' directory) will be linked for the newly installed kernel. But that will not solve the problem for people only wanting to start using a specific kmod with the latest kernel already installed .. or am i missing the point ?
On Tue, Nov 18, 2008 at 1:55 PM, Fabian Arrotin fabian.arrotin@arrfab.net wrote:
Akemi Yagi wrote:
On Tue, Nov 18, 2008 at 1:39 PM, Fabian Arrotin fabian.arrotin@arrfab.net wrote:
While i was talking with someone in #centos about drbd, we saw that there was no kmod-drbd82 (nor kmod-drbd) package for the latest and current 5.2 kernel. In fact the last one was for 2.6.18-92.1.10 ...
Actually, the latest version is kmod-drbd-8.0.13-2 (and kmod-drbd82-8.2.6-2). It uses weak-updates, so...
So what ? ;-) Simple example : i'm a new sysadmin and i've recently installed a clean CentOS 5.2 on which i've directly made updates. So (at this time) i'm running with kernel-2.6.18-92.1.18. Two days after i'm interested in installing kmod-drbd82 and , surprise, there is not kmod-drbd82-`uname -r` available in the centos extras repo .. weak-updates is 'invoked' after each kernel update so that kmod installed (and correctly located in the 'extras' directory) will be linked for the newly installed kernel. But that will not solve the problem for people only wanting to start using a specific kmod with the latest kernel already installed .. or am i missing the point ?
Weak-updates, when invoked, will look for *all* kABI compatible kernels on a given system and create a symlink for each one of them. (is my understanding)
Akemi
Akemi Yagi wrote:
On Tue, Nov 18, 2008 at 1:55 PM, Fabian Arrotin
<snip>
Simple example : i'm a new sysadmin and i've recently installed a clean CentOS 5.2 on which i've directly made updates. So (at this time) i'm running with kernel-2.6.18-92.1.18. Two days after i'm interested in installing kmod-drbd82 and , surprise, there is not kmod-drbd82-`uname -r` available in the centos extras repo .. weak-updates is 'invoked' after each kernel update so that kmod installed (and correctly located in the 'extras' directory) will be linked for the newly installed kernel. But that will not solve the problem for people only wanting to start using a specific kmod with the latest kernel already installed .. or am i missing the point ?
Weak-updates, when invoked, will look for *all* kABI compatible kernels on a given system and create a symlink for each one of them. (is my understanding)
Akemi
Yes, my bad .. i didn't notice that actual kmod-drbd82-8.2.6-2 already used the weak-modules scripts ... I think the wiki has to be updated now to say "yum install kmod-drbd82"and not "yum install kmod-drbd82-`uname -r`" On the other hand it's true that having old kmod (with specific kver in the name) in the same repository tends to confuse people : that's why i reacted on the first question because there was no 'actual' kmod in the repo .. so i guess that all older kmods not using /sbin/weak-updates can be removed from the repo Are all the provided kmod rpms already using the weak-modules scripts ?
On Tue, Nov 18, 2008 at 2:20 PM, Fabian Arrotin fabian.arrotin@arrfab.net wrote:
Akemi Yagi wrote:
On Tue, Nov 18, 2008 at 1:55 PM, Fabian Arrotin
<snip>
Ah, your post crossed mine :-D
Yes, my bad .. i didn't notice that actual kmod-drbd82-8.2.6-2 already used the weak-modules scripts ... I think the wiki has to be updated now to say "yum install kmod-drbd82"and not "yum install kmod-drbd82-`uname -r`"
It needs to be corrected, yes.
On the other hand it's true that having old kmod (with specific kver in the name) in the same repository tends to confuse people : that's why i reacted on the first question because there was no 'actual' kmod in the repo .. so i guess that all older kmods not using /sbin/weak-updates can be removed from the repo
I agree. Older files must go.
Are all the provided kmod rpms already using the weak-modules scripts ?
I believe Johnny has done them all but this has to be re-checked with him (or by testing them).
Akemi
Akemi Yagi wrote:
On Tue, Nov 18, 2008 at 2:20 PM, Fabian Arrotin fabian.arrotin@arrfab.net wrote:
Akemi Yagi wrote:
On Tue, Nov 18, 2008 at 1:55 PM, Fabian Arrotin
<snip>
Ah, your post crossed mine :-D
Yes, my bad .. i didn't notice that actual kmod-drbd82-8.2.6-2 already used the weak-modules scripts ... I think the wiki has to be updated now to say "yum install kmod-drbd82"and not "yum install kmod-drbd82-`uname -r`"
It needs to be corrected, yes.
On the other hand it's true that having old kmod (with specific kver in the name) in the same repository tends to confuse people : that's why i reacted on the first question because there was no 'actual' kmod in the repo .. so i guess that all older kmods not using /sbin/weak-updates can be removed from the repo
from where does this /sbin/weak-updates comes from?
I agree. Older files must go.
Are all the provided kmod rpms already using the weak-modules scripts ?
I believe Johnny has done them all but this has to be re-checked with him (or by testing them).
is there any docs about weak-updates and how to use in centos kmod?
On Tue, Nov 18, 2008 at 2:44 PM, Farkas Levente lfarkas@lfarkas.org wrote:
Akemi Yagi wrote:
<snip>
from where does this /sbin/weak-updates comes from?
is there any docs about weak-updates and how to use in centos kmod?
Actually, the best documentation may be the script itself:
/sbin/weak-modules
Akemi
On Tue, Nov 18, 2008 at 2:54 PM, Akemi Yagi amyagi@gmail.com wrote:
On Tue, Nov 18, 2008 at 2:44 PM, Farkas Levente lfarkas@lfarkas.org wrote:
Akemi Yagi wrote:
<snip>
from where does this /sbin/weak-updates comes from?
is there any docs about weak-updates and how to use in centos kmod?
Actually, the best documentation may be the script itself:
/sbin/weak-modules
Sorry, forgot one thing. You can see how it is called upon kernel install/update:
rpm -q --scripts kernel
Akemi
On Tue, Nov 18, 2008 at 2:07 PM, Akemi Yagi amyagi@gmail.com wrote:
On Tue, Nov 18, 2008 at 1:55 PM, Fabian Arrotin
So what ? ;-) Simple example : i'm a new sysadmin and i've recently installed a clean CentOS 5.2 on which i've directly made updates. So (at this time) i'm running with kernel-2.6.18-92.1.18. Two days after i'm interested in installing kmod-drbd82 and , surprise, there is not kmod-drbd82-`uname -r` available in the centos extras repo .. weak-updates is 'invoked' after each kernel update so that kmod installed (and correctly located in the 'extras' directory) will be linked for the newly installed kernel. But that will not solve the problem for people only wanting to start using a specific kmod with the latest kernel already installed .. or am i missing the point ?
Weak-updates, when invoked, will look for *all* kABI compatible kernels on a given system and create a symlink for each one of them. (is my understanding)
Akemi
Alright. I just did a small test run.
[yagi2@nova7 ~]$ rpm -q kmod-drbd package kmod-drbd is not installed [yagi2@nova7 ~]$ uname -a Linux nova7 2.6.18-92.1.13.el5 #1 SMP Wed Sep 24 19:32:05 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux [yagi2@nova7 ~]$ rpm -q kernel kernel-2.6.18-92.el5.x86_64 kernel-2.6.18-92.1.13.el5.x86_64
<So, the system does not have kmod-drbd and has kernel 2.6.18-92.1.13.>
[root@nova7 ~]# yum install kmod-drbd
Dependencies Resolved
============================================================================= Package Arch Version Repository Size ============================================================================= Installing: kmod-drbd x86_64 8.0.13-2 extras 794 k
Transaction Summary ============================================================================= Install 1 Package(s) Update 0 Package(s) Remove 0 Package(s)
Total download size: 794 k Is this ok [y/N]: y
<kmod-drbd has been installed on the system successfully>
[yagi2@nova7 ~]$ ls -l `find /lib/modules/ -name drbd.ko` -rw-r--r-- 1 root root 2874444 Oct 3 08:13 /lib/modules/2.6.18-92.1.13.el5/extra/drbd/drbd.ko lrwxrwxrwx 1 root root 50 Nov 18 14:47 /lib/modules/2.6.18-92.el5/weak-updates/drbd/drbd.ko -> /lib/modules/2.6.18-92.1.13.el5/extra/drbd/drbd.ko
<The above result is what I expected>
Akemi
-
Akemi Yagi -
Fabian Arrotin -
Farkas Levente