newbie questions

[Fajar A. Nugraha]

Matt Domsch wrote:
>> - Managing SAN qla module installation
>>     
>
> I believe these are posted on EMC's support web site.  qla was one of
> the very first modules delivered using DKMS. :-)
>
>   
What? There's a dkms rpm for qla2xxx? You mean all the time I spent
creating my own dkms rpm was reinventing the wheel? :-[

Seriously though, qlogic driver on their driver download page (not OEM)
doesn't mention the DKMS package (for qla2xxx at least). It only builds
a module for current running kernel. Upgrading the kernel means
re-running the install script, telling it to remove and reinstall the
driver.

I wonder how EMC's dkms rpm handle kernel upgrades. Problems that I
encountered on early versions of my rpm was :
- dkms modules are automatically rebuilt on the next reboot. This will
be a problem if the driver is for scsi storage (or HBA), and "/"
partition is on that storage, because it won't be available during first
boot of that kernel.
- forcing a call to /etc/init.d/dkms_autoinstaller during kernel upgrade
(using %post, or in my case by hijacking /sbin/weak-modules) might not
work, due to the fact that kernel-devel for that kernel version might
not be installed yet.
- upgrading dkms driver rpms might lead to messy (and sometimes not
working) /etc/modprobe.conf, due to adding and removing entry from
modprobe.conf.

I ended up creating a cleanup script that would :
- do automated yum update
- cleanup modprobe.conf, if necessary
- build dkms modules for all available kernel afterwards

I wonder if there's an easier way.

Regards,

Fajar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3229 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.us.dell.com/pipermail/dkms-devel/attachments/20071206/7f13a0c4/attachment.bin