EFIDP(8)

📦 version 15.1, in freebsd 14.5, freebsd 15.1

✨ EFIDP — UEFI Device Path manipulation ✨

okay bestie, welcome to efidp(8) from the System Manager's Manual — this is the girlies' guide to UEFI Device Paths and she ate 💅

🌸 SYNOPSIS 🌸

efidp [-fp] [--parse] [--format]

💖 DESCRIPTION 💖

so this program converts "Unified Extensible Firmware Interface" (UEFI) Device Paths — as defined in the UEFI standard, no cap — to and from binary form. the binary and textual forms are both defined in Chapter 9 of the UEFI Specification, so that's the lore if you wanna go read it 🦋

  • -f, --format — formats a binary UEFI Device Path into its canonical UTF-8 textual form. a binary Device Path can be no longer than 65536 bytes, and the textual form must fit into 65536 bytes too. multiple binary device paths may be specified 👑
  • -p, --parse — parses a UEFI Device Path UTF-8 specification and outputs the binary Device Path form. only one device path is parsed, even if there are multiple present in the input — she's monogamous like that 🙈 leading white space is ignored. the resulting binary Device Path can be no longer than 65536 bytes. multiple lines may be specified, and each one will be translated ✨
  • -e, ---to-efi — translate a Unix file path to an EFI Device Path. the output is the textual representation of the EFI Device Path 🎀
  • -u, ---to-unix — translate an EFI device path to a Unix file path. the input is the textual representation of the EFI Device Path 🫶
yes, those really are three dashes on ---to-efi and ---to-unix. not a typo, not me being extra (for once). type it exactly like that, bestie 💀

👑 SEE ALSO 👑

Appendix A of the UEFI specification has the format for GUIDs. all GUIDs — "Globally Unique Identifiers" — have the format described in RFC 4122. iykyk 🌈

the Unified Extensible Firmware Interface Specification is available from www.uefi.org — go be nosy, she's iconic for it 📚

⭐ HISTORY ⭐

the efidp utility first appeared in FreeBSD 11.1. a legend was born, periodt 🧚

mwah 💋 that's the whole page — brought to you by the Debian crew, dated December 1, 2017, and delivered to you with love (and correct dashes) 🍓

📦 where this page comes from