Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Change 9a5e71044bb7262e makes it impossible to parse loader path vs. args to loader #269

Open
noahfriedman opened this issue Sep 3, 2024 · 1 comment
Open

Change 9a5e71044bb7262e makes it impossible to parse loader path vs. args to loader #269

noahfriedman opened this issue Sep 3, 2024 · 1 comment

Comments

@noahfriedman
Copy link

The original log entry says

File device paths: don't print "File(" or ")"

Well, now efibootmgr shows

Boot0000* Windows Boot Manager HD(2,GPT,3c55a653-7f3b-4f30-b402-37b0bb907eb3,0x40800,0x82000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000...

Instead of

Boot0000* Windows Boot Manager HD(2,GPT,3c55a653-7f3b-4f30-b402-37b0bb907eb3,0x40800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000...

That is not an improvement, because now I can't reliably tell where the filename ends and the parameters begin. Would you please revert this change. It wasn't hurting anything before and now it is.
JohnFlowerful added a commit to JohnFlowerful/buildkernel that referenced this issue Oct 5, 2024
@JohnFlowerful
fix efivar breakage
663e9ca 
rhboot/efivar@9a5e710
rhboot/efivar#269
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@noahfriedman and others