Package Details: grub-hook 2.0-5

Git Clone URL: (read-only, click to copy)
Package Base: grub-hook
Description: Pacman hook to update GRUB after a kernel update
Upstream URL:
Licenses: GPL
Submitter: runnytu
Maintainer: runnytu
Last Packager: runnytu
Votes: 19
Popularity: 0.26
First Submitted: 2013-08-25 22:38
Last Updated: 2016-08-16 19:42

Latest Comments

runnytu commented on 2016-11-20 12:53

@QuartzDragon, it seems to haven't installed the bash package (base), in terminal execute /bin/sh, if fails, install or reinstall the bash package, if not please execute sudo /bin/sh -c 'grub-mkconfig -o /boot/grub/grub.cfg', and attach the output errors.

QuartzDragon commented on 2016-11-20 04:27

After kernel upgrades, grub-hook fails with:

(3/3) Updating GRUB Config
call to execv failed (No such file or directory)
error: command failed to execute correctly

Not sure what the issue is?

runical commented on 2016-08-16 23:27

All right, the first one is a good reason. I hadn't thought of that. As for the second, I swear it worked, but you are correct. On further testing, my solution didn't work. Sorry about that :S

And glad I could help make the hook a bit more elegant :)

runnytu commented on 2016-08-16 20:06

Bump to new version 2.0-5.


First, it's necessary if you want to update the number of kernel version in config file of grub in every kernel upgrade, this is the reason for create this hook, if you don't want it, you can comment the upgrade line during the build process of package.

Second, Ok but your config doesn't work, because the file target refers to a file in the package you're installing/upgrading/removing, not in a file in your local directories, my new config concerning to file vmlinuz works Ok.

Third, Ok i include the command in the hook file instead of sh file.

runical commented on 2016-08-12 08:40

I can't help but notice that the current hook is quite unwieldy. How about using something like [1]?

Let me explain the though process.

First off, you do not need to update the grub config with every update to the kernel. The new kernel image has the same name as the old kernel image, so the grub entries do not change.

Second, listing all of the possible kernels is inefficient (and unwieldy, it requires you to know all possible kernel packages), so we would like to find something that all kernel updates have in common. That is that a new kernel image is generated on the /boot partition. So we trigger the hook on any change to the image files on /boot.

And lastly, you do not need a separate since you can include the command in the hook itself.

I tested the hook on my system and it works, so maybe you'd like it as well.


runnytu commented on 2016-03-10 22:12

Bump to new version 2.0-3.