public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: dracut-ng
Date: Tue, 2 Sep 2025 14:13:37 +0200	[thread overview]
Message-ID: <3a21931a-8ad0-40b8-b4e2-a5cbd0ac61d7@ipfire.org> (raw)

Hi All,

I was looking at packages that needed updating. I noticed that dracut was at version 056. The source for that had version 059 but that was from Dec 2022 and the last commit in that repo was Mar 2024.

There is a new repo providing dracut-ng. Their version 100 (Apr 2024) is said to be a drop-in replacement for the original dracut. They are now at version 108 and it is being actively maintained.

With it being said to be a drop-in replacement I thought dracut-ng looked a good candidate to test out but as dracut plays a critical role in the booting process I thought I would ask if anyone has any information to indicate that it is not worth trying it.

Regards,

Adolf.



             reply	other threads:[~2025-09-02 12:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02 12:13 Adolf Belka [this message]
2025-09-02 14:00 ` dracut-ng Michael Tremer

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=3a21931a-8ad0-40b8-b4e2-a5cbd0ac61d7@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.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