fix paths on direct boot script
vmlinux and initramfs files path on direct boot script are not the same as on the other scripts on the page, I think it's better to change the direct boot script as follow
# mount -t efivarfs efivarfs /sys/firmware/efi/efivars # ignore if already mounted # efibootmgr -d /dev/sdX -p Y -c -L "Arch Linux" -l '\EFI\arch\vmlinuz-linux' -u "root=/dev/sda2 rw initrd=/EFI/arch/initramfs-linux.img"
Can UUIDs be used as the --disk and --part parameters in efibootmgr?
(My first ever Arch Wiki discussion comment!)
I like the idea of using UUIDs wherever possible. I got EFISTUB booting working last night with this command (and so I updated the wiki page to add the syntax for reference):
# efibootmgr --disk /dev/sdX --part Y --create --gpt --label "Arch Linux" --loader /vmlinuz-linux --unicode 'root=UUID=00000000-0000-0000-0000-000000000000 rw initrd=\initramfs-linux.img'
But can UUIDs be used on the --disk and --part parameters? If so, what's the syntax? I'd like to update the new UUID example I just added using only UUIDs if this is possible.
- I haven't tried that, but I think it can not be used. For one thing, one will not have to specify both a disk and a part, as per the
, if a UUID is usable. For the second thing, the description of the is
- Tool to modify UEFI Firmware Boot Manager Variables
- My understanding is that to be able to do what you want, the efibootmgr command will have to translate the UUID that you will sepcify on the command line to terms that the UEFI Firmware can work with. Rethinking, one should look at the efibootmgr code to see if it can do that. If it can not, maybe it might be added.
- Regid (talk) 06:51, 15 December 2018 (UTC)
Add example for block device identifier
Multiple people added this now already. Why does it keep getting removed?
User:Lahwaacz instead of reverting the change with "there is no such thing as a full format", it would be more helpful if you would reword it.