From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arne Fitzenreiter To: development@lists.ipfire.org Subject: Re: [PATCH] flash-images: Drop 2gb-ext4 from image filename Date: Wed, 10 Aug 2022 09:44:31 +0200 Message-ID: <4668cf14f837cc9843f0b130bf22baab@ipfire.org> In-Reply-To: <4989289A-1DEB-49C3-B939-4EB56006F02E@gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2346178883541674808==" List-Id: --===============2346178883541674808== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Am 2022-08-09 21:03, schrieb Jon Murphy: > I=E2=80=99ve always been curious about the 2 GB max size. It was not the max size. It was the minimal size of the media that could=20 used. Now it is larger so 4GB cards are now minimum. At first boot IPFire resize it to the size of the used media up to 2 TB (max size of a MBR partitioned disk) >=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? >=20 > No rush - just curious. >=20 >=20 > Jon >=20 >> On Aug 8, 2022, at 3:27 PM, Michael Tremer =20 >> wrote: >>=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 >> --- >> 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=20 >> /install/images/$(SNAME)-$(VERSION).2gb-ext4.$(BUILD_ARCH)-full-core$(CORE= ).img.xz >> +IMAGE_FILE =3D=20 >> /install/images/$(SNAME)-$(VERSION)-core$(CORE)-$(BUILD_ARCH).img.xz >>=20 >> FSTAB_FMT =3D UUID=3D%s %-8s %-4s %-10s %d %d\n >>=20 >> -- >> 2.30.2 >>=20 --===============2346178883541674808==--