From: Peter Korsgaard <peter@korsgaard.com>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Danilo Bargen <mail@dbrgn.ch>,
buildroot@buildroot.org,
Suniel Mahesh <sunil@amarulasolutions.com>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Michael Nazzareno Trimarchi <michael@amarulasolutions.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH] configs/roc_pc_rk3399_defconfig: expand rootfs size to 120M
Date: Tue, 15 Feb 2022 09:15:43 +0100 [thread overview]
Message-ID: <87czjok0k0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <6edcbc6d-c9bb-e802-48f1-d4866a698aa9@mind.be> (Arnout Vandecappelle's message of "Mon, 14 Feb 2022 21:13:33 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
>> It is because of modules(30M) and linux "Image", it's not
>> compressed, so it's 25M. So only for Linux+modules => 55M, plus the
>> few other stuff(Busybox+libc etc.)1M
> Yeah those giant aarch64 default configs are mightily annoying...
> I'm thinking, perhaps we should just bite the bullet and move the
> default ext2 size to 120M...
> Peter, Yann, what do you think?
Fine by me.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-02-15 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 17:10 [Buildroot] [PATCH] configs/pcengines_apu2_defconfig: linux needs host libelf Giulio Benetti
2022-02-02 17:10 ` [Buildroot] [PATCH] configs/roc_pc_rk3399_defconfig: expand rootfs size to 120M Giulio Benetti
2022-02-13 11:35 ` Arnout Vandecappelle
2022-02-14 0:03 ` Giulio Benetti
2022-02-14 20:13 ` Arnout Vandecappelle
2022-02-14 20:36 ` Yann E. MORIN
2022-02-15 8:15 ` Peter Korsgaard [this message]
2022-02-14 20:56 ` Arnout Vandecappelle
2022-02-14 20:01 ` [Buildroot] [PATCH] configs/pcengines_apu2_defconfig: linux needs host libelf Arnout Vandecappelle
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=87czjok0k0.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=mail@dbrgn.ch \
--cc=michael@amarulasolutions.com \
--cc=sunil@amarulasolutions.com \
--cc=yann.morin.1998@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.