[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230718084300.GU9196@kitsune.suse.cz>
Date: Tue, 18 Jul 2023 10:43:00 +0200
From: Michal Suchánek <msuchanek@...e.de>
To: Jan Engelhardt <jengelh@...i.de>
Cc: linux-modules@...r.kernel.org, Takashi Iwai <tiwai@...e.com>,
Lucas De Marchi <lucas.de.marchi@...il.com>,
Michal KoutnĂ˝ <mkoutny@...e.com>,
Jiri Slaby <jslaby@...e.com>,
Masahiro Yamada <masahiroy@...nel.org>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Nicolas Schier <nicolas@...sle.eu>,
linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH kmod v4 4/4] libkmod, depmod, modprobe: Make directory
for kernel modules configurable
Hello,
On Mon, Jul 17, 2023 at 09:28:30PM +0200, Jan Engelhardt wrote:
>
> On Monday 2023-07-17 12:39, Michal Suchanek wrote:
>
> >modprobe.d is now searched under ${prefix}/lib, add ${module_directory} to
> >specify the directory where to search for kernel modules.
> >
> >With this distributions that do not want to ship files in /lib can also
> >move kernel modules to /usr while others can keep them in /lib.
>
> This patch breaks kernel builds/installation.
>
> * assume $distro has given me a kmod that has your submission included,
> and such kmod was ./configure'd --with-module-directory=/usr/lib/modules
>
> With such a kmod, the module installation of current and past kernels
> is not possible, in other words, ** bisecting kernels ** is broken:
It might be nice to provide backwads compatibility with earlier
configurations.
However, if it comes at the cost of making the implementation more
complex and future maintenance more difficult it might not be such a
great idea. So far I have not seen a proposal how to do it nicely.
You can use any of the number of workarounds that have been used for
installing kernels on usrmerged distributions up until now.
sed -i -e s,/lib/modules,/usr/lib/modules, Makefile scripts/depmod.sh is
one.
Failing depmod is not critical, you can fix it up after the fact once
the modules are deployed on the test system.
You can also build a differently configured kmod for the purpose and
pass it with DEPMOD= to the kernel build.
Thanks
Michal
Powered by blists - more mailing lists