From 9a827f9464c914aeeb532d21cd9fc82ddafe94fe Mon Sep 17 00:00:00 2001 From: Neel Chotai Date: Sat, 27 Feb 2021 20:03:09 +0000 Subject: [PATCH] efibootmgr: move setup instructions to README.voidlinux --- srcpkgs/efibootmgr/INSTALL.msg | 21 ++------------------- srcpkgs/efibootmgr/files/README.voidlinux | 19 +++++++++++++++++++ srcpkgs/efibootmgr/template | 4 ++-- 3 files changed, 23 insertions(+), 21 deletions(-) create mode 100644 srcpkgs/efibootmgr/files/README.voidlinux diff --git a/srcpkgs/efibootmgr/INSTALL.msg b/srcpkgs/efibootmgr/INSTALL.msg index 2b27d196f3e..3c1f4796dba 100644 --- a/srcpkgs/efibootmgr/INSTALL.msg +++ b/srcpkgs/efibootmgr/INSTALL.msg @@ -1,19 +1,2 @@ -efibootmgr can automatically generate EFI boot entries to -directly boot the kernel after every kernel update or installation. -Enable this by editing /etc/default/efibootmgr-kernel-hook. - -The efi variables need to be accessible in order for this to work, so -add this line to your fstab and reboot or mount manually: - efivarfs /sys/firmware/efi/efivars efivarfs 0 0 ------------------------------------------------------------------------ -Kernel cmd options can be configured in /etc/default/efibootmgr-kernel-hook, -but you always have to reconfigure the kernel: - - $ xbps-reconfigure -f linux4.8 - (or any other kernel version) - -This is also required after the first installation of this package. ------------------------------------------------------------------------ -The bootorder itself is not changed, so your previous boot loader will -stay enabled until you can edit the order in your firmware interface or -using "efibootmgr -o " +See /usr/share/doc/efibootmgr/README.voidlinux for instructions on +using efibootmgr to automatically manage EFI boot entries. diff --git a/srcpkgs/efibootmgr/files/README.voidlinux b/srcpkgs/efibootmgr/files/README.voidlinux new file mode 100644 index 00000000000..98844fd85a6 --- /dev/null +++ b/srcpkgs/efibootmgr/files/README.voidlinux @@ -0,0 +1,19 @@ +efibootmgr can automatically generate EFI boot entries to +directly boot the kernel after every kernel update or installation. +Enable this by editing /etc/default/efibootmgr-kernel-hook. + +The EFI variables need to be accessible in order for this to work, so +add this line to your fstab and reboot or mount manually: + efivarfs /sys/firmware/efi/efivars efivarfs defaults 0 0 +----------------------------------------------------------------------- +Kernel cmd options can be configured in /etc/default/efibootmgr-kernel-hook, +but you always have to reconfigure the kernel: + + $ xbps-reconfigure -f linux4.8 + (or any other kernel version) + +This is also required after the first installation of this package. +----------------------------------------------------------------------- +The bootorder itself is not changed, so your previous boot loader will +stay enabled until you can edit the order in your firmware interface or +using "efibootmgr -o " diff --git a/srcpkgs/efibootmgr/template b/srcpkgs/efibootmgr/template index e9b1bff036a..ca131efb1b1 100644 --- a/srcpkgs/efibootmgr/template +++ b/srcpkgs/efibootmgr/template @@ -1,7 +1,7 @@ # Template file for 'efibootmgr' pkgname=efibootmgr version=17 -revision=3 +revision=4 hostmakedepends="pkg-config" makedepends="libefivar-devel popt-devel" short_desc="Tool to modify UEFI Firmware Boot Manager Variables" @@ -39,7 +39,7 @@ do_install() { } post_install() { - vlicense COPYING + vdoc ${FILESDIR}/README.voidlinux vmkdir etc/ vinstall "${FILESDIR}/efibootmgr-kernel-hook.confd" 644 etc/default efibootmgr-kernel-hook vinstall ${FILESDIR}/kernel.d/efibootmgr.post-install 744 \