-
Notifications
You must be signed in to change notification settings - Fork 246
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
Add 2 more 32MiB blocks to efi_img_sz (issue 2552) #2562
Conversation
Add 2 more 32MiB blocks to be on the safe side against inexplicaple failures like "cp: error writing '/tmp/rear.XXX/tmp/efi_virt/./EFI/BOOT/elilo.conf': No space left on device" where the above calculated $efi_img_sz is a bit too small in practice cf. #2552
Typo fix in comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Use simpler arithmetic evaluation code.
Always nice to see how one could make code even simpler: RFC 1925 item 12 (excerpt):
https://tools.ietf.org/html/rfc1925 I wish you all a relaxed and recovering weekend! |
I would like to wait until next week so that @abbbi has a chance to test it, |
Interestingly
at least for me with GNU bash version 4.4.23 (on openSUSE Leap 15.2). |
@abbbi |
Type: Bug Fix / Enhancement
Impact: Normal
Reference to related issue (URL):
./EFI/BOOT/grub.cfg': No space left on device #2552
How was this pull request tested?
Not at all tested by me (I don't use EFI).
Brief description of the changes in this pull request:
Add 2 more 32MiB blocks to be on the safe side against inexplicaple failures like
"cp: error writing '/tmp/rear.XXX/tmp/efi_virt/./EFI/BOOT/elilo.conf': No space left on device"
where the above calculated $efi_img_sz is a bit too small in practice.