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