anticapitalX
Managing multiple init systems that may accumulate kernel versions over time
How come?
I thought kernel is init agnostic.
You’re absolutely right, and thanks for the correction! The kernel is init agnostic – my phrasing was misleading there. Multiple init systems don’t cause kernel accumulation. What I should have said is that over time, as users update their systems, old kernel versions naturally accumulate regardless of the init system being used.
The main point I was trying to make is that antiX users, especially those experimenting with different init systems (runit, s6-rc, dinit, s6-66), are likely the type of users who keep their systems running for extended periods and perform regular updates. This means they’re more likely to benefit from an easy cleanup tool.
Thanks for sharing the MX Cleanup repository link! Looking at the dependencies, it appears to be a Qt6 application. Given antiX’s focus on being lightweight and the current default desktop environment, a simpler alternative might be more appropriate – perhaps:
- A CLI-based tool that could work across all antiX configurations
- A lightweight GTK or even TUI (text-based) interface
- Integration into existing antiX tools like the Control Centre
The core functionality (identifying and safely removing old kernels and unused firmware) could potentially be implemented as a shell script with a simple interface, keeping it true to antiX’s lean philosophy. This would avoid adding Qt6 dependencies which might be overkill for the antiX.
Let's accept antiX as it is
Pure and Elegant by its nature