From: Lucas De Marchi <lucas.de.marchi@gmail.com>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: "Michal Suchanek" <msuchanek@suse.de>,
linux-modules <linux-modules@vger.kernel.org>,
"Marcus Rückert" <mrueckert@suse.com>,
"Takashi Iwai" <tiwai@suse.com>,
"Dominique Leuenberger" <dimstar@opensuse.org>
Subject: Re: [PATCH] modprobe.d: load from /usr/lib.
Date: Wed, 13 Jan 2021 06:08:41 -0800 [thread overview]
Message-ID: <CAKi4VALOXOqrb34gZMqa29+=5MF8n7VnGPuEWbeu3JpZCJ1F=g@mail.gmail.com> (raw)
In-Reply-To: <20210112222226.GA31541@altlinux.org>
On Tue, Jan 12, 2021 at 2:22 PM Dmitry V. Levin <ldv@altlinux.org> wrote:
>
> On Tue, Jan 12, 2021 at 12:56:05PM -0800, Lucas De Marchi wrote:
> > On Tue, Jan 12, 2021 at 8:06 AM Michal Suchanek <msuchanek@suse.de> wrote:
> > >
> > > There is an ongoing effort to limit use of files outside of /usr (or
> > > $prefix on general). Currently all modprobe.d paths are hardcoded to
> > > outside of $prefix. Teach kmod to load modprobe.d from $prefix/lib.
> >
> > /lib came from module-init-tools and we kept it for compatibility. It
> > became a non-issue when distros
> > decided to just merge them and do a symlink /lib -> /usr/lib following
> > https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
> >
> > what distros didn't do that?
>
> FWiW, we decided not to do TheUsrMerge at all.
It looks like we will need to put this behind a compilation option
then: --enable-split-usr.
Then we only add the additional dir if split-usr is being used.
If it's not used, we may actually change the path and corresponding
docs to move it to /usr,
but that is another separate change.
thanks
Lucas De Marchi
>
>
> --
> ldv
next prev parent reply other threads:[~2021-01-13 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 16:02 [PATCH] modprobe.d: load from /usr/lib Michal Suchanek
2021-01-12 20:56 ` Lucas De Marchi
2021-01-12 22:22 ` Dmitry V. Levin
2021-01-13 14:08 ` Lucas De Marchi [this message]
2021-01-14 9:54 ` Michal Suchánek
2021-05-30 9:39 ` Michal Suchánek
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='CAKi4VALOXOqrb34gZMqa29+=5MF8n7VnGPuEWbeu3JpZCJ1F=g@mail.gmail.com' \
--to=lucas.de.marchi@gmail.com \
--cc=dimstar@opensuse.org \
--cc=ldv@altlinux.org \
--cc=linux-modules@vger.kernel.org \
--cc=mrueckert@suse.com \
--cc=msuchanek@suse.de \
--cc=tiwai@suse.com \
/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).