aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGlenn Washburn <development@efficientek.com>2022-05-11 21:56:21 -0500
committerDaniel Kiper <daniel.kiper@oracle.com>2022-05-24 14:49:19 +0200
commita56a622ae71f0b590b9aaa13866b0df7847c37cc (patch)
treedccbff9fea57ee724be052af5fb37e5d8c804deb
parentaf7c86674c052c39361cc216a81992768e007302 (diff)
downloadgrub-a56a622ae71f0b590b9aaa13866b0df7847c37cc.tar.gz
docs: Markup loader commands with @command tag
Also, add period to terminate sentence. Signed-off-by: Glenn Washburn <development@efficientek.com> Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>
-rw-r--r--docs/grub.texi7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/grub.texi b/docs/grub.texi
index 773933216..5ff4660c6 100644
--- a/docs/grub.texi
+++ b/docs/grub.texi
@@ -1005,13 +1005,14 @@ kopenbsd payload this is disabled by default. Aditionally behaviour of
initial ramdisk depends on command line options. Several distributors provide
the image for this purpose or it's integrated in their standard ramdisk and
activated by special option. Consult your kernel and distribution manual for
-more details. Other loaders like appleloader, chainloader (BIOS, EFI, coreboot),
-freedos, ntldr and plan9 provide no possibility of loading initial ramdisk and
+more details. Other loaders like @command{appleloader}, @command{chainloader}
+(BIOS, EFI, coreboot), @command{freedos}, @command{ntldr}, @command{plan9}
+and @command{truecrypt} provide no possibility of loading initial ramdisk and
as far as author is aware the payloads in question don't support either initial
ramdisk or discovering loopback boot in other way and as such not bootable this
way. Please consider alternative boot methods like copying all files
from the image to actual partition. Consult your OS documentation for
-more details
+more details.
@node LVM cache booting
@section Booting from LVM cache logical volume