From: jim.cromie@gmail.com
To: Ian Pilcher <arequipeno@gmail.com>
Cc: linux-modules@vger.kernel.org, kernelnewbies@kernelnewbies.org
Subject: Re: Faster, incremental depmod when adding modules?
Date: Thu, 13 Oct 2022 09:40:33 -0600 [thread overview]
Message-ID: <CAJfuBxy+U6eK=3SM6JE4zW7cuQU=rq-0ePR0duEnNb718PEOEQ@mail.gmail.com> (raw)
In-Reply-To: <148c7e0e-3de9-e3ad-81a3-5444864e9bfe@gmail.com>
On Sun, Aug 21, 2022 at 12:46 PM Ian Pilcher <arequipeno@gmail.com> wrote:
>
> When installing 1 or more out-of-tree modules within
> /lib/modules/$UNAME, is it possible to run depmod in an incremental
> fashion - adding symbols from the new modules to modules.dep[.bin]
> without re-scanning all of the other modules from that kernel version?
>
> I've tried specifying the new module files, but that seems to create a
> completely new modules.dep containing *only* the symbols from the new
> modules (which obviously isn't very useful).
>
OPTIONS
-a, --all
Probe all modules. This option is enabled by default if no
file names are given in the command-line.
-A, --quick
This option scans to see if any modules are newer than the
modules.dep file before any work is done: if not, it silently exits
rather than regenerating the files.
2nd looks like what u want
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2022-10-13 15:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 18:46 Faster, incremental depmod when adding modules? Ian Pilcher
2022-10-13 15:40 ` jim.cromie [this message]
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='CAJfuBxy+U6eK=3SM6JE4zW7cuQU=rq-0ePR0duEnNb718PEOEQ@mail.gmail.com' \
--to=jim.cromie@gmail.com \
--cc=arequipeno@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-modules@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).