From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <n.ullreich@proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits))
 (No client certificate requested)
 by lists.proxmox.com (Postfix) with ESMTPS id 26CA0CC02
 for <pve-devel@lists.proxmox.com>; Mon, 10 Jul 2023 15:50:05 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id 0A39718652
 for <pve-devel@lists.proxmox.com>; Mon, 10 Jul 2023 15:50:05 +0200 (CEST)
Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com
 [94.136.29.106])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits))
 (No client certificate requested)
 by firstgate.proxmox.com (Proxmox) with ESMTPS
 for <pve-devel@lists.proxmox.com>; Mon, 10 Jul 2023 15:50:04 +0200 (CEST)
Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1])
 by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 2C7144294F
 for <pve-devel@lists.proxmox.com>; Mon, 10 Jul 2023 15:50:04 +0200 (CEST)
From: Noel Ullreich <n.ullreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Date: Mon, 10 Jul 2023 15:49:49 +0200
Message-Id: <20230710134951.79263-3-n.ullreich@proxmox.com>
X-Mailer: git-send-email 2.39.2
In-Reply-To: <20230710134951.79263-1-n.ullreich@proxmox.com>
References: <20230710134951.79263-1-n.ullreich@proxmox.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.061 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DMARC_MISSING             0.1 Missing DMARC policy
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
 T_SCC_BODY_TEXT_LINE    -0.01 -
Subject: [pve-devel] [PATCH pmg_docs 1/1] Consistency of GB and GiB pmg
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Mon, 10 Jul 2023 13:50:05 -0000

Since the actual system-checks are done in GiB and to stay consistent
with the other docs, change all GB units to GiB

Signed-off-by: Noel Ullreich <n.ullreich@proxmox.com>
---
 pmg-planning-deployment.adoc | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/pmg-planning-deployment.adoc b/pmg-planning-deployment.adoc
index 9287574..6a0083b 100644
--- a/pmg-planning-deployment.adoc
+++ b/pmg-planning-deployment.adoc
@@ -110,13 +110,13 @@ Minimum System Requirements
 
 * CPU: 64bit (Intel EMT64 or AMD64)
 
-* 2 GB RAM
+* 2 GiB RAM
 
 * Bootable CD-ROM-drive or USB boot support
 
 * Monitor with a minimum resolution of 1024x768 for the installation
 
-* Hard disk with at least 8 GB of disk space
+* Hard disk with at least 8 GiB of disk space
 
 * Ethernet network interface card (NIC)
 
@@ -127,7 +127,7 @@ Recommended System Requirements
 * Multi-core CPU: 64bit (Intel EMT64 or AMD64), +
 ** for use in a virtual machine, activate Intel VT/AMD-V CPU flag
 
-* 4 GB RAM
+* 4 GiB RAM
 
 * Bootable CD-ROM-drive or USB boot support
 
@@ -135,7 +135,7 @@ Recommended System Requirements
 
 * 1 Gbps Ethernet network interface card (NIC)
 
-* Storage: at least 8 GB free disk space, best set up with redundancy,
+* Storage: at least 8 GiB free disk space, best set up with redundancy,
   using a hardware RAID controller with battery backed write cache (``BBU'') or
   ZFS. ZFS is not compatible with hardware RAID controllers. For best
   performance, use enterprise-class SSDs with power loss protection.
-- 
2.39.2