You are not logged in.
Pages: 1
Hi, I currently have both the 'linux' and 'linux-lts' kernel packages installed. What I am trying to do is have the kernel files in /boot tagged with the kernel version number instead of the generic 'linux' name. Then during boot I am reminded of the current versions installed.
During the grub boot screen each Kernel version is listed as:-
Arch Linux, with Linux linux-lts
Arch Linux, with Linux linux-lts (fallback initramfs)
Arch Linux, with Linux linux
Arch Linux, with Linux linux (fallback initramfs)
and then post grub:-
Loading Linux linux ...
Loading initial ramdisk ...
Previously I have just renamed the kernal files replacing 'linux' with for eg. '4.8.11-1-ARCH' in the filenames and then do a rebuild of the grub config. This works but when another kernel is available under the 'linux' or 'linux-lts' package, it fails to install as it is looking for files that have been renamed.
Is there a more automated way I can configure these packages to produce the kernel files with the names I require? And which will allow future kernel updates to install?
Arch Linux, with Linux 4.4.35-1-ARCH
Arch Linux, with Linux 4.4.35-1-ARCH (fallback initramfs)
Arch Linux, with Linux 4.8.11-1-ARCH
Arch Linux, with Linux 4.8.11-1-ARCH (fallback initramfs)
and then post grub:-
Loading Linux 4.8.11-1-ARCH ...
Loading initial ramdisk ...
Thanks in advance.
Last edited by GrimBandito (2016-12-04 18:31:35)
Offline
See the mkinitcpio presets in /etc/mkinitcpio.d/
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
@Eschwartz, hi again.
Unfortunately, it looks like the kernel filenames themselves are kept generic to allow for future kernels to overwrite the existing kernel when an update occurs.
Offline
Whoops, my bad -- grub uses the vmlinuz file, not the initrd, to generate names/entries.
But you can at least use a pacman hook to create a symlink (and clean up old ones) to the vmlinuz/initramfs names you want, triggered on any update to the linux* package. (I wouldn't move files owned by pacman if it can be avoided...)
You could also wait for this bug to be resolved, though I do not anticipate that happening soon at the current rate: https://bugs.archlinux.org/task/16702
Last edited by eschwartz (2016-12-04 19:50:44)
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
Again, thx for the heads-up on the feature request. Use of symlinks is a possibility.
Offline
Pages: 1