[PATCH] flash-images: Drop 2gb-ext4 from image filename

[PATCH] flash-images: Drop 2gb-ext4 from image filename

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 803 bytes --]

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.

Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
---
 lfs/flash-images | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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  = /dev/mapper/$(patsubst /dev/%,%,$(DEVICE))p3
 
-IMAGE_FILE = /install/images/$(SNAME)-$(VERSION).2gb-ext4.$(BUILD_ARCH)-full-core$(CORE).img.xz
+IMAGE_FILE = /install/images/$(SNAME)-$(VERSION)-core$(CORE)-$(BUILD_ARCH).img.xz
 
 FSTAB_FMT = UUID=%s %-8s %-4s %-10s %d %d\n
 
-- 
2.30.2

Re: [PATCH] flash-images: Drop 2gb-ext4 from image filename

[Jon Murphy]

[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]

I’ve always been curious about the 2 GB max size. 

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> wrote:
> 
> 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.
> 
> Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
> ---
> lfs/flash-images | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> 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  = /dev/mapper/$(patsubst /dev/%,%,$(DEVICE))p3
> 
> -IMAGE_FILE = /install/images/$(SNAME)-$(VERSION).2gb-ext4.$(BUILD_ARCH)-full-core$(CORE).img.xz
> +IMAGE_FILE = /install/images/$(SNAME)-$(VERSION)-core$(CORE)-$(BUILD_ARCH).img.xz
> 
> FSTAB_FMT = UUID=%s %-8s %-4s %-10s %d %d\n
> 
> -- 
> 2.30.2
> 

Re: [PATCH] flash-images: Drop 2gb-ext4 from image filename

[Arne Fitzenreiter]

[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]

Am 2022-08-09 21:03, schrieb Jon Murphy:
> I’ve 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 
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)


> 
> 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> 
>> wrote:
>> 
>> 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.
>> 
>> Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
>> ---
>> lfs/flash-images | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>> 
>> 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  = /dev/mapper/$(patsubst /dev/%,%,$(DEVICE))p3
>> 
>> -IMAGE_FILE = 
>> /install/images/$(SNAME)-$(VERSION).2gb-ext4.$(BUILD_ARCH)-full-core$(CORE).img.xz
>> +IMAGE_FILE = 
>> /install/images/$(SNAME)-$(VERSION)-core$(CORE)-$(BUILD_ARCH).img.xz
>> 
>> FSTAB_FMT = UUID=%s %-8s %-4s %-10s %d %d\n
>> 
>> --
>> 2.30.2
>>