Wols Lists wrote: > On 01/07/2022 00:21, Dale wrote: >> When I upgrade to a new kernel, I run for a month or so and then >> manually clean out /boot, that would include kernel, init thingy, >> System.map and config files. >> >> Seeing this reminds me it might be a good time to look into updating, >> even tho I might not reboot for a while yet. > > When I update, I wait until I'm happy the new one seems okay, and then > I just leave the most recent one and the one before. > > That said, I need to upgrade, and I need to see if my random hangs are > fixed (there's apparently a bug in the Ryzen 3000, and I'm guessing > that's what I'm hitting). > > Cheers, > Wol > >
After my previous reply, I updated to a newer kernel. It's in /boot but it may be months before I reboot. Anyway, I currently have four kernels in /boot. My current running kernel and two backup kernels plus the new untested one. Whenever I get around to rebooting and the new kernel works fine, I'll remove the oldest one including sources etc. I try to keep at least two backup kernels. One reason I do that, the init thingy. I admit dracut is working well for me but given the history I have with those thingys, I want extra protection. The odds of three boot options going bad are pretty slim and if it did happen, I likely have a serious hard drive problem anyway, file system at the very least. Either way, I have a lot to worry about. Maybe one of the suggestions mentioned here will help the OP. It seems he is letting the updater do the install or something and the kernel is a fast moving target. One has to have some way, automated or manual, to clean up the unneeded bits. I doubt most anyone makes their /boot to large anyway. Usually 300 or 400MBs is enough. Dale :-) :-)
