admin: system-booting: add screenshots

additionally adapt the paths for pmg with:
sed -ri 's/screenshot\///g' system-booting.adoc

Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>

diff --git a/images/screenshot/boot-grub.png b/images/screenshot/boot-grub.png
new file mode 100644 (file)
index 0000000..b2716de
Binary files /dev/null and b/images/screenshot/boot-grub.png differ

diff --git a/images/screenshot/boot-systemdboot.png b/images/screenshot/boot-systemdboot.png
new file mode 100644 (file)
index 0000000..56ed672
Binary files /dev/null and b/images/screenshot/boot-systemdboot.png differ

diff --git a/system-booting.adoc b/system-booting.adoc
index af5b767f54823a7f347990e83148e8a38dbf9ccf..bdbac1f8708ee3e08fbd1958adf91d2d0e64eca6 100644 (file)
--- a/system-booting.adoc
+++ b/system-booting.adoc
@@ -178,7 +178,7 @@ Partitions (ESPs) after a manual kernel addition or removal from above.
 Determine which Bootloader is Used
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-[thumbnail="screenshot/boot-grub.png", float="left"]
+[thumbnail="boot-grub.png", float="left"]
 
 The simplest and most reliable way to determine which bootloader is used, is to
 watch the boot process of the {pmg} node.
@@ -186,7 +186,7 @@ watch the boot process of the {pmg} node.
 You will either see the blue box of GRUB or the simple black on white
 `systemd-boot`.
 
-[thumbnail="screenshot/boot-systemdboot.png"]
+[thumbnail="boot-systemdboot.png"]
 
 Determining the bootloader from a running system might not be 100% accurate. The
 safest way is to run the following command: