From: Noel Ullreich <n.ullreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs 2/4] consistency: change mainboard to motherboard
Date: Tue, 27 Jun 2023 14:40:04 +0200 [thread overview]
Message-ID: <20230627124010.57050-3-n.ullreich@proxmox.com> (raw)
In-Reply-To: <20230627124010.57050-1-n.ullreich@proxmox.com>
To be consistent, replaced all instances of mainboard/main board with
motherboard.
Signed-off-by: Noel Ullreich <n.ullreich@proxmox.com>
---
ha-manager.adoc | 2 +-
pve-system-requirements.adoc | 2 +-
qm-pci-passthrough.adoc | 2 +-
qm.adoc | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/ha-manager.adoc b/ha-manager.adoc
index 3724ab3..8773552 100644
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -63,7 +63,7 @@ usually at higher price.
* Eliminate single point of failure (redundant components)
** use an uninterruptible power supply (UPS)
-** use redundant power supplies on the main boards
+** use redundant power supplies in your servers
** use ECC-RAM
** use redundant network hardware
** use RAID for local storage
diff --git a/pve-system-requirements.adoc b/pve-system-requirements.adoc
index bb474ac..bc3689d 100644
--- a/pve-system-requirements.adoc
+++ b/pve-system-requirements.adoc
@@ -20,7 +20,7 @@ used in production.
* CPU: 64bit (Intel EMT64 or AMD64)
-* Intel VT/AMD-V capable CPU/Mainboard for KVM full virtualization support
+* Intel VT/AMD-V capable CPU/motherboard for KVM full virtualization support
* RAM: 1 GB RAM, plus additional RAM needed for guests
diff --git a/qm-pci-passthrough.adoc b/qm-pci-passthrough.adoc
index b90a0b9..4daa5b3 100644
--- a/qm-pci-passthrough.adoc
+++ b/qm-pci-passthrough.adoc
@@ -23,7 +23,7 @@ some requirements to check and preparations to be done to make it work.
Hardware
^^^^^^^^
Your hardware needs to support `IOMMU` (*I*/*O* **M**emory **M**anagement
-**U**nit) interrupt remapping, this includes the CPU and the mainboard.
+**U**nit) interrupt remapping, this includes the CPU and the motherboard.
Generally, Intel systems with VT-d, and AMD systems with AMD-Vi support this.
But it is not guaranteed that everything will work out of the box, due
diff --git a/qm.adoc b/qm.adoc
index ca1dfa2..83f6c53 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -60,7 +60,7 @@ and PCI devices.
Emulated devices and paravirtualized devices
--------------------------------------------
-The PC hardware emulated by QEMU includes a mainboard, network controllers,
+The PC hardware emulated by QEMU includes a motherboard, network controllers,
SCSI, IDE and SATA controllers, serial ports (the complete list can be seen in
the `kvm(1)` man page) all of them emulated in software. All these devices
are the exact software equivalent of existing hardware devices, and if the OS
--
2.39.2
next prev parent reply other threads:[~2023-06-27 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 12:40 [pve-devel] [PATCH pmg-docs; pmg-docs; proxmox-backup/docs 0/8] fix consistency of some words Noel Ullreich
2023-06-27 12:40 ` [pve-devel] [PATCH pve-docs 1/4] consistency of passthrough/pass-through Noel Ullreich
2023-06-27 12:40 ` Noel Ullreich [this message]
2023-06-27 12:40 ` [pve-devel] [PATCH pve-docs 3/4] consistenct of USB flash drive spelling Noel Ullreich
2023-06-27 12:40 ` [pve-devel] [PATCH pve-docs 4/4] Fixed spelling of command line/command-line Noel Ullreich
2023-06-27 12:40 ` [pve-devel] [PATCH proxmox-backup/docs 1/2] consistenct of USB flash drive spelling Noel Ullreich
2023-06-27 13:45 ` [pve-devel] applied: " Thomas Lamprecht
2023-06-27 12:40 ` [pve-devel] [PATCH proxmox-backup/docs 2/2] Fixed spelling of command line/command-line Noel Ullreich
2023-06-27 13:50 ` [pve-devel] applied: " Thomas Lamprecht
2023-07-03 8:15 ` Noel Ullreich
2023-06-27 12:40 ` [pve-devel] [PATCH pmg-docs 1/2] consistenct of USB flash drive spelling Noel Ullreich
2023-06-27 12:40 ` [pve-devel] [PATCH pmg-docs 2/2] Fixed spelling of command line/command-line Noel Ullreich
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=20230627124010.57050-3-n.ullreich@proxmox.com \
--to=n.ullreich@proxmox.com \
--cc=pve-devel@lists.proxmox.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 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.