Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#38222 - [grub] grub-mkconfig produce entries for every architecture
Attached to Project:
Arch Linux
Opened by Tom Yan (tom.ty89) - Saturday, 21 December 2013, 22:38 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Thursday, 01 May 2014, 19:38 GMT
Opened by Tom Yan (tom.ty89) - Saturday, 21 December 2013, 22:38 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Thursday, 01 May 2014, 19:38 GMT
|
DetailsDescription:
Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: # grub-mkconfig -o /boot/grub/grub.cfg |
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Thursday, 01 May 2014, 19:38 GMT
Reason for closing: Fixed
Additional comments about closing: grub-1:2.02.beta2-3
Thursday, 01 May 2014, 19:38 GMT
Reason for closing: Fixed
Additional comments about closing: grub-1:2.02.beta2-3
It's clearly not necessary,
I mean, how often is the architecture of your cpu changing?!?
On top of that, I couldn't see any difference in those entries.
chmod a-x /etc/grub.d/10_archlinux
There is still a x86_64-xen entry I cannot get rid of (even after `chmod a-x 20_linux_xen`) though, but at least I do not have over 40 entries (not kidding, there are three custom kernels here for testing purposes plus the stock kernel).
When I look into grub-mkconfig, "x86_64" is not in the iteration.
Though I do notice that when in actual boot, only one entry would be shown. The "testing mechanism" did work.
P.S. Is Arch not going to adopt the submenu thing? Sounds good if the fallback mode can be made an "advance option", if it can be done so.
EDIT 1: You guys can try modified 10_archlinux I uploaded to grub-git AUR pkg maintained by me.
EDIT 2: Personally I suggest everyone to manually maintain their grub.cfg file. It is simply a scaled down shell script. See https://wiki.archlinux.org/index.php/UEFI#Using_GRUB and my grub.cfg (attached) for examples. Most of the perceived complexity of GRUB comes from the grub-mkconfig generated grub.cfg . Arch does not auto overwrite /boot/grub/grub.cfg file unlike other distros, so it is safe to manually maintain grub.cfg . Syslinux does not come with any built-in config generator (neither upstream nor any Arch specific script/tool) and that works perfectly well for users. I don't think that should not work for GRUB.
EDIT 3: Although I submitted the 10_archlinux script and checked the generated grub.cfg (separate /boot, so didn't catch the ${subdir} vs ${SUBDIR} issue discussed at https://bugs.archlinux.org/task/38223), I use my manually written grub.cfg since GRUB 2.00-beta1 release and it works perfectly well for me.
I get two normal entries from 10_archlinux (normal boot and fallback) and another two from 10_linux: "Arch Linux" and a submenu "Advanced options for Arch Linux" with "Arch Linux, with Linux linux".
# chmod -x /etc/grub.d/10_linux
or
# chmod -x /etc/grub.d/10_archlinux