On 9/20/2019 11:29 PM, Kevin Buckley via lfs-dev wrote:
On Sat, 21 Sep 2019 at 07:46, DJ Lucas via lfs-dev
<[email protected]> wrote:
In the book, we currently have the text "Install the modules, if the kernel
configuration uses them:" - this is incorrect. All kernels use them, whether they
are built-in or not, and this step is required to populate /lib/modules/$(uname
-r)/modules.{builtin,dep,order,*}. This sentence should be changed, but I'm at a loss for
the moment. Suggestions?
--DJ
Not clear, from the discussion so far, if the
modules.{builtin,dep,order,*}.
files need to be created for a SysV kernel that was built without any modules,
although DJ's suggestion is that "things fail" for the SysD revision.
I'm sorry, I should clarify. I was under the mistaken impression that
firewalld only ran under systemd, this is not the case (it doesn't even
require elogind on SysV). Although there is an issue with the conntrack
helpers if the modules are builtins (for which I also intend to use the
modules.builtin file to fix this problem upstream as was already done in
the earlier bug that I pointed to). But, yes, this is on SysV and
systemd. I'm building a no loadable modules kernel now.
--DJ
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
