| 1 |
Am Thu, 16 Feb 2017 02:36:42 +0100 |
| 2 |
schrieb Bertram Scharpf <lists@×××××××××××××××.de>: |
| 3 |
|
| 4 |
> On Wednesday, 15. Feb 2017, 19:27:26 +0100, Johannes Rosenberger |
| 5 |
> wrote: |
| 6 |
> > On 15.02.2017 19:10, Bertram Scharpf wrote: |
| 7 |
> > > I did not find this by Google. Maybe I asked the wrong |
| 8 |
> > > terms. |
| 9 |
> > > |
| 10 |
> > > The package "virtualbox-modules" contains some kernel |
| 11 |
> > > modules. When I built the package they landed in the |
| 12 |
> > > directory |
| 13 |
> > > |
| 14 |
> > > # equery f |
| 15 |
> > > app-emulation/virtualbox-modules ... |
| 16 |
> > > /lib/modules/4.4.39-gentoo/misc/vboxdrv.ko |
| 17 |
> > > /lib/modules/4.4.39-gentoo/misc/vboxnetadp.ko |
| 18 |
> > > ... |
| 19 |
> > > |
| 20 |
> > > After a kernel update the VirtualBox won't find them any |
| 21 |
> > > more and do not expect that at all. |
| 22 |
> > > |
| 23 |
> > > I could delete the package and build-install it again, but |
| 24 |
> > > then the old kernels modules would disappear. I just want |
| 25 |
> > > to install the new ones. |
| 26 |
> > > |
| 27 |
> > > I could do a sequence of "ebuild" commands. Is there a |
| 28 |
> > > front end "emerge" command, too? Something like the -U flag? |
| 29 |
> > |
| 30 |
> > emerge @module-rebuild |
| 31 |
> > |
| 32 |
> > (find out via 'emerge --list-sets') |
| 33 |
> |
| 34 |
> Exactly what I searched for. Works. |
| 35 |
|
| 36 |
You can also rebuild by file name if you don't know which ebuild they |
| 37 |
belong to, like in: |
| 38 |
|
| 39 |
emerge -1a $(find /lib/modules/4.4.39-gentoo/misc -type f) |
| 40 |
|
| 41 |
This is a pretty unknown feature... |
| 42 |
|
| 43 |
-- |
| 44 |
Regards, |
| 45 |
Kai |
| 46 |
|
| 47 |
Replies to list-only preferred. |
Archives