From: Michael Stapelberg <michael+lkml-Ocq5V1Lzw0iVILNE37Xk8A@public.gmane.org>
To: Martin Wilck <mwilck-IBi9RG/b67k@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: distri: 20x faster initramfs (initrd) from scratch
Date: Wed, 29 Jan 2020 13:59:24 +0100 [thread overview]
Message-ID: <CANnVG6nrehtmu9xdiR2eTdUsyEwO-43eP-DD9Fv=Wum49T5fbA@mail.gmail.com> (raw)
In-Reply-To: <7212371cedf396e118d6b1a712b7d5aa2e928afe.camel-IBi9RG/b67k@public.gmane.org>
I agree, and getting minitramfs adopted anywhere is not my goal at all
:) See section https://michael.stapelberg.ch/posts/2020-01-21-initramfs-from-scratch-golang/#minitrd-outside-of-distri
On Wed, Jan 29, 2020 at 10:53 AM Martin Wilck <mwilck-IBi9RG/b67k@public.gmane.org> wrote:
>
> On Tue, 2020-01-21 at 18:07 +0100, Michael Stapelberg wrote:
> > Hey,
> >
> > I just published a blog post about a custom proof-of-concept
> > initramfs
> > generator (minitrd):
> >
> > https://michael.stapelberg.ch/posts/2020-01-21-initramfs-from-scratch-golang/
> >
> > This demonstrates that there is still a whole bunch of optimization
> > potential in existing initramfs generators such as dracut :)
>
> Cool, but I don't think it has big chances to be adopted in larger
> mainstream distros unless you add some extension/plugin functionality,
> like dracut's modules.d. Such plugins should be easy to write and
> maintain.
>
> Martin
>
>
>
prev parent reply other threads:[~2020-01-29 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 17:07 distri: 20x faster initramfs (initrd) from scratch Michael Stapelberg
[not found] ` <CANnVG6nFsnvva+qoQHJF+YY6Y3q46-C6tA742fMAkZFB3QFubg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-01-29 9:54 ` Martin Wilck
[not found] ` <7212371cedf396e118d6b1a712b7d5aa2e928afe.camel-IBi9RG/b67k@public.gmane.org>
2020-01-29 12:59 ` Michael Stapelberg [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='CANnVG6nrehtmu9xdiR2eTdUsyEwO-43eP-DD9Fv=Wum49T5fbA@mail.gmail.com' \
--to=michael+lkml-ocq5v1lzw0ivilne37xk8a@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mwilck-IBi9RG/b67k@public.gmane.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).