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 4f2dbX5Fwhz332V for ; Fri, 30 Jan 2026 14:26:00 +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) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4f2dbT18L5z3332 for ; Fri, 30 Jan 2026 14:25:57 +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 4f2dbS3Wp2z310; Fri, 30 Jan 2026 14:25:56 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1769783156; 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=EZlbqer+BusJyNsngmvo0KH36RYwgiy1U9BFCPJKB6o=; b=bXPuzqtyxj6c0jJAdu3iNbKhxV3wBq7c98Y8Pn573YF31r+47OeAiP3wn4i9Og1wuPGF2Z Ov1YiTZqWI7oGeCg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1769783156; 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=EZlbqer+BusJyNsngmvo0KH36RYwgiy1U9BFCPJKB6o=; b=ElMrjBN1VoQMBfU5y52Qd+nZ5b36zgG2WYJyTJXj6eFdfCd/5Z+ZStoaG9NLPDiPTp/OXd LkvC/mnlKlcRC2zq/m6AF1H8cnKfmJTmCYNXAKKbJErNQEoIxHa5m7IaLSQ2/0wCG6Ivyi WHhuHII+Qtvc7q6nar7M/uHKSQpJWgkC8Q1pYPpiFgMxdvqSR9wIGeu7h78bW7ewmk7lzW 576k3W7MdLIStjq92CvXnsjOIQzGuP4Aqlcudz/HVMfvjFcSNDBRlJubYdMTsjQosn+5Sf 5GNilwBi9G37VG/IK8BDqFU7aLHYjC9u7Z0kjUEuwskCfo/UdVgWai0twdL2QQ== Content-Type: text/plain; charset=utf-8 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: [PATCH] installer: Increase size of mount for iso due to size increase From: Michael Tremer In-Reply-To: Date: Fri, 30 Jan 2026 15:25:26 +0100 Cc: development@lists.ipfire.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20260128185006.4131577-1-adolf.belka@ipfire.org> <430044BC-94E0-4D3C-BA10-095C408DFFB6@ipfire.org> To: Adolf Belka Hello Adolf, > On 30 Jan 2026, at 14:25, Adolf Belka wrote: >=20 > Hi Michael, >=20 > On 30/01/2026 10:20, Michael Tremer wrote: >> Hello Adolf, >> Thanks for this patch. I have merged it. >> The value only specifies a maximum size of the temporary directory. = It won=E2=80=99t use up all the space on allocation. Therefore setting = it to 1024 MiB is absolutely fine. The intention was probably to not = exhaust the system of the entirety of memory, but since we have nowhere = else to write the image to, we will not probably require more than 1 GiB = of memory to make the PXE install work. >=20 > Unless the iso size gets to 1 GiB but we will just have to cross that = bridge when we get to it. It probably will. The kernel will be much bigger and we will also ship = more firmware without ever cleaning anything up there. >> Are you aware of this being documented anywhere? Do we need to add a = note to the installation documentation that at least 2 GiB would be = needed for PXE? >=20 > I have checked in all of our documentation that was shown when = searching for PXE and there is no reference to amount of memory required = for PXE. Thank you! > Regards, >=20 > Adolf. >=20 >> -Michael >>> On 28 Jan 2026, at 19:50, Adolf Belka = wrote: >>>=20 >>> - download.sh defines a mount of 512M for downloading the iso for = use with PXE. >>> Unfortunately since CU192 the iso sizes have been greater than = 512M >>> - This was identified by a user on the forum as their PXE install = failed to work. >>> - They had suggested increasing it to around 800M. As CU200 is = already at 658M I >>> thought it made more sense to give a bit more room and so = specified 1024M. If this >>> is considered too excessive then it can always be modified. >>>=20 >>> Signed-off-by: Adolf Belka >>> --- >>> src/installer/downloadsource.sh | 4 ++-- >>> 1 file changed, 2 insertions(+), 2 deletions(-) >>>=20 >>> diff --git a/src/installer/downloadsource.sh = b/src/installer/downloadsource.sh >>> index 47086b2b7..d8b1ddd03 100644 >>> --- a/src/installer/downloadsource.sh >>> +++ b/src/installer/downloadsource.sh >>> @@ -2,7 +2,7 @@ >>> = ##########################################################################= ##### >>> # = # >>> # IPFire.org - A linux based firewall = # >>> -# Copyright (C) 2007-2022 IPFire Team = # >>> +# Copyright (C) 2007-2026 IPFire Team = # >>> # = # >>> # This program is free software: you can redistribute it and/or = modify # >>> # it under the terms of the GNU General Public License as published = by # >>> @@ -35,7 +35,7 @@ URL=3D"${2}" >>> OUTPUT_DIR=3D"${OUTPUT%/*}" >>>=20 >>> mkdir -p "${OUTPUT_DIR}" >>> -if ! mount -t tmpfs none "${OUTPUT_DIR}" -o size=3D512M; then >>> +if ! mount -t tmpfs none "${OUTPUT_DIR}" -o size=3D1024M; then >>> echo "Could not mount tmpfs to ${OUTPUT_DIR}" >&2 >>> exit 1 >>> fi >>> --=20 >>> 2.52.0 >>>=20 >>>=20 >=20 >=20