| 1 |
On 15.02.2017 19:10, Bertram Scharpf wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I did not find this by Google. Maybe I asked the wrong |
| 5 |
> terms. |
| 6 |
> |
| 7 |
> The package "virtualbox-modules" contains some kernel |
| 8 |
> modules. When I built the package they landed in the |
| 9 |
> directory |
| 10 |
> |
| 11 |
> # equery f app-emulation/virtualbox-modules |
| 12 |
> ... |
| 13 |
> /lib/modules/4.4.39-gentoo/misc/vboxdrv.ko |
| 14 |
> /lib/modules/4.4.39-gentoo/misc/vboxnetadp.ko |
| 15 |
> ... |
| 16 |
> |
| 17 |
> After a kernel update the VirtualBox won't find them any |
| 18 |
> more and do not expect that at all. |
| 19 |
> |
| 20 |
> I could delete the package and build-install it again, but |
| 21 |
> then the old kernels modules would disappear. I just want |
| 22 |
> to install the new ones. |
| 23 |
> |
| 24 |
> I could do a sequence of "ebuild" commands. Is there a |
| 25 |
> front end "emerge" command, too? Something like the -U flag? |
| 26 |
> |
| 27 |
> Thanks in advance. |
| 28 |
> |
| 29 |
> Bertram |
| 30 |
> |
| 31 |
> |
| 32 |
|
| 33 |
emerge @module-rebuild |
| 34 |
|
| 35 |
(find out via 'emerge --list-sets') |
Archives