Last night, when I shut down the workstation for the night, it took quite a while (minutes); it was running akmod. I had done no installs and no upgrades since the previous boot (earlier in the day). I had only done dnf removes and rm commands. Why was akmod run during that shutdown?!
On 5/20/23 3:41 AM, Barry Scott wrote:
That brings the du -m down from 317 to 294.
I've noticed a bunch of "hidden" files in /boot. Here's an ls -lrta output for /boot
-----
-bash.38[boot]: ls -lrta
total 281371
drwx------. 2 root root 12288 Mar 17 2013 lost+found
-rw-r--r--. 1 root root 5897400 May 21 2015 vmlinuz-fedup
-rw-r--r--. 1 root root 42314752 Sep 22 2015 initramfs-fedup.img
-rw-r--r--. 1 root root 166 Mar 10 2016 .vmlinuz.hmac-4.4.5-300.fc23.x86_64
-rw-r--r--. 1 root root 166 Mar 16 2016 .vmlinuz.hmac-4.4.6-300.fc23.x86_64
-rw-r--r--. 1 root root 166 Mar 30 2016 .vmlinuz.hmac-4.4.6-301.fc23.x86_64
-rw-r--r--. 1 root root 166 Apr 12 2016 .vmlinuz.hmac-4.4.7-300.fc23.x86_64
-rw-r--r--. 1 root root 166 Apr 20 2016 .vmlinuz.hmac-4.4.8-300.fc23.x86_64
-rw-r--r--. 1 root root 166 May 4 2016 .vmlinuz.hmac-4.4.9-300.fc23.x86_64
-rw-r--r--. 1 root root 166 Jun 1 2016 .vmlinuz.hmac-4.5.6-200.fc23.x86_64
-rw-r--r--. 1 root root 166 Jun 8 2016 .vmlinuz.hmac-4.5.7-200.fc23.x86_64
-rw-r--r--. 1 root root 166 Jun 28 2016 .vmlinuz.hmac-4.5.7-202.fc23.x86_64
-rw-r--r--. 1 root root 166 Jul 12 2016 .vmlinuz.hmac-4.6.4-201.fc23.x86_64
-rw-r--r--. 1 root root 166 Jul 27 2016 .vmlinuz.hmac-4.6.5-200.fc23.x86_64
-rw-r--r--. 1 root root 166 Aug 10 2016 .vmlinuz.hmac-4.6.6-200.fc23.x86_64
Yep all these *.fc23.x86_64 can go.
-bash.7[boot]: ls -a .vmlinuz.hmac-4.*
.vmlinuz.hmac-4.4.5-300.fc23.x86_64 .vmlinuz.hmac-4.5.7-200.fc23.x86_64
.vmlinuz.hmac-4.4.6-300.fc23.x86_64 .vmlinuz.hmac-4.5.7-202.fc23.x86_64
.vmlinuz.hmac-4.4.6-301.fc23.x86_64 .vmlinuz.hmac-4.6.4-201.fc23.x86_64
.vmlinuz.hmac-4.4.7-300.fc23.x86_64 .vmlinuz.hmac-4.6.5-200.fc23.x86_64
.vmlinuz.hmac-4.4.8-300.fc23.x86_64 .vmlinuz.hmac-4.6.6-200.fc23.x86_64
.vmlinuz.hmac-4.4.9-300.fc23.x86_64 .vmlinuz.hmac-4.6.7-200.fc23.x86_64
.vmlinuz.hmac-4.5.6-200.fc23.x86_64
-bash.8[boot]: rm .vmlinuz.hmac-4.4.5-300.fc23.x86_64
rm: remove regular file '.vmlinuz.hmac-4.4.5-300.fc23.x86_64'? y
-bash.9[boot]: rm .vmlinuz.hmac-4.4.6-300.fc23.x86_64
rm: remove regular file '.vmlinuz.hmac-4.4.6-300.fc23.x86_64'? y
-bash.10[boot]: rm .vmlinuz.hmac-4.4.6-301.fc23.x86_64
rm: remove regular file '.vmlinuz.hmac-4.4.6-301.fc23.x86_64'? y
-bash.11[boot]: rm .vmlinuz.hmac-4.4.7-300.fc23.x86_64
rm: remove regular file '.vmlinuz.hmac-4.4.7-300.fc23.x86_64'? y
-bash.12[boot]: rm .vmlinuz.hmac-4.4.8-300.fc23.x86_64
rm: remove regular file '.vmlinuz.hmac-4.4.8-300.fc23.x86_64'? y
-bash.13[boot]: rm .vmlinuz.hmac-4.4.9-300.fc23.x86_64
rm: remove regular file '.vmlinuz.hmac-4.4.9-300.fc23.x86_64'? y
-bash.14[boot]: rm .vmlinuz.hmac-4.5.6-200.fc23.x86_64
rm: remove regular file '.vmlinuz.hmac-4.5.6-200.fc23.x86_64'? y
-bash.15[boot]: rm .vmlinuz.hmac-4.5.7-200.fc23.x86_64
rm: remove regular file '.vmlinuz.hmac-4.5.7-200.fc23.x86_64'? y
-bash.16[boot]: rm .vmlinuz.hmac-4.5.7-202.fc23.x86_64
rm: remove regular file '.vmlinuz.hmac-4.5.7-202.fc23.x86_64'? y
-bash.17[boot]: rm .vmlinuz.hmac-4.6.4-201.fc23.x86_64
rm: remove regular file '.vmlinuz.hmac-4.6.4-201.fc23.x86_64'? y
-bash.18[boot]: rm .vmlinuz.hmac-4.6.5-200.fc23.x86_64
rm: remove regular file '.vmlinuz.hmac-4.6.5-200.fc23.x86_64'? y
-bash.19[boot]: rm .vmlinuz.hmac-4.6.6-200.fc23.x86_64
rm: remove regular file '.vmlinuz.hmac-4.6.6-200.fc23.x86_64'? y
-bash.20[boot]: rm .vmlinuz.hmac-4.6.7-200.fc23.x86_64
rm: remove regular file '.vmlinuz.hmac-4.6.7-200.fc23.x86_64'? y
-bash.21[boot]: ls -a .vmlinuz.hmac-4.*
ls: cannot access '.vmlinuz.hmac-4.*': No such file or directory
-bash.22[boot]:
-rw-r--r--. 1 root root 166 Aug 17
2016 .vmlinuz.hmac-4.6.7-200.fc23.x86_64
-rw-r--r--. 1 root root 560654 Oct 21 2016 initrd-plymouth.img
That initrd-plymouth.img is not needed.
-bash.23[boot]: ls initrd-*
initrd-plymouth.img
-bash.24[boot]: rm initrd-plymouth.img
rm: remove regular file 'initrd-plymouth.img'? y
-bash.25[boot]: ls initrd-*
ls: cannot access 'initrd-*': No such file or directory
-bash.26[boot]:
drwxr-xr-x. 3 root root 1024 Oct 11 2018 loader
-rwxr-xr-x. 1 root root 10494664 Mar 19 2020 vmlinuz-0-rescue-70857e3fb05849139515e66a3fdc6b38
[... snip ...]
Thank-you, Barry.
So as was pointed out by more than one poster, some grub clean-up is needed. How do I do that?
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
