From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Adam Duskett <aduskett@gmail.com>,
Thierry Bultel <thierry.bultel@linatsea.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/4] fs/cpio: accept a list of dracut.conf files
Date: Sat, 17 Sep 2022 23:10:29 +0200 [thread overview]
Message-ID: <20220917211029.GA1127102@scaer> (raw)
In-Reply-To: <55b0aae8-4e00-990b-2f98-abbb4437c29e@mind.be>
Arnout, All,
On 2022-09-17 22:17 +0200, Arnout Vandecappelle spake thusly:
> On 19/08/2022 19:51, Yann E. MORIN wrote:
> >Allow users to specify more than one dracut config file to cover
> >tose cases.
[--SNIP--]
> Applied to master, thanks.
[--SNIP--]
> >diff --git a/fs/cpio/Config.in b/fs/cpio/Config.in
> >index 861e9a929e..94a826f9e4 100644
> >--- a/fs/cpio/Config.in
> >+++ b/fs/cpio/Config.in
> >@@ -29,13 +29,15 @@ endchoice
> > if BR2_TARGET_ROOTFS_CPIO_DRACUT
> >-config BR2_TARGET_ROOTFS_CPIO_DRACUT_CONF_FILE
> >- string "dracut configuration file"
> >+config BR2_TARGET_ROOTFS_CPIO_DRACUT_CONF_FILES
When that patch was written, we did not have a release yet with support
for dracut, so I did not add a legacy for _CPIO_DRACUT_CONF_FILE when I
made it a plural. But 2022.08 does have dracut, so we now need to handle
the legacy for BR2_TARGET_ROOTFS_CPIO_DRACUT_CONF_FILE (or not make it a
plural).
Regards,
Yann E. MORIN.
> >+ string "dracut configuration files"
> > default "fs/cpio/dracut.conf"
> > help
> >- Dracut configuration file. It determines which parts of the
> >- rootfs get included in the cpio image. See dracut.conf(5) or
> >- https://github.com/dracutdevs/dracut/blob/master/man/dracut.conf.5.asc
> >+ Space-separated list of Dracut configuration files. They
> >+ determine which parts of the rootfs get included in the
> >+ cpio image. See:
> >+ dracut.conf(5)
> >+ https://github.com/dracutdevs/dracut/blob/master/man/dracut.conf.5.asc
> > The default configuration file is suitable for busybox init.
> > It doesn't, however, pivot_root into a full rootfs.
> >diff --git a/fs/cpio/cpio.mk b/fs/cpio/cpio.mk
> >index fa66b1c710..d671c337df 100644
> >--- a/fs/cpio/cpio.mk
> >+++ b/fs/cpio/cpio.mk
> >@@ -50,9 +50,14 @@ else ifeq ($(BR2_TARGET_ROOTFS_CPIO_DRACUT),y)
> > ROOTFS_CPIO_DEPENDENCIES += host-dracut
> >-ROOTFS_CPIO_DRACUT_CONF_FILE = $(call qstrip,$(BR2_TARGET_ROOTFS_CPIO_DRACUT_CONF_FILE))
> >-ifeq ($(BR_BUILDING):$(ROOTFS_CPIO_DRACUT_CONF_FILE),y:)
> >-$(error No dracut config file name specified, check your BR2_TARGET_ROOTFS_CPIO_DRACUT_CONF_FILE setting)
> >+ROOTFS_CPIO_DRACUT_CONF_FILES = $(call qstrip,$(BR2_TARGET_ROOTFS_CPIO_DRACUT_CONF_FILES))
> >+ifeq ($(BR_BUILDING),y)
> >+ifeq ($(ROOTFS_CPIO_DRACUT_CONF_FILES),)
> >+$(error No dracut config file name specified, check your BR2_TARGET_ROOTFS_CPIO_DRACUT_CONF_FILES setting)
> >+endif
> >+ifneq ($(words $(ROOTFS_CPIO_DRACUT_CONF_FILES)),$(words $(sort $(notdir $(ROOTFS_CPIO_DRACUT_CONF_FILES)))))
> >+$(error No two dracut config files can have the same basename, check your BR2_TARGET_ROOTFS_CPIO_DRACUT_CONF_FILES setting)
> >+endif
> > endif
> > ifeq ($(BR2_LINUX_KERNEL),y)
> >@@ -63,10 +68,14 @@ ROOTFS_CPIO_OPTS += --no-kernel
> > endif
> > define ROOTFS_CPIO_CMD
> >- mkdir -p $(ROOTFS_CPIO_DIR)/tmp
> >+ mkdir -p $(ROOTFS_CPIO_DIR)/tmp $(ROOTFS_CPIO_DIR)/confdir
> >+ $(foreach cfg,$(ROOTFS_CPIO_DRACUT_CONF_FILES), \
> >+ cp $(cfg) $(ROOTFS_CPIO_DIR)/confdir/$(notdir $(cfg))
> >+ )
> > $(HOST_DIR)/bin/dracut \
> > $(ROOTFS_CPIO_OPTS) \
> >- -c $(ROOTFS_CPIO_DRACUT_CONF_FILE) \
> >+ -c /dev/null \
> >+ --confdir $(ROOTFS_CPIO_DIR)/confdir \
> > --sysroot $(TARGET_DIR) \
> > --tmpdir $(ROOTFS_CPIO_DIR)/tmp \
> > -M \
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-09-17 21:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 17:50 [Buildroot] [PATCH 0/4] dracut: extend support and tests (branch yem/dracut) Yann E. MORIN
2022-08-19 17:50 ` [Buildroot] [PATCH 1/4] support/test/cpio: test for pv already done by listing the cpio archive Yann E. MORIN
2022-09-17 20:13 ` Arnout Vandecappelle
2022-08-19 17:50 ` [Buildroot] [PATCH 2/4] package/dracut: allow users to provide their own modules Yann E. MORIN
2022-09-17 20:17 ` Arnout Vandecappelle
2022-09-17 21:19 ` Yann E. MORIN
2022-09-18 8:57 ` Arnout Vandecappelle
2022-09-18 19:36 ` Yann E. MORIN
2022-08-19 17:51 ` [Buildroot] [PATCH 3/4] fs/cpio: accept a list of dracut.conf files Yann E. MORIN
2022-09-17 20:17 ` Arnout Vandecappelle
2022-09-17 21:10 ` Yann E. MORIN [this message]
2022-09-18 8:41 ` Arnout Vandecappelle
2022-09-18 8:46 ` Yann E. MORIN
2022-08-19 17:51 ` [Buildroot] [PATCH 4/4] support/tests/cpio: extend runtime tests Yann E. MORIN
2022-09-17 20:17 ` Arnout Vandecappelle
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=20220917211029.GA1127102@scaer \
--to=yann.morin.1998@free.fr \
--cc=aduskett@gmail.com \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=thierry.bultel@linatsea.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox