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 4cKWPD1C8rz2ymx for ; Sun, 07 Sep 2025 13:38:08 +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 4cKWP85qjSz2xKC for ; Sun, 07 Sep 2025 13:38:04 +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 4cKWP23x5ZzTD; Sun, 07 Sep 2025 13:37:58 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1757252278; 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=ap2cwYaxnnFLUR+o3jKNOj2BXCF1kVCkHhR6qD1eQoY=; b=sfV1gfjn8CuGrh01WJJghnCmmkvlComTPGp4PwQwUbBCZqCNwEInhaDzh1o2/N01ZNzVEr UsZx/7m3j4dc0GCw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1757252278; 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=ap2cwYaxnnFLUR+o3jKNOj2BXCF1kVCkHhR6qD1eQoY=; b=AQTLrqhbIka8BxX3u2PNuGnceg0tnpJjP25ioqv3WGjVyXPJm0iPe/my0Eml+reR9OxZQW eypBuKY7tHpj4RcrAoelYor27WlmJHb58Xg4YDFjCWxoE6rajtJAy04g6d0CWUiBgFc+vV b3SJyiFhBo0Xn2p/VEpUL15nSGT4hjoigfRuHmTNxako6xFDzMR7FvcA19GWUemb8nmtv4 pv/M/kN5qOcVBB8MGwFl9umC1H/iTRT1RqqqfMncAmAJnFMbxTJDPr2ZQrksm2mVG8fssp peFBhjOv6CnKDKsoQ4hiVeBdhnGtflTyX/A4QzG66RAHd5yoOtnRB0areD4gxA== Message-ID: <1ca6a0c8-da42-483f-af8b-e31acfc3497d@ipfire.org> Date: Sun, 7 Sep 2025 15:37:55 +0200 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: dracut-ng To: Stefan Schantl References: <3a21931a-8ad0-40b8-b4e2-a5cbd0ac61d7@ipfire.org> <5B5EF7C9-775C-4F28-94C6-A3C8CE756AC1@ipfire.org> Content-Language: en-GB Cc: "IPFire: Development-List" From: Adolf Belka In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Stefan, On 07/09/2025 14:29, Stefan Schantl wrote: > Hello Adolf, >> Hi Michael & all, >> >> On 02/09/2025 16:00, Michael Tremer wrote: >>> 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 :) >> >> 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. >> >> Then it failed with the message Unable to install the language cache. >> >> So I then built version 100 and it did exactly the same. >> >> 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. >> >> It still failed exactly the same. >> >> 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=ipfire-2.x.git;a=blob;f=src/installer/main.c;h=9b9c630c35fa44ecb372f58cccad64806c198af4;hb=HEAD#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/518133714b769160448a51c512d5e152ea6332da Yes, so I see it was already in the old dracut version 058. If I had tried updating from our current version 054 to 058, I would have had the same problem. > > 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. Giving it a try currently in a build. Thanks very much for your help on this. Regards, Adolf. > > Best regards, > > -Stefan >> >> Regards, >> >> Adolf. >> >>> >>> Best, >>> -Michael >>> >>>> On 2 Sep 2025, at 13:13, Adolf Belka >>>> wrote: >>>> >>>> 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. >>>> >>>> >>> >> >