-
Notifications
You must be signed in to change notification settings - Fork 101
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- use -lefivar and -lefiboot to make device paths and load options. Signed-off-by: Peter Jones <pjones@redhat.com>
- Loading branch information
Showing
3 changed files
with
15 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,13 @@ | ||
For 0.9: | ||
|
||
- support for setting hotkeys | ||
- support for driver variables, not just boot variables. | ||
- support for arbitrary device paths with -c (including guid parsing) | ||
- audit for missing unparse_*_path() types. | ||
- verify/debug NVME code | ||
- maintain a list of known GUIDs and print {vendor} instead of the full GUID | ||
- accept these for arbitrary paths as well. | ||
- these are done in libefivar, but efibootmgr still needs some work on it | ||
- MS-DOS style extended partitions | ||
- lots more network stuff | ||
- IPv6 with various discovery methods | ||
- IPv4 w/o dhcp | ||
- make sure FCoE works | ||
- iscsi | ||
- make sure nvme works |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters