From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4cGS6y6H1cz30Vk for ; Tue, 02 Sep 2025 14:00:10 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R13" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4cGS6v3VHGz2xFx for ; Tue, 02 Sep 2025 14:00:07 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4cGS6t2jMgz1Sq; Tue, 02 Sep 2025 14:00:06 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1756821606; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=92Gbmw1KaF35036ytfokwRq6VDev8GCtiRyjdkOH4Go=; b=u6bjoUEYaqVQ05Pa3cUOnxKWOsPprSbcm4gRLy/hbHz9kBSRMpfBHcCm1Z9ktkLZn3RdPQ C9bRoKu3MxUmLgBA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1756821606; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=92Gbmw1KaF35036ytfokwRq6VDev8GCtiRyjdkOH4Go=; b=ixorV+0AVMN9Oen3CEtaBdshjjwqAYe61VsodpEEQ9WsRvkrXSnzLoHF3im2Y/xW5TiSF5 iWOY9dZ7zjkgvBVnmKSlN+S/r783nJnYDYl8OGoCtuW4+/Mq208+cQN23bu3VCnncozZly WJcDh/T4e6CNYQT4IM++YC4DLKFD/d33hHsdrpIbPFLP3NipUctklHTcTskLaWD2kHZ+MS Un9mYrfa6EI2fgVzQFQf73qSXONneCkcRO8IDz8M1LUM8MyTUR2TfpYFlKkFZ00pxxrOFD w35CcORPsSTnni8BxUr5ltSeN+EGZxtnfBYCJ10AJuCkynPyCCRYtUl3p1mLNA== Content-Type: text/plain; charset=us-ascii Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: dracut-ng From: Michael Tremer In-Reply-To: <3a21931a-8ad0-40b8-b4e2-a5cbd0ac61d7@ipfire.org> Date: Tue, 2 Sep 2025 15:00:05 +0100 Cc: "IPFire: Development-List" Content-Transfer-Encoding: quoted-printable Message-Id: <5B5EF7C9-775C-4F28-94C6-A3C8CE756AC1@ipfire.org> References: <3a21931a-8ad0-40b8-b4e2-a5cbd0ac61d7@ipfire.org> To: Adolf Belka Hello Adolf, Yes, I would be happy for you to give this a try. Since Harald Hoyer has left RedHat, it seems that dracut has effectively = been abandoned and dracut-ng is the successor with pretty much the same = people contributing to it. I did not find any breaking changes in the change log (although it seems = quite extensive), so we might have a very good chance to indeed ship it = as a drop-in. Let us know what you find out during testing it :) Best, -Michael > On 2 Sep 2025, at 13:13, Adolf Belka wrote: >=20 > Hi All, >=20 > 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. >=20 > 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. >=20 > 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. >=20 > Regards, >=20 > Adolf. >=20 >=20