Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

yum : manually adding depencies

Can I (manually) create a 'yum' dependency between a kernel package and a kmod package?

Currently I have to manually install the latest kmod version and this for each kernel update. But if the latest version of the kmod is delayed, it can lead to a little curse. Because I have to reboot to my older kernel, and wait until the kmod is generated before I can use the newest kernel.

FYI: it concerns 'kmod-VirtualBox'.

I know I can use 'akmod', but at rpmfusion the latest version of VirtualBox.x86_64 is '4.3.6-4.fc19' and for akmod-VirtualBox.x86_64 it is '4.3.6-2.fc19' ! And I suspect that this was the reason why I could not get it to work.

yum : manually adding depenciesdependencies

Can I (manually) create a 'yum' dependency between a kernel package and a kmod package?

Currently I have to manually install the latest kmod version and this for each kernel update. But if the latest version of the kmod is delayed, it can lead to a little curse. Because I have to reboot to my older kernel, and wait until the kmod is generated before I can use the newest kernel.

FYI: it concerns 'kmod-VirtualBox'.

I know I can use 'akmod', but at rpmfusion the latest version of VirtualBox.x86_64 is '4.3.6-4.fc19' and for akmod-VirtualBox.x86_64 it is '4.3.6-2.fc19' ! And I suspect that this was the reason why I could not get it to work.

click to hide/show revision 3
retagged

yum : manually adding dependencies

Can I (manually) create a 'yum' dependency between a kernel package and a kmod package?

Currently I have to manually install the latest kmod version and this for each kernel update. But if the latest version of the kmod is delayed, it can lead to a little curse. Because I have to reboot to my older kernel, and wait until the kmod is generated before I can use the newest kernel.

FYI: it concerns 'kmod-VirtualBox'.

I know I can use 'akmod', but at rpmfusion the latest version of VirtualBox.x86_64 is '4.3.6-4.fc19' and for akmod-VirtualBox.x86_64 it is '4.3.6-2.fc19' ! And I suspect that this was the reason why I could not get it to work.