Make automatic remove of obsolete kernels the default instead of opt-in
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- linux, python
- Domain
- operating-systems
Research direction
The issue names no files or tests. Start by locating the automatic maintenance preference and the existing obsolete-kernel cleanup behavior in the Update Manager, then determine how the default and retention count are configured. Done means automatic cleanup is enabled by default, retains three old kernels, and remains user-configurable.
Written by the indexing model from the issue text.
Description
I have a suggestion on kernel that are not deleted.
After a Mint update from Mint 17 to 20, I've found that I have many old kernel on my system. I've never deleted them and didn't know that I have to delete them manually. It can consume quite a bit of disk space (gigabytes), if there are many. I'm aware that a fresh install of Mint is advised rather then upgrading and I would probably not have that many on my system with a fresh install. Still, I assume one can accumulate quite a number of kernel over the lifetime of a Mint LTS version in 5 years and in the case there is an update, even more (17 in my case).
I would suggest that old kernels get deleted regularly by the system and by default, with the following option
Edit > Preferences > Automation tab > automatic maintenance
I think that the majority of Mint users will profit if this options is turned on by default. I would say it would be good to keep 3 old kernels. It's saver then only one but it's till not too much disk space that is wasted.
I assume that there may be a few people who would rater like to delete kernels manually and for those it should be possible to turn off that auto feature.
- Dominant language
- Python
- Stars
- 425
- Forks
- 190
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxmint/mintupdate
-
BUG
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
linuxmint/mintupdate#1089 ·
-
BUG
Difficulty 1/5 Under an hour Newbie friendliness 88/100
linuxmint/mintupdate#1062 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
linuxmint/mintupdate#1041 · 1 comment ·
-
FEATURE REQUEST
Difficulty 1/5 Under an hour Newbie friendliness 65/100
linuxmint/mintupdate#910 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
linuxmint/mintupdate#903 ·
All issues in linuxmint/mintupdate
Similar issues
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100