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.

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

Release bare shell{aa64,arm,ia32,riscv64,x64}.efi files #5

Closed
kc2zgu opened this issue Feb 20, 2024 · 3 comments
Closed

Release bare shell{aa64,arm,ia32,riscv64,x64}.efi files #5

kc2zgu opened this issue Feb 20, 2024 · 3 comments
Assignees

Comments

@kc2zgu
Copy link

kc2zgu commented Feb 20, 2024

The ISO image is useful for making bootable media on a dedicated device, but I expect many people will also want to add a shell executable to an existing system with its own EFI partition. The extra step of extracting the files from the iso image isn't too difficult, but since they need to be renamed to "shell" instead of "boot" this makes it a little more cumbersome when you don't want to clobber an existing default bootloader.

It would be nice to have the shell files available individually in the releases with the "shell" filenames.

@pbatard
Copy link
Owner

pbatard commented Feb 21, 2024

I'll see what I can do for the next release.

@pbatard pbatard self-assigned this Feb 21, 2024
@FoxieFlakey
Copy link

this would be nice too for some people who just want the .efi file precisely and dont want to deal with mounting/extracting from ISO

pbatard added a commit that referenced this issue May 29, 2024
* From edk2-stable202405
* Closes #5
pbatard added a commit that referenced this issue May 29, 2024
* From edk2-stable202405
* Closes #5
pbatard added a commit that referenced this issue May 29, 2024
* From edk2-stable202405
* Closes #5
pbatard added a commit that referenced this issue May 29, 2024
* From edk2-stable202405
* Closes #5
pbatard added a commit that referenced this issue May 29, 2024
* From edk2-stable202405
* Closes #5
pbatard added a commit that referenced this issue May 29, 2024
* From edk2-stable202405
* Closes #5
pbatard added a commit that referenced this issue May 29, 2024
* From edk2-stable202405
* Closes #5
pbatard added a commit that referenced this issue May 29, 2024
* From edk2-stable202405
* Closes #5
* This is getting old, GitHub...
pbatard added a commit that referenced this issue May 29, 2024
* From edk2-stable202405
* Closes #5
* This is getting VERY old...
pbatard added a commit that referenced this issue May 29, 2024
* From edk2-stable202405
* Closes #5
* WTF is wrong with GitHub now?!?
pbatard added a commit that referenced this issue May 29, 2024
* From edk2-stable202405
* Closes #5
* What the FUCK is wrong with GitHub Actions?!?
@pbatard
Copy link
Owner

pbatard commented May 29, 2024

And now you guys see how much one has to fight to get this bloody thing going, because when it's not the EDK2 being broken for no good reason, then it's GitHub Actions deciding to silently rate-limiting you. In the software world, even if you don't change anything, don't ever count on something that worked fine 6 months ago to work fine today...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants