From: Facundo Curti <facu.curti@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Install dkms: which package
Date: Sat, 16 Jul 2016 06:37:28 -0300 [thread overview]
Message-ID: <CABxff59d9Cm8hEbVyPSJp1hprY0gjbKOHcN7x_XOzh40zA9mSQ@mail.gmail.com> (raw)
In-Reply-To: <20160716084505.4ea2330b@digimed.co.uk>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
2016-07-16 4:45 GMT-03:00 Neil Bothwick <neil@digimed.co.uk>:
> On Fri, 15 Jul 2016 19:59:51 -0300, Facundo Curti wrote:
>
> > > Why do you want DKMS whereas you already compile your own kernel?
>
> > Because I have a module that is outside the kernel tree:
>
> You don't need DKMS for that, either re-emerge the module manually after
> compiling a new kernel or run emerge @module-rebuild. If the module is
> not in portage, manually reinstall it for each new kernel.
>
> DKMS is for people that don't get involved in compiling kernels or
> modules, it is for users of binary distros.
>
>
> --
> Neil Bothwick
>
> Walking on water and writing software to specification is easy if they're
> frozen.
>
It is not in portage. It is a unique module. Edited by me in the source
code.
But how can I install the module without dkms? usually I make this
automatically with dkms :S
[-- Attachment #2: Type: text/html, Size: 1571 bytes --]
next prev parent reply other threads:[~2016-07-16 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 17:20 [gentoo-user] Install dkms: which package Facundo Curti
2016-07-15 21:54 ` Alarig Le Lay
2016-07-15 22:59 ` Facundo Curti
2016-07-16 7:45 ` Neil Bothwick
2016-07-16 9:37 ` Facundo Curti [this message]
2016-07-16 10:52 ` Jeremi Piotrowski
2016-07-16 18:03 ` Facundo Curti
2016-07-16 19:12 ` Neil Bothwick
2016-07-16 22:29 ` Facundo Curti
2016-07-16 22:29 ` Alan McKinnon
2016-07-15 22:13 ` Fernando Rodriguez
2016-07-15 23:29 ` Stroller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABxff59d9Cm8hEbVyPSJp1hprY0gjbKOHcN7x_XOzh40zA9mSQ@mail.gmail.com \
--to=facu.curti@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox