You are not logged in.
Hi everyone,
I've noticed that my GRUB menu always displays:
Loading Linux linux ...
instead of something more informative like:
Loading Linux linux 6.x.x ...
I'm using Arch Linux with the default setup, and my /boot contains the usual:
/vmlinuz-linux
/initramfs-linux.img
/initramfs-linux-fallback.img
From my understanding, the GRUB menu entries are generated by /etc/grub.d/10_linux, and the name "linux" seems to be hardcoded rather than dynamically including the kernel version.
I haven’t made any manual changes to GRUB scripts. Here's the relevant part from /boot/grub/grub.cfg:
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=xxxx rw quiet splash
Is there a recommended way to make the kernel version appear in the menu, either in the echo line or the menu entry title? I'd prefer a clean solution that doesn't break with future updates.
Thanks in advance!
Last edited by billybigsword (Today 17:56:40)
Offline
have you tried looking into the 10_linux linux to see the relevant line that is producing that output? pretty sure you can change that line to add the version as well
Offline
have you tried looking into the 10_linux linux to see the relevant line that is producing that output? pretty sure you can change that line to add the version as well
but isn't that manual,i'll have to enter new kernel version myself after every kernel upgrade
Offline
as the config is static - and you're not supposed to edit any other than 40_custom anyway - and 10_linux creates the config by the filename it reads you would have to:
1) change how the kernel-image is named by mkinitcpio
2) re-run grub-mkconfig everytime mkinitcpio is run - which arch is designed to not rely on by keep a fixed filename for the kernel in the first place
tldr: can be done - but shouldn't as it introduces yet another point of failure - and given by how many prople already struggle to setup thier system in a way to not suffer from such issues I recommend just not doing it
Offline
My humble opinion: it's not a very good security practice. Have you seen systemd printing own/kernel/any versions (except for higher loglevel modes used for debugging) during the system loading? That's for a reason. It may look cool, but it adds a bit of vulnerability. For the same reason (an example), sshd never greets you with a "hello, I'm sshd version x.y, go look for CVEs and hack me".
My answer: a custom, handwritten "grub.cfg". "Loading `ArchLinux [ZEN/LTS/HRD/RT]`..." looks cool too, no? Though, I'd prefer nothing if there were no errors.
And please don't tell me that the config format will change. I use the same "grub.cfg" written about 15 years ago on all machines and only change UUIDs, copypasting and very minor editing (usually, kernel command line, specific to hardware). Never was a single problem related to it.
Offline
My humble opinion: it's not a very good security practice. Have you seen systemd printing own/kernel/any versions (except for higher loglevel modes used for debugging) during the system loading? That's for a reason. It may look cool, but it adds a bit of vulnerability. For the same reason (an example), sshd never greets you with a "hello, I'm sshd version x.y, go look for CVEs and hack me".
My answer: a custom, handwritten "grub.cfg". "Loading `ArchLinux [ZEN/LTS/HRD/RT]`..." looks cool too, no? Though, I'd prefer nothing if there were no errors.
And please don't tell me that the config format will change. I use the same "grub.cfg" written about 15 years ago on all machines and only change UUIDs, copypasting and very minor editing (usually, kernel command line, specific to hardware). Never was a single problem related to it.
Got it, thanks! Makes sense to stick with the defaults and avoid extra hassle down the line. I’ll leave it as is.
Offline