From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH v2 2/3] manuals: add rm_work disk space data
Date: Fri, 17 Mar 2023 18:31:29 +0100 [thread overview]
Message-ID: <20230317173130.36268-3-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20230317173130.36268-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/dev-manual/disk-space.rst | 6 ++++++
documentation/poky.yaml.in | 2 ++
2 files changed, 8 insertions(+)
diff --git a/documentation/dev-manual/disk-space.rst b/documentation/dev-manual/disk-space.rst
index 3a5d2b7297..c63591cc7a 100644
--- a/documentation/dev-manual/disk-space.rst
+++ b/documentation/dev-manual/disk-space.rst
@@ -17,6 +17,12 @@ building a recipe once the recipe is built. For more information on
"rm_work", see the :ref:`ref-classes-rm-work` class in the
Yocto Project Reference Manual.
+When you inherit this class and build a ``core-image-sato`` image for a
+``qemux86-64`` machine from an Ubuntu 22.04 x86-64 system, you end up with a
+final disk usage of 22 Gbytes instead of &MIN_DISK_SPACE; Gbytes. However,
+&MIN_DISK_SPACE_RM_WORK; Gbytes of initial free disk space are still needed to
+create temporary files before they can be deleted.
+
Purging Duplicate Shared State Cache Files
==========================================
diff --git a/documentation/poky.yaml.in b/documentation/poky.yaml.in
index 7810b8d2a5..eefdd3f30d 100644
--- a/documentation/poky.yaml.in
+++ b/documentation/poky.yaml.in
@@ -43,3 +43,5 @@ MIN_GCC_VERSION : "7.5"
MIN_MAKE_VERSION : "4.0"
# Disk space (Gbytes) needed to generate qemux86-64 core-image-sato on Ubuntu 22.04 (x86-64), rounded up from 87
MIN_DISK_SPACE : "90"
+# Disk space (Gbytes) needed to generate qemux86-64 core-image-sato on Ubuntu 22.04 (x86-64) with "rm_work", rounded up from 38
+MIN_DISK_SPACE_RM_WORK : "40"
--
2.34.1
next prev parent reply other threads:[~2023-03-17 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <174D0151E4C65905.10271@lists.yoctoproject.org>
2023-03-17 17:31 ` [PATCH v2 0/3] Update and expand system requirements michael.opdenacker
2023-03-17 17:31 ` [PATCH v2 1/3] manuals: update disk space requirements michael.opdenacker
2023-03-17 17:31 ` michael.opdenacker [this message]
2023-03-17 17:31 ` [PATCH v2 3/3] manuals: add minimum RAM requirements michael.opdenacker
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=20230317173130.36268-3-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.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