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 4f2cG46DBYz30KY for ; Fri, 30 Jan 2026 13:25:48 +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 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4f2cG12vGYz2xXH for ; Fri, 30 Jan 2026 13:25:45 +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 4f2cFz5bzzzN7; Fri, 30 Jan 2026 13:25:43 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1769779543; 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=MUQjOv5eJKHSj6JvieF2n0eIWorra5bkdX8k1BZFZU4=; b=ANMe7UvxnCgbPOzRTxTQbeye1S8JLuxX7/N73QGUshdWFXVh8qYnfnl/oe/FHWSbN53GzN 9pRLHs6hmRTqd8Aw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1769779543; 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=MUQjOv5eJKHSj6JvieF2n0eIWorra5bkdX8k1BZFZU4=; b=qkq69hfz0VBkPL/ecjeiSMgmQb4B7527tmX3GuSJyXFEDOi3ySTv/iUllFN3JTRbgzH56J D6d3Z7Gbcn0HrxhaeqVCHn903qPXsb7I3Yii0zbTOpaMMkflSgNntew8UaTq7hVdSZqiv6 /juZM8NOLd6cAOuS0W28dvLFjvFMyMAtE3Fbz1WdHHqUTvJ2cKl2V17cTUsrJa1+DEJsoq EPqDLdD05MqM74aub2sByBvTaFiWy20a4OXVeKe3d4MLcbgPI1M9JEm158hz3liROgSK0K 7KHhu99EThHTUDIJi0E8rR/jfZDPCPBrzKexcAtoY9ko1SlukKjKMsVY+Zf10A== Message-ID: Date: Fri, 30 Jan 2026 14:25:35 +0100 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 To: Michael Tremer Cc: development@lists.ipfire.org References: <20260128185006.4131577-1-adolf.belka@ipfire.org> <430044BC-94E0-4D3C-BA10-095C408DFFB6@ipfire.org> Content-Language: en-GB From: Adolf Belka In-Reply-To: <430044BC-94E0-4D3C-BA10-095C408DFFB6@ipfire.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Michael, 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’t 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. Unless the iso size gets to 1 GiB but we will just have to cross that bridge when we get to it. > > 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? 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. Regards, Adolf. > > -Michael > >> On 28 Jan 2026, at 19:50, Adolf Belka wrote: >> >> - 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. >> >> Signed-off-by: Adolf Belka >> --- >> src/installer/downloadsource.sh | 4 ++-- >> 1 file changed, 2 insertions(+), 2 deletions(-) >> >> 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="${2}" >> OUTPUT_DIR="${OUTPUT%/*}" >> >> mkdir -p "${OUTPUT_DIR}" >> -if ! mount -t tmpfs none "${OUTPUT_DIR}" -o size=512M; then >> +if ! mount -t tmpfs none "${OUTPUT_DIR}" -o size=1024M; then >> echo "Could not mount tmpfs to ${OUTPUT_DIR}" >&2 >> exit 1 >> fi >> -- >> 2.52.0 >> >> >