Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Clément Péron" <peron.clem@gmail.com>
To: buildroot@buildroot.org
Cc: "Giulio Benetti" <giulio.benetti@benettiengineering.com>,
	"Clément Péron" <peron.clem@gmail.com>
Subject: [Buildroot] [PATCH v2 1/2] configs/beelink_gs1: increase rootfs size to 120M
Date: Sat, 29 Jan 2022 12:17:30 +0100	[thread overview]
Message-ID: <20220129111731.736265-1-peron.clem@gmail.com> (raw)

For the moment Beelink GS1 use a default rootfs size of 60M,
which is a bit low if you want to add some packages like a
graphic stack.

Increase the rootfs size to 120M.

Reviewed-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Signed-off-by: Clément Péron <peron.clem@gmail.com>
---
 configs/beelink_gs1_defconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/configs/beelink_gs1_defconfig b/configs/beelink_gs1_defconfig
index e88f3e3b69..1872aabdf0 100644
--- a/configs/beelink_gs1_defconfig
+++ b/configs/beelink_gs1_defconfig
@@ -24,6 +24,7 @@ BR2_PACKAGE_AUTOSSH=y
 BR2_PACKAGE_DROPBEAR=y
 BR2_TARGET_ROOTFS_EXT2=y
 BR2_TARGET_ROOTFS_EXT2_4=y
+BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
 
 # Firmware
 BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
-- 
2.32.0

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2022-01-29 11:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29 11:17 Clément Péron [this message]
2022-01-29 11:17 ` [Buildroot] [PATCH v2 2/2] configs/beelink_gs1: bump to linux 5.15, atf 2.5 and u-boot 2021.10 Clément Péron
2022-01-29 11:22   ` Giulio Benetti
2022-01-30 17:16   ` Thomas Petazzoni via buildroot
2022-01-30 17:18 ` [Buildroot] [PATCH v2 1/2] configs/beelink_gs1: increase rootfs size to 120M Thomas Petazzoni via buildroot
2022-01-31 12:43   ` Clément Péron

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=20220129111731.736265-1-peron.clem@gmail.com \
    --to=peron.clem@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    /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