From: Lucas De Marchi <lucas.de.marchi@gmail.com>
To: Jan Tojnar <jtojnar@gmail.com>
Cc: linux-modules <linux-modules@vger.kernel.org>
Subject: Re: Support for /usr/local/lib/modprobe.d
Date: Mon, 6 Jul 2020 23:34:20 -0700 [thread overview]
Message-ID: <CAKi4VAJjjpziyNYNAs5rDivAxt-b=L3ucCUN+P=0Aou7GwsJnA@mail.gmail.com> (raw)
In-Reply-To: <b0894a8dd06ccee4326bcd7ff14e1f871bd45080.camel@gmail.com>
On Wed, Jul 1, 2020 at 6:21 PM Jan Tojnar <jtojnar@gmail.com> wrote:
>
> Hello.
>
> We are working with a project that ships a blacklist file [1] that is
> supposed to be installed to modprobe.d directory but it is not clear
> what the default installation path should be.
>
> Distros will typically install modprobe config files to
> /lib/modprobe.d but it is common to use /usr/local as the default
> prefix [2] for manual `make` invocations. The manual page [3] does not
> list /usr/local/lib/modprobe.d as a supported location though.
>
> In the past module-init-tools added [4] support for that path but that
> repo appears to be abandoned and it does not look like kmod supports
> it [5].
>
> 1. Am I missing something, or was this an omission when porting
> modprobe to kmod?
> 2. Could the support be added?
That is probably because we don't default prefix to /usr/local so people never
actually needed it. Yes, I think we could add. Could you prepare a
patch for that?
> 3. Should we default to /lib or /etc for manual `make` invocations for
> now?
/lib is where packages should install and /etc is up to the system
admin to set up.
if we add /usr/local, then override order would be /etc, /usr/local/lib, /lib.
Lucas De Marchi
>
> [1]:
> https://github.com/medusalix/xow/blob/4aa49f27cb6fcb3da995da9e8d51167bed40f520/Makefile#L22
> [2]:
> https://www.gnu.org/prep/standards/html_node/Directory-Variables.html#index-prefix
> [3]: https://man7.org/linux/man-pages/man5/modprobe.d.5.html
> [4]:
> https://git.kernel.org/pub/scm/utils/kernel/module-init-tools/module-init-tools.git/commit/?id=9454d710137be3799f343cc9d0f833f0802e2111
> [5]:
> https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/tree/libkmod/libkmod.c?id=f5434cf5fc5b567359e1b9207bbab24c6782cfbd#n65
>
> Cheers,
>
> Jan
>
--
Lucas De Marchi
prev parent reply other threads:[~2020-07-07 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 1:20 Support for /usr/local/lib/modprobe.d Jan Tojnar
2020-07-07 6:34 ` Lucas De Marchi [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='CAKi4VAJjjpziyNYNAs5rDivAxt-b=L3ucCUN+P=0Aou7GwsJnA@mail.gmail.com' \
--to=lucas.de.marchi@gmail.com \
--cc=jtojnar@gmail.com \
--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).