[Buildroot] [PATCH 1/1] package/skeleton-init-common: Create /lib/modules directory

Norbert Lange nolange79 at gmail.com
Mon Mar 18 18:11:17 UTC 2019


Am Mo., 18. März 2019 um 18:44 Uhr schrieb Yann E. MORIN
<yann.morin.1998 at free.fr>:
>
> On 2019-03-18 17:30 +0100, Norbert Lange spake thusly:
> > For read-only root file systems, the kernel-modules
> > will be mounted over this directory.
>
> This does not mean anything.
>
> Either you build your kernel with Buildroot, and the kernel does the
> installation of modules in /lib/modules, and thus you do not need to
> create it, or you build your kernel outside of Buildroot and you install
> the modules at build time in there.
>
> So, having a read-only filesystem is of no consequence here.
>
> Also, I don;t see how "the kernel-modules will be mounted over this
> directory", which imply this is done at runtime. If your system uses
> special means to store the kernel modules, then it's your duty to
> provide it on your own, like as an overlay (or a specific package) that
> install those files/direcoties.

If you prepare a kernel with an builtin initramfs containing
the modules and an initscript to mount those over /lib/modules,
then you wont have to touch the root fs.
(can be replaced independently of each other).

>
> > This directory should always exist for this reason,
>
> This is wrong: one can have a no-module kernel, in which case
> /lib/modules is useless.

One could also have nothing to use with  /mnt, /media and /opt.

> > just as /mnt and /opt are in the skeleton.
>
> Those are madanted by the FHS [0].

Ok, if I red that right, then /boot and /srv would be required/mandated aswell?

I guess I wont get the change up-streamed, and thats fine (minor annoyance
that I cant use verbatim buildroot's with such kernels). But this seems
to be pretty arbitrary given that buildroot seems rather lenient
otherwise (for good reasons).

Norbert.


More information about the buildroot mailing list