From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] fs/cpio: don't fail systems without /dev/null
Date: Tue, 1 Nov 2022 21:45:41 +0100 [thread overview]
Message-ID: <20221101214541.228f9e47@windsurf> (raw)
In-Reply-To: <20221101183032.3631097-1-yann.morin.1998@free.fr>
On Tue, 1 Nov 2022 19:30:32 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> We pass all our dracut configuration files via a config dir, but dracut
> insist with having one config file. Because we do not want to have to
> chose which file we pass (which would then have to be excluded fro; the
> config dir), we jsut used an arbitrary empty file, and /dev/null seemed
> to be a good candidate.
>
> However, some build environments do not have a complete /dev, and may be
> missing entries otherwise taken for granted, like /dev/null. This is
> especially the case in constrained environments like containers.
>
> Switch away from using /dev/n ull, and do create an actual empty file
> that we can use as the dracut config file.
>
> Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/3249828364
> Reported-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> ---
> fs/cpio/cpio.mk | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-11-01 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 18:30 [Buildroot] [PATCH] fs/cpio: don't fail systems without /dev/null Yann E. MORIN
2022-11-01 20:45 ` Thomas Petazzoni via buildroot [this message]
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=20221101214541.228f9e47@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox