From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jon Murphy <jcmurphy26@gmail.com>
To: development@lists.ipfire.org
Subject: Re: [PATCH] flash-images: Drop 2gb-ext4 from image filename
Date: Tue, 09 Aug 2022 14:03:34 -0500
Message-ID: <4989289A-1DEB-49C3-B939-4EB56006F02E@gmail.com>
In-Reply-To: <20220808202742.1120200-1-michael.tremer@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2036094537126021908=="
List-Id: <development.lists.ipfire.org>

--===============2036094537126021908==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

I=E2=80=99ve always been curious about the 2 GB max size.=20

When the internet was slow and HDs were expensive it made perfect sense. But =
I am curious why not 3 GB or 4 GB?

No rush - just curious.


Jon

> On Aug 8, 2022, at 3:27 PM, Michael Tremer <michael.tremer(a)ipfire.org> wr=
ote:
>=20
> This is now being dropped since the image won't fit onto a 2GB device
> any more and since there is only one type of image, we don't need to
> state the filesystem type.
>=20
> Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
> ---
> lfs/flash-images | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>=20
> diff --git a/lfs/flash-images b/lfs/flash-images
> index b4fde8dd9..af78f5de9 100644
> --- a/lfs/flash-images
> +++ b/lfs/flash-images
> @@ -36,7 +36,7 @@ ifeq "$(EFI)" "1"
> endif
> PART_ROOT  =3D /dev/mapper/$(patsubst /dev/%,%,$(DEVICE))p3
>=20
> -IMAGE_FILE =3D /install/images/$(SNAME)-$(VERSION).2gb-ext4.$(BUILD_ARCH)-=
full-core$(CORE).img.xz
> +IMAGE_FILE =3D /install/images/$(SNAME)-$(VERSION)-core$(CORE)-$(BUILD_ARC=
H).img.xz
>=20
> FSTAB_FMT =3D UUID=3D%s %-8s %-4s %-10s %d %d\n
>=20
> --=20
> 2.30.2
>=20


--===============2036094537126021908==--