Description of problem: When a new Linux kernel is installed, then the pathnames /boot/uInitrd and /boot/uImage become separate copies instead of being linked to specific versions of uInitrd-* and uImage-*. This wastes space and time. Version-Release number of selected component (if applicable): grubby-8.40-4.fc26.armv7hl (/usr/sbin/new-kernel-pkg) How reproducible: every time Steps to Reproduce: 1. "dnf update" which installs a new Linux kernel 2. cd /boot; ls -li uInitrd* uImage* 3. cmp uInitrd* <latest uInitrd-version>; cmp uImge <latest uImage-version> Actual results: 541 -rw-r--r--. 1 root root 6271096 Jul 23 16:33 uImage 1595 -rw-r--r--. 1 root root 6267528 Jul 18 20:21 uImage-4.11.10-300.fc26.armv7hl 540 -rw-r--r--. 1 root root 6271096 Jul 23 16:33 uImage-4.11.11-300.fc26.armv7hl 1070 -rw-r--r--. 1 root root 6267824 Jul 12 15:27 uImage-4.11.9-300.fc26.armv7hl 542 -rw-r--r--. 1 root root 17370691 Jul 23 16:33 uInitrd 1596 -rw-r--r--. 1 root root 17369397 Jul 18 20:21 uInitrd-4.11.10-300.fc26.armv7hl 543 -rw-r--r--. 1 root root 17370691 Jul 23 16:33 uInitrd-4.11.11-300.fc26.armv7hl 1071 -rw-r--r--. 1 root root 17404913 Jul 12 15:27 uInitrd-4.11.9-300.fc26.armv7hl [root@f26xfcepi boot]# cmp uImage uImage-4.11.11-300.fc26.armv7hl [root@f26xfcepi boot]# echo $? 0 ## files compare equal [root@f26xfcepi boot]# cmp uInitrd uInitrd-4.11.11-300.fc26.armv7hl [root@f26xfcepi boot]# echo $? 0 ## files compare equal Expected results: uImage and uInitrd are links (either hardlink or symlink) to the actual specific version. In this case for hardlink: ===== # ls -li uImage uImage-4.11.11-300.fc26.armv7hl 540 -rw-r--r--. 2 root root 6271096 Jul 23 16:33 uImage 540 -rw-r--r--. 2 root root 6271096 Jul 23 16:33 uImage-4.11.11-300.fc26.armv7hl # ls -li uInitrd uInitrd-4.11.11-300.fc26.armv7hl 542 -rw-r--r--. 2 root root 17370691 Jul 23 16:33 uInitrd 542 -rw-r--r--. 2 root root 17370691 Jul 23 16:33 uInitrd-4.11.11-300.fc26.armv7hl ===== Notice the link count ' 2 ' and the same inode number listed twice (540 and 542). In this case for symlink: ===== # ls -l uImage uImage-4.11.11-300.fc26.armv7hl lrwxrwxrwx. 1 root root 31 Jul 23 16:33 uImage -> uImage-4.11.11-300.fc26.armv7hl -rw-r--r--. 1 root root 6271096 Jul 23 16:33 uImage-4.11.11-300.fc26.armv7hl # ls -li uInitrd uInitrd-4.11.11-300.fc26.armv7hl lrwxrwxrwx. 1 root root 32 Jul 23 16:33 uInitrd -> uInitrd-4.11.11-300.fc26.armv7hl -rw-r--r--. 1 root root 17370691 Jul 23 16:33 uInitrd4.11.11-300.fc26.armv7hl ===== Additional info:
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.