thesamesam
commented
3 years ago I stopped calling my kernel files “vmlinuz” a long time ago, because it doesn’t fit modern systems and formats. And eclean-kernel just removed ALL my kernels! If the config files hadn’t been saved somewhere else too, they’d be gone and I would have had to re-install from backups before rebooting, or been left with a broken system. :/
My layout is as follows: In /boot, there are symlinks .config -> /boot/.config-$currentVersion .config.stable -> /boot/.config-$lastVersion System.map -> /boot/System.map-$currentVersion System.map.stable -> /boot/System.map-$lastVersion kernel -> /boot/kernel-$currentVersion kernel.stable -> /boot/kernel-$lastVersion
E.g. currentVersion=5.13.10-zen1.0 lastVersion=5.13.4-zen1.0
eclean-kernel deleted every System.map- and every kernel- and then all /etc/src/linux-* directories too, including the .config files therein.
I would use --pretend in future, but it's of course unfortunate.
Looking at its, frankly, gigantic amount of source code for such a simple program, I cannot even locate where to alter what it looks for to determine which kernels are still in use. It seems to all be much too generic code. So I’m even more surprised it failed for my case. (Did it fail because of the symlinks?)
Nobody is making you use this, to be fair.
So can you please enable people to specify how they named their stuff inside /boot? Because like this, eclean-kernel is not only useless for all but “I don’t care, just do it the standard way” cases… when the whole point of Gentoo is that you care and customize… but it also can be out-performed by a 5-line bash script. (Or a Haskell one-liner, albeit in write-only code ;)
Sure, Gentoo might have a lot of use for customisation, but that doesn't mean one particular upstream is obligated to make their software do what you want. It's worth being a little bit more polite when making feature requests IMO.
jstrieter
yaaarg32
I stopped calling my kernel files “vmlinuz” a long time ago, because it doesn’t fit modern systems and formats. And eclean-kernel just removed ALL my kernels! If the config files hadn’t been saved somewhere else too, they’d be gone and I would have had to re-install from backups before rebooting, or been left with a broken system. :/
My layout is as follows: In /boot, there are symlinks .config -> /boot/.config-$currentVersion .config.stable -> /boot/.config-$lastVersion System.map -> /boot/System.map-$currentVersion System.map.stable -> /boot/System.map-$lastVersion kernel -> /boot/kernel-$currentVersion kernel.stable -> /boot/kernel-$lastVersion
E.g. currentVersion=5.13.10-zen1.0 lastVersion=5.13.4-zen1.0
eclean-kernel deleted every System.map- and every kernel- and then all /etc/src/linux-* directories too, including the .config files therein.
Looking at its, frankly, gigantic amount of source code for such a simple program, I cannot even locate where to alter what it looks for to determine which kernels are still in use. It seems to all be much too generic code. So I’m even more surprised it failed for my case. (Did it fail because of the symlinks?)
So can you please enable people to specify how they named their stuff inside /boot? Because like this, eclean-kernel is not only useless for all but “I don’t care, just do it the standard way” cases… when the whole point of Gentoo is that you care and customize… but it also can be out-performed by a 5-line bash script. (Or a Haskell one-liner, albeit in write-only code ;)