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>
This commit is contained in:
Stoiko Ivanov 2024-02-27 11:54:04 +01:00
parent abe750ed54
commit 349ff12ada
3 changed files with 2 additions and 2 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 5.8 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.4 KiB

View File

@ -178,7 +178,7 @@ Partitions (ESPs) after a manual kernel addition or removal from above.
Determine which Bootloader is Used 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 The simplest and most reliable way to determine which bootloader is used, is to
watch the boot process of the {pmg} node. 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 You will either see the blue box of GRUB or the simple black on white
`systemd-boot`. `systemd-boot`.
[thumbnail="screenshot/boot-systemdboot.png"] [thumbnail="boot-systemdboot.png"]
Determining the bootloader from a running system might not be 100% accurate. The Determining the bootloader from a running system might not be 100% accurate. The
safest way is to run the following command: safest way is to run the following command: