Rebuild src.rpm kernel driver for non-running kernel

[Jonathan Berry]

Hi all,

I have a few kernel drivers that I like to install that are not
included in the kernel itself but have rpms or src.rpms available from
Livna (ntfs, nvidia, etc) .  These of course have to be rebuilt or
reinstalled for a new kernel.  Sometimes I update my kernel before
Livna gets the rpms rebuilt, so it can be easier to just rebuild the
src.rpm.  However, it would be really convenient to be able to rebuild
the src.rpms before rebooting to the new kernel, so everything just
works.

So, now to my question: is it possible to rebuild a kernel driver
src.rpm for a non-running kernel?  Is there a standard way to do it?

I tried doing this with the nvidia driver for FC5T3 once with very
poor results.  I had to go hack into the spec file to change the way
it got the kernel version (it used some self-contained script to get
the kernel version (or versions)).  Not at all an ideal way to do it. 
It would be really nice to just pass in a KVER=2.6.16-1.2069_FC4 or
something with the rpmbuild --rebuild command.

Jonathan

[Thorsten Leemhuis]

Am Donnerstag, den 30.03.2006, 23:25 -0600 schrieb Jonathan Berry:

>  I tried doing this with the nvidia driver for FC5T3 once with very
>  poor results.  I had to go hack into the spec file to change the way
>  it got the kernel version (it used some self-contained script to get
>  the kernel version (or versions)).  Not at all an ideal way to do it. 
>  It would be really nice to just pass in a KVER=2.6.16-1.2069_FC4 or
>  something with the rpmbuild --rebuild command. 
rpmbuild --rebuild kmod-foo --define "kversion 2.6.16-1.2080_FC5" --define
"kvariants """

For example would rebuild for the UP kernel of 2.6.16-1.2080_FC5 even if
you are currently running 2.6.16-1.2054_FC5. This only works correctly
with the latest kmod-SRPMS from livna. 

rpmbuild --rebuild kmod-foo --define "kversion 2.6.16-1.2080_FC5" --define
"kvariants smp"

Would build for 2.6.16-1.2080_FC5smp

Sorry, this in not documented anywhere yet. We are simply to less folks
in livna atm and still have a lot to do to make everything work
perfectly. We really could need more help from the community.

CU
thl

[Jonathan Berry]

On 3/31/06, Thorsten Leemhuis <fedora(a)leemhuis.info&gt; wrote:
>  Am Donnerstag, den 30.03.2006, 23:25 -0600 schrieb Jonathan Berry:
>
>  > I tried doing this with the nvidia driver for FC5T3 once with very
>  > poor results.  I had to go hack into the spec file to change the way
>  > it got the kernel version (it used some self-contained script to get
>  > the kernel version (or versions)).  Not at all an ideal way to do it.
>  > It would be really nice to just pass in a KVER=2.6.16-1.2069_FC4 or
>  > something with the rpmbuild --rebuild command.
>
>  rpmbuild --rebuild kmod-foo --define "kversion 2.6.16-1.2080_FC5" --define
> "kvariants """
>
>  For example would rebuild for the UP kernel of 2.6.16-1.2080_FC5 even if
>  you are currently running 2.6.16-1.2054_FC5. This only works correctly
>  with the latest kmod-SRPMS from livna.
>
>  rpmbuild --rebuild kmod-foo --define "kversion 2.6.16-1.2080_FC5" --define
> "kvariants smp"
>
>  Would build for 2.6.16-1.2080_FC5smp 
That's some great info, Thorsten, thanks!  Do you know how this
behaves on x86_64 where there is only an "smp" kernel?  I think only
uname reports the kernel as smp, everything else (rpm, kernel images,
modules dirs, etc.) does not have smp since there is no UP.
I guess this will not work for FC4 srpms just yet.  Are there plans to
implement this feature for FC4 srpms?

>  Sorry, this in not documented anywhere yet. We are simply to less
> folks
>  in livna atm and still have a lot to do to make everything work
>  perfectly. We really could need more help from the community. 
I'd volunteer to help if I had the time.  Maybe I'll have a little
more time here in a couple of months.  Although, I do live in the USA.
 Not sure if that would be an issue or not.

Jonathan

[Thorsten Leemhuis]

Am Freitag, den 31.03.2006, 20:14 -0600 schrieb Jonathan Berry:
>  On 3/31/06, Thorsten Leemhuis <fedora(a)leemhuis.info&gt; wrote:
>  > Am Donnerstag, den 30.03.2006, 23:25 -0600 schrieb Jonathan Berry:
>  >
>  > > I tried doing this with the nvidia driver for FC5T3 once with very
>  > > poor results.  I had to go hack into the spec file to change the way
>  > > it got the kernel version (it used some self-contained script to get
>  > > the kernel version (or versions)).  Not at all an ideal way to do it.
>  > > It would be really nice to just pass in a KVER=2.6.16-1.2069_FC4 or
>  > > something with the rpmbuild --rebuild command.
>  >
>  > rpmbuild --rebuild kmod-foo --define "kversion 2.6.16-1.2080_FC5" --define
> "kvariants """
>  >
>  > For example would rebuild for the UP kernel of 2.6.16-1.2080_FC5 even if
>  > you are currently running 2.6.16-1.2054_FC5. This only works correctly
>  > with the latest kmod-SRPMS from livna.
>  >
>  > rpmbuild --rebuild kmod-foo --define "kversion 2.6.16-1.2080_FC5" --define
> "kvariants smp"
>  >
>  > Would build for 2.6.16-1.2080_FC5smp
>  
>  That's some great info, Thorsten, thanks!  Do you know how this
>  behaves on x86_64 where there is only an "smp" kernel?  I think only
>  uname reports the kernel as smp [...] 
Nope. The x86_64 FC5 kernel in regards of packaging behaves just like
the UP i686 kernel. E.g. everything works if you just use

rpmbuild --rebuild kmod-foo --define "kversion 2.6.16-1.2080_FC5" --define
"kvariants """

>   Are there plans to
>  implement this feature for FC4 srpms? 
Nope, this would only confuse users.

CU
thl
-- 
Thorsten Leemhuis <fedora(a)leemhuis.info&gt;