From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Wit <linuxcdeveloper@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Fwd: [PATCH] fs/user-initrd: add new method for building customizable INITRD
Date: Wed, 13 Sep 2023 11:45:08 +0200 [thread overview]
Message-ID: <20230913114508.70a1ea44@windsurf> (raw)
In-Reply-To: <CAEVrM6QhnK8kbQDtjzx8_rNLTq4s96EK=vUQz-vf1QVZUpt64g@mail.gmail.com>
Hello Witold,
On Wed, 13 Sep 2023 06:41:48 +0200
Wit <linuxcdeveloper@gmail.com> wrote:
> Hello All!
>
> As for now user has not much influence on creation of contents of an
> INITRD image I've made some proof of concept of some wider idea of
> creating customizable INITRD image.
> This patch adds possibility of creating customizable INITRD image by
> selecting some of packages to install. At the moment it supports only
> glibc builds but I planned to add support for musl and uClibc as well.
> I've got also some other plans regarding this patch.
> This patch adds new submenu in "Filesystem images" main menu.
>
> I'm sending this patch for evaluation. If the idea of this patch is ok
> for you I could take care of developing it.
>
> Signed-off-by: Witold Kowolik <linuxcdeveloper@gmail.com>
Thanks for your proposal. A couple of comments:
(1) Your patch is line-wrapped, so difficult to review. Could you use
git send-email to send your patches?
(2) Have you looked at Dracut and its integration in Buildroot? Because
to me it does pretty much the same as what you're doing. We know
Dracut's integration in Buildroot has some shortcomings, but I'd
rather see them being resolved rather than introduce another new
mechanism.
(3) I see you're using a Perl script. We generally try to have most of
the Buildroot plumbing implemented either in shell or in Python.
However, it's true that having a Python interpreter on the host is
no longer required, while having a Perl interpreter is (which would
go in favor of keeping a Perl script).
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-13 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEVrM6T=5vb98vVUr4AxNWf7xV6VSLyuNME1HpxW=KVJR1vvQw@mail.gmail.com>
2023-09-13 4:41 ` [Buildroot] Fwd: [PATCH] fs/user-initrd: add new method for building customizable INITRD Wit
2023-09-13 9:45 ` Thomas Petazzoni via buildroot [this message]
2023-09-13 13:30 ` Yann E. MORIN
2023-09-13 14:27 ` Wit
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=20230913114508.70a1ea44@windsurf \
--to=buildroot@buildroot.org \
--cc=linuxcdeveloper@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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