From 4051815230f443ac4b052a4cf0f55a951e3f88c8 Mon Sep 17 00:00:00 2001 From: Jeremy Kerr Date: Fri, 13 Dec 2013 16:02:12 +0800 Subject: ui/ncurses: Add help to boot editor screen Signed-off-by: Jeremy Kerr --- ui/ncurses/nc-boot-editor-help.c | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 ui/ncurses/nc-boot-editor-help.c (limited to 'ui/ncurses/nc-boot-editor-help.c') diff --git a/ui/ncurses/nc-boot-editor-help.c b/ui/ncurses/nc-boot-editor-help.c new file mode 100644 index 0000000..3f0c7fb --- /dev/null +++ b/ui/ncurses/nc-boot-editor-help.c @@ -0,0 +1,24 @@ +const char *boot_editor_help_text = "\ +This screen allows you to edit or create boot options.\n\ +\n\ +Device: This is a list of block devices available on the system. Select \ +the device which contains your boot resources (kernel, initrd and device \ +tree), or \"Specify paths/URLs manually\" to use full URLs to the boot \ +resources.\n\ +\n\ +Kernel: enter the path to the kernel to boot. This field is mandatory. \ +This should be a kernel image that the kexec utility can handle. Generally, \ +this will be a 'vmlinux'-type image.\n\ +Example: /boot/vmlinux\n\ +\n\ +Initrd: enter the path to the initial RAM disk image. This is optional.\n\ +Example: /boot/initrd.img\n\ +\n\ +Device tree: enter the path to the device tree blob file (.dtb). \ +This is optional; if not specified, and your platform currently provides \ +a device tree, the current one will be used.\n\ +Example: /boot/device-tree.dtb\n\ +\n\ +Boot arguments: enter the kernel command-line arguments. This is optional.\n\ +Example: root=/dev/sda1 console=hvc0\n\ +\n"; -- cgit v1.2.1