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 4cKTt7304lz30VX for ; Sun, 07 Sep 2025 12:29:35 +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 4cKTt40VfBz2xKC for ; Sun, 07 Sep 2025 12:29:32 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4cKTt24wh9z2pW for ; Sun, 07 Sep 2025 12:29:30 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1757248170; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9mB6m0wuA7m0ERfZRqnraW4JmM7XjAjBuWPXsRsJ+QA=; b=fKAJUlEHM2NrHfy3lxa0T0UoeHBVhxkpCNVKkdJx6pmGuGQpUmoIF+jKYTxJYraS3mX9W4 FyezUAoN4Oh+4KDg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1757248170; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9mB6m0wuA7m0ERfZRqnraW4JmM7XjAjBuWPXsRsJ+QA=; b=eYnoQwBxaDZARskC9/Kd+79J+WfDhJq7Ew+T78mcmr8ewVmXVrn4gdmr0Dx116zHo+isp2 SAI4GUHoIgKh7Hra6+FdAyw/lSTHQ2chTbRqdKorvCTp040j7RbbWo8WoCDafyYbpvNAUj tE0GyCIIrBOCujw4eO/Xev8WfxsKsHfnJsCLw9JKNpsH+0ITzUSqtSnCeBRsQWzAy4jR9R n8pQmWGJElCQ6HWd1dmBIS7Spc6e7Dva3cbGjyzILxbT6bwwIPdAF81iu47+AyusJffNxH sk5anf2DFnCZanhgZJ3BQ0gOITt6hPDqz7CIrnujGHZU3wtrXd/mjRYCth9UBA== Message-ID: Subject: Re: dracut-ng From: Stefan Schantl To: development@lists.ipfire.org Date: Sun, 07 Sep 2025 14:29:08 +0200 In-Reply-To: References: <3a21931a-8ad0-40b8-b4e2-a5cbd0ac61d7@ipfire.org> <5B5EF7C9-775C-4F28-94C6-A3C8CE756AC1@ipfire.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Hello Adolf, > Hi Michael & all, >=20 > On 02/09/2025 16:00, Michael Tremer wrote: > > Hello Adolf, > >=20 > > Yes, I would be happy for you to give this a try. > >=20 > > 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. > >=20 > > 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. > >=20 > > Let us know what you find out during testing it :) >=20 > So I tested dracut-ng using the newest version 108. When I installed > IPFire, it built my raid system, it partitioned the disk, created the > filesystem, mounted them and installed the system. >=20 > Then it failed with the message Unable to install the language cache. >=20 > So I then built version 100 and it did exactly the same. >=20 > Then I thought, maybe I had commented out something in the rootfile > that was needed so I did a build with all the rootfile lines > uncommented. >=20 > It still failed exactly the same. >=20 > Any help or suggestions on how I can debug this would be gratefully > accepted. This happens because the setup utils tries to launch the "chroot" binary and ties to execute the the required command to generate the update cache within the changed root directory. https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dblob;f=3Dsrc/installer/main.= c;h=3D9b9c630c35fa44ecb372f58cccad64806c198af4;hb=3DHEAD#l763 In our current used version of dracut the "chroot" binary is part of the base and always is present in a generated initramdisk. During development of dracut and dracut-ng the developers decided, that "chroot" does not have to be packed as default into an initramdisk. https://github.com/dracut-ng/dracut-ng/commit/518133714b769160448a51c512d5e= 152ea6332da So the chroot binary now manually must be specified to be part of the initramdisk. Something like "dracut --install "/usr/sbin/chroot" " should to the trick. Best regards, -Stefan >=20 > Regards, >=20 > Adolf. >=20 > >=20 > > Best, > > -Michael > >=20 > > > 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 > >=20 >=20