From: Ian Pilcher <arequipeno@gmail.com>
To: kernelnewbies@kernelnewbies.org, linux-modules@vger.kernel.org
Subject: Faster, incremental depmod when adding modules?
Date: Sun, 21 Aug 2022 13:46:29 -0500 [thread overview]
Message-ID: <148c7e0e-3de9-e3ad-81a3-5444864e9bfe@gmail.com> (raw)
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).
--
========================================================================
Google Where SkyNet meets Idiocracy
========================================================================
next reply other threads:[~2022-08-21 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 18:46 Ian Pilcher [this message]
2022-10-13 15:40 ` Faster, incremental depmod when adding modules? jim.cromie
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=148c7e0e-3de9-e3ad-81a3-5444864e9bfe@gmail.com \
--to=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).