Run script after apt-get updates grub
up vote
0
down vote
favorite
I use Debian 9 on an EFI system with a custom grub image and configuration file in order to make Secure Boot work. However, whenever apt-get updates Grub my customizations get overriden.
What is the best solution for this? I do not want to prevent grub from updating, as there might be security updates. I have a script that creates my customizations. Is there a way to run that every time apt-get updates grub?
Unfortunately, I cannot find much information on this, as the Google results are just cluttered with people running into grub update error messages.
debian grub uefi bootloader secure-boot
add a comment |
up vote
0
down vote
favorite
I use Debian 9 on an EFI system with a custom grub image and configuration file in order to make Secure Boot work. However, whenever apt-get updates Grub my customizations get overriden.
What is the best solution for this? I do not want to prevent grub from updating, as there might be security updates. I have a script that creates my customizations. Is there a way to run that every time apt-get updates grub?
Unfortunately, I cannot find much information on this, as the Google results are just cluttered with people running into grub update error messages.
debian grub uefi bootloader secure-boot
Can you clarify exactly what is custom and how you create it?
– fixer1234
Nov 14 at 11:56
The grub image (grubx64.efi) is custom, I created it with grub-mkstandalone.
– Raymond Garver
Nov 15 at 4:09
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I use Debian 9 on an EFI system with a custom grub image and configuration file in order to make Secure Boot work. However, whenever apt-get updates Grub my customizations get overriden.
What is the best solution for this? I do not want to prevent grub from updating, as there might be security updates. I have a script that creates my customizations. Is there a way to run that every time apt-get updates grub?
Unfortunately, I cannot find much information on this, as the Google results are just cluttered with people running into grub update error messages.
debian grub uefi bootloader secure-boot
I use Debian 9 on an EFI system with a custom grub image and configuration file in order to make Secure Boot work. However, whenever apt-get updates Grub my customizations get overriden.
What is the best solution for this? I do not want to prevent grub from updating, as there might be security updates. I have a script that creates my customizations. Is there a way to run that every time apt-get updates grub?
Unfortunately, I cannot find much information on this, as the Google results are just cluttered with people running into grub update error messages.
debian grub uefi bootloader secure-boot
debian grub uefi bootloader secure-boot
edited Nov 15 at 4:27
asked Nov 14 at 11:33
Raymond Garver
11
11
Can you clarify exactly what is custom and how you create it?
– fixer1234
Nov 14 at 11:56
The grub image (grubx64.efi) is custom, I created it with grub-mkstandalone.
– Raymond Garver
Nov 15 at 4:09
add a comment |
Can you clarify exactly what is custom and how you create it?
– fixer1234
Nov 14 at 11:56
The grub image (grubx64.efi) is custom, I created it with grub-mkstandalone.
– Raymond Garver
Nov 15 at 4:09
Can you clarify exactly what is custom and how you create it?
– fixer1234
Nov 14 at 11:56
Can you clarify exactly what is custom and how you create it?
– fixer1234
Nov 14 at 11:56
The grub image (grubx64.efi) is custom, I created it with grub-mkstandalone.
– Raymond Garver
Nov 15 at 4:09
The grub image (grubx64.efi) is custom, I created it with grub-mkstandalone.
– Raymond Garver
Nov 15 at 4:09
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Make a custom trigger file at /var/lib/dpkg/triggers
More info: https://wiki.debian.org/DpkgTriggers
Thanks for the suggestion, but I don't understand how this would help. If I create a custom trigger it wouldn't be called by the grub package when it is installed, because it doesn't know about my trigger.
– Raymond Garver
Nov 15 at 4:16
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Make a custom trigger file at /var/lib/dpkg/triggers
More info: https://wiki.debian.org/DpkgTriggers
Thanks for the suggestion, but I don't understand how this would help. If I create a custom trigger it wouldn't be called by the grub package when it is installed, because it doesn't know about my trigger.
– Raymond Garver
Nov 15 at 4:16
add a comment |
up vote
0
down vote
Make a custom trigger file at /var/lib/dpkg/triggers
More info: https://wiki.debian.org/DpkgTriggers
Thanks for the suggestion, but I don't understand how this would help. If I create a custom trigger it wouldn't be called by the grub package when it is installed, because it doesn't know about my trigger.
– Raymond Garver
Nov 15 at 4:16
add a comment |
up vote
0
down vote
up vote
0
down vote
Make a custom trigger file at /var/lib/dpkg/triggers
More info: https://wiki.debian.org/DpkgTriggers
Make a custom trigger file at /var/lib/dpkg/triggers
More info: https://wiki.debian.org/DpkgTriggers
answered Nov 14 at 11:45
Ipor Sircer
3,41711014
3,41711014
Thanks for the suggestion, but I don't understand how this would help. If I create a custom trigger it wouldn't be called by the grub package when it is installed, because it doesn't know about my trigger.
– Raymond Garver
Nov 15 at 4:16
add a comment |
Thanks for the suggestion, but I don't understand how this would help. If I create a custom trigger it wouldn't be called by the grub package when it is installed, because it doesn't know about my trigger.
– Raymond Garver
Nov 15 at 4:16
Thanks for the suggestion, but I don't understand how this would help. If I create a custom trigger it wouldn't be called by the grub package when it is installed, because it doesn't know about my trigger.
– Raymond Garver
Nov 15 at 4:16
Thanks for the suggestion, but I don't understand how this would help. If I create a custom trigger it wouldn't be called by the grub package when it is installed, because it doesn't know about my trigger.
– Raymond Garver
Nov 15 at 4:16
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1375287%2frun-script-after-apt-get-updates-grub%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Can you clarify exactly what is custom and how you create it?
– fixer1234
Nov 14 at 11:56
The grub image (grubx64.efi) is custom, I created it with grub-mkstandalone.
– Raymond Garver
Nov 15 at 4:09