From: Arne Fitzenreiter <arne_f@ipfire.org>
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 [thread overview]
Message-ID: <4668cf14f837cc9843f0b130bf22baab@ipfire.org> (raw)
In-Reply-To: <4989289A-1DEB-49C3-B939-4EB56006F02E@gmail.com>
[-- 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
>>
prev parent reply other threads:[~2022-08-10 7:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 20:27 Michael Tremer
2022-08-09 19:03 ` Jon Murphy
2022-08-10 7:44 ` Arne Fitzenreiter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4668cf14f837cc9843f0b130bf22baab@ipfire.org \
--to=arne_f@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox