| 1 |
2016-07-16 4:45 GMT-03:00 Neil Bothwick <neil@××××××××××.uk>: |
| 2 |
|
| 3 |
> On Fri, 15 Jul 2016 19:59:51 -0300, Facundo Curti wrote: |
| 4 |
> |
| 5 |
> > > Why do you want DKMS whereas you already compile your own kernel? |
| 6 |
> |
| 7 |
> > Because I have a module that is outside the kernel tree: |
| 8 |
> |
| 9 |
> You don't need DKMS for that, either re-emerge the module manually after |
| 10 |
> compiling a new kernel or run emerge @module-rebuild. If the module is |
| 11 |
> not in portage, manually reinstall it for each new kernel. |
| 12 |
> |
| 13 |
> DKMS is for people that don't get involved in compiling kernels or |
| 14 |
> modules, it is for users of binary distros. |
| 15 |
> |
| 16 |
> |
| 17 |
> -- |
| 18 |
> Neil Bothwick |
| 19 |
> |
| 20 |
> Walking on water and writing software to specification is easy if they're |
| 21 |
> frozen. |
| 22 |
> |
| 23 |
|
| 24 |
It is not in portage. It is a unique module. Edited by me in the source |
| 25 |
code. |
| 26 |
|
| 27 |
But how can I install the module without dkms? usually I make this |
| 28 |
automatically with dkms :S |
Archives