[elrepo] RFP: mISDN and Dahdi ...

[Clinton Lee Taylor]

Greetings ...

>>>> I see there is a new kernel out for CentOS, so I would really like try
>>>> and see if there are any problems or if I might be able to provide
>>>> back some more positive feedback ...
>>>
>>> That is always appreciated for the first kernel update following the
>>> release of a kmod-package.
>>  Okay, is there anything I can test or just a reboot into the new
>> kernel with the kmod in place?
>
> If the new kernel is already installed but has not yet been booted,
> the output returned by something like the following should give you
> the confidence to perform a reboot --
>
> [code]
> ls -l $(find /lib/modules -name \*.ko | grep -E 'extra|weak')
> [/code]
 Lots of files are listed with this command ...

 Currently remove all old kernels not used any more ...

> Essentially you will be looking for the symlink(s) from the
> weak-updates/ directory of kernel-2.6.18-164.10.1.el5 back to the
> module(s) in the extra/ directory of kernel-2.6.18-164.el5 . . .
 Okay, if I go into the weak-updates of the new kernel, I see symlinks
to these files and they look go ...

> If you see that, everything should be o.k. for the reboot.
 Cool, I will try this when I'm in front of said servers, because I
have had server not reboot nicely when done remotely after and upgrade
of sorts ... Like a really good rule of thumb ...

 This all bring two more questions, which might be a little off topic,
but should I keep older kernels around?  I normally only keep the
original installed kernel and the last two installed kernels, but
looking through some of the weak-updates, I see refferance to older
kernels that have been removed ... Good or bad thing?

 Second ... I was wonder, and this is loud, if there is a way to test
a new kernel, temporarily? Like change grub for only next boot, and
switch bad if there is a problem, without having to be in front of the
system?

Thanks
Mailed
LeeT