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 4fgGtD6PdLz2yDc for ; Tue, 24 Mar 2026 17:16:52 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4fgGt941vTz2xM3 for ; Tue, 24 Mar 2026 17:16:49 +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 4fgGt847kXz1xs for ; Tue, 24 Mar 2026 17:16:48 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1774372608; 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; bh=ycjNy1CGnruJfTt8K1u4pw3gvLkZnY7MdenLCKbxHlo=; b=BXwBKOov05AP9fP5tLMAmHHswgMNbJY0ooKUa+ibm3nW+xeq/MajYVjdy9y+6XYAKwHPZL 9B/kvFD5vSZ2nhDw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1774372608; 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; bh=ycjNy1CGnruJfTt8K1u4pw3gvLkZnY7MdenLCKbxHlo=; b=oJkgSIxQnpv7CFQNuPz0Wzobb9gkbxAF8P6foVWWDAWeb5h30BxCvMta93LbcmVM/D3WH6 eDvPbYDBQshjeJAAqkLPa56cG3v8E1+DQBOAyUtOyswsBDFhda/65ASpG+TtRhs1rjaogf /+6i0ssqUf7xwBPHP7e1sigl9Lt3XKRuA2IRjvJrMH9W6iBDDMcSnJ96tY71oCn84+YwpC 0n2vNR451MwVb+9AqirdWKgcZbV+bt9RQx7dpdNH7LQh+Lj2WFpBTlYIHHIW16kxZkDfMX pQ25o/TsIa5czJnt7c9ezv6Nhs29W8HavkZHYJHpZ4NqpWDkwIRGkx9vz48mag== From: Michael Tremer Content-Type: text/plain; charset=us-ascii 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 Subject: Building IPFire without using loop devices Message-Id: <910F5D38-B456-4C23-9795-8F0DE003EAE8@ipfire.org> Date: Tue, 24 Mar 2026 17:16:47 +0000 To: "IPFire: Development-List" Hello everyone, On the last call, some people raised that the distribution no longer = builds properly when running a recent version of GNOME or a similar = desktop environment. We identified that the problem is udisk2 trying to = figure out what the new device is that has just been mounted, not = understanding that it is inside a container and that there should be no = access. Since loop devices are not namespaces in Linux, there is no way to get = around this. However, I have put some code together that generates the = image without using any loop devices whatsoever: = https://git.ipfire.org/?p=3Dpeople/ms/ipfire-2.x.git;a=3Dshortlog;h=3Drefs= /heads/no-loop Could the people who have been affected by this and check if this branch = builds without any problems and if the generated image is also bootable = in either EFI, non-EFI or both modes, please? Feel free to hit me up with any problems or questions. Best, -Michael=