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.
Given that there may be two different texts for the SysV and SysD books,
then, assuming that it is thought necessary to alter the SysV text, what
about changing the texts so that the two partially "echo" each other:
SysV
If the kernel configuration has specified that any kernel modules be buiil,
create the directory that modules will be stored in, and install the modules,
by running the following command
SysD
Even if the kernel configuration has not specified that any kernel
modules be buiil,
systemd requires that the location they would be stored in be created,
so run the
following command
If it turns out that the SysV kernel really does require the files,
that cause systemd
to fail if they don't exist, then some form of the SysD text should
suffice to convey
why you need to run an "install modules" even when you haven't
explicitly built any
modules.
Just my thr'pen'th,
Kevin
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
