User avatar
Alba 🌸 v_pat @mildsunrise@tech.lgbt
7mo
for reasons that may or may not be related to work, I'm implementing efibootmgr in pure python
terminal screenshot of my test.py script running... it shows BootCurrent, BootNext, BootOrder and the defined BootOptions. output is colorized and hexdumps are shown for the optional data section of boot options, if present
1
0
0
0
User avatar
Alba 🌸 v_pat @mildsunrise@tech.lgbt
7mo
also the UEFI spec is so obnoxiously overengineered...
2
0
0
0
User avatar
celeste_hearts_lesbianceleste_hearts_transceleste_hearts_demisexual flori_ava_star:~cursor_blinking @star@amazonawaws.com
7mo
@mildsunrise Would you like to elaborate? I'd be interested :3
1
0
0
0
User avatar
Alba 🌸 v_pat @mildsunrise@tech.lgbt
7mo
@star I'm probably not the best person to opine on this, since I'm not that familiar with it, but what i see is that it
has lots and lots of features
which can be combined in an exploding number of ways
only some combinations are supported/implemented
some functionality is hinted at but not concretely described
the spec falls short of creating a full contract and I've ended up having to look at tianocore frequently

efibootmgr for example only implements a very specific (even if common) kind of boot entry: one with exactly two nodes, a hard drive node followed by a file path node. see the device path protocol for the full list of node types that can appear in the path to your EFI image. keep in mind this protocol is used for all kinds of paths, not just paths to booted EFI images but also to describe the default console device for example
:noted:1
0
0
1
1