On Sun, 9 Dec 2018 06:44:52 +0530, Amish via arch-general wrote: >KISS (Keep it simple) implies that if you can use a tool >(grub-mkconfig in this case) then use it. No, it does not. The Arch Linux kernel names don't change. They are always something like e.g. vmlinuz-linux, never something like e.g. vmlinuz-4.4.0-140-whatsoever. When I used GRUB 2, I always edited grub.cfg directly by myself. However, I migrated to syslinux. Btw. on my multi-boot machine are Ubuntu flavours installed. Even if I remove the boot-loader from an Ubuntu flavour install, it likely gets reinstalled after a release upgrade. I workaround the useless call of the grub auto-thingy by dpkg-divert, since the bootloader is only needed by one install. [root@archlinux moonstudio]# systemd-nspawn -q dpkg-divert --list | grep "local diversion of" local diversion of /usr/sbin/grub-mkconfig to /usr/sbin/grub-mkconfig.real local diversion of /usr/sbin/update-grub to /usr/sbin/update-grub.real The generated grub.cfg contains all kinds of needless crap. It takes way to long to generate grub.cfg after each upgrade of each installed distro, simply editing grub.cfg or adding two links (e.g. vmlinuz-lowlatency -> vmlinuz-4.4.0-140-lowlatency) is less time consuming. By default the grub auto-thingy fails and editing the configs for this auto-thingy is rocket science, not KISS.
