All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Bultel <thierry.bultel@linatsea.fr>
To: buildroot@buildroot.org, yann.morin.1998@free.fr
Subject: Re: [Buildroot] [PATCH v3 3/3] fs/cpio: new option to use dracut tool
Date: Thu, 6 Jan 2022 14:48:52 +0100	[thread overview]
Message-ID: <313f164a-4f58-3212-a75a-d64acbbc0168@linatsea.fr> (raw)
In-Reply-To: <20220106103149.GN614810@scaer>


>> +
>> +show_modules=yes
>> +i18n_install_all=no
>> +lvmconf=no
>> +mdadmconf=no
>> +early_microcode=no
>> +hostonly=no
>> +hostonly_cmdline=no
>> +use_fstab=no
>> +kernel_cmdline="rd.break=initqueue"
>> +do_strip=no
>> +
>> +# Dracut modules need
>> +add_dracutmodules+=" \
>> +busybox-buildroot \
>> +bash
>> +"
>> +
>> +# Modules to ignore
>> +omit_dracutmodules+=" \
> [--SNIP big list of stuff--]
>> +"
> Rather than remove select stuff, can't we just start from an empty set
> and add just what is needed?

Yann,

Unfortunately, This is not that simple.
Dracut will unconditionally source a lot of unwanted modules present in 
host/usr/lib/modules.d
(basically because it considers that the init system is systemd always) 
unless you tell it not to do it.

There is no option to specify another directory to look in, nor a way to 
select the only needed modules.
Only excluding them seems the way.

Also, when you asked why I put the module-setup.sh as executable. You 
are right, it is not mandatory to do
so, because dracut just sources these files. The fact is that all the 
ones that it provides are set
as executables, with no real reason.

Regards,
Thierry
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-01-06 13:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 11:13 [Buildroot] [PATCH v3 1/3] package/cross-ldd: new package Thierry Bultel
2021-12-23 11:13 ` [Buildroot] [PATCH v3 2/3] package/dracut: new host package Thierry Bultel
2022-01-05 23:16   ` Yann E. MORIN
2022-01-06 14:56     ` Thierry Bultel
2022-01-06 15:13       ` Thomas Petazzoni
2022-01-06 15:56         ` Thierry Bultel
2021-12-23 11:13 ` [Buildroot] [PATCH v3 3/3] fs/cpio: new option to use dracut tool Thierry Bultel
2022-01-06 10:31   ` Yann E. MORIN
2022-01-06 13:48     ` Thierry Bultel [this message]
2022-01-05 22:29 ` [Buildroot] [PATCH v3 1/3] package/cross-ldd: new package Yann E. MORIN

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=313f164a-4f58-3212-a75a-d64acbbc0168@linatsea.fr \
    --to=thierry.bultel@linatsea.fr \
    --cc=buildroot@buildroot.org \
    --cc=yann.morin.1998@free.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.