dkms removes kernel module when installing/upgrading
Fajar A. Nugraha
fajar at fajar.net
Thu Jun 7 00:04:14 CDT 2007
Matt Domsch wrote:
> On Wed, Jun 06, 2007 at 10:20:51PM +0100, Z? wrote:
>
>>> The right solution is to edit the driver RPM %post script to check the
>>> return code of 'dkms install' command. If $? == 101, this means the
>>> install did not succeed because it didn't need to, and --force should
>>> be used; or, don't uninstall.
>>>
>> Im really not understanding very well, but shouldnt be needed to use --force,
>> dkms should check on the kernel module and if already exists, should
>> uninstall the previous dkms package and dont remove the vboxdrv drive from
>> kernel tree since this is an upgrade and not an uninstall.
>>
>
> OK, this might be considered a fault of DKMS; it should notice the
> --rpm_safe_upgrade flag to the 'dkms install' command and
> automatically do what --force does; let the new version install
> anyway. I'll think about this some more.
>
>
Incidently, if rpm -Uvh actually makes dkms install the driver with
--force, will the removal of the old one still remove it (being the same
version and all), or would it actually detect that "this is not what I
placed, even if it is the same version, so I should leave it alone"?
Regards,
Fajar
More information about the DKMS-devel
mailing list