Subject: | |
From: | |
Reply To: | |
Date: | Thu, 27 May 2004 09:31:23 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Jarek,
It can work pretty much like magic as long as the
module is compatible with the new kernel and the
source is installed. On a reboot, it can be instructed
to build the module. I'm not sure how critical
things (like a FibreChannel driver that hosts the
root partition) work.
You could probably use dkms to build the module for
the rpm build, but I don't think it would be that
helpful. I think having a good spec file would
be more valuable.
I think the proposed method should be more reliable,
it just requires building a slew of module rpms for
each kernel upgrade.
--Shane
> [log in to unmask] wrote:
>
> Yes, indeed: I've seen this one too.
>
> Looks quite interesting: there was even some discussion
> about it among people packaging kernel modules.
>
> Definitely the strong point is the automation of
> module rebuilding process: but it does not give the automation
> of updates magic (I think ...)
>
> Could dkms be used to build kernel-module-<foo>-<kversion>
> packages by any chance ?
>
> Jarek
> __
> -------------------------------------------------------
> _ Jaroslaw_Polok ___________________ CERN - IT/ADC/LE _
> _ http://home.cern.ch/~jpolok ___ tel_+41_22_767_1834 _
> _____________________________________ +41_78_792_0795 _
>
>
------------------------------------------------------------------------
Shane Canon voice: 510-486-6981
PSDF Project Lead fax: 510-486-7520
National Energy Research Scientific
Computing Center
1 Cyclotron Road Mailstop 943-256
Berkeley, CA 94720 [log in to unmask]
------------------------------------------------------------------------
|
|
|