Introduction to sysclean(8)
kapouay.eu.org
kapouay.eu.org
It's a list of things to look at, not a list of things you definitely don't need.
I tried it once a long time ago; it failed to find the sqlite3 command (back when SQLite was part of base). I spent way too much time debugging a sqlite-based script until I noticed /usr/bin/sqlite3 was still on my system.
"sysclean is a perl(1) script designed to help remove obsolete files, users and groups, between OpenBSD upgrades."
Or you could read the release notes.
I think there is a linux tool that does the same thing but I can't remember what it is. I just used mtree on my linux hosts and it worked fine.
I have some bus schedule apps that i use when i travel to other cities so Android removing them will be an inconvenience.
I much prefer that over apps having permissions "forever".
Only thing I dislike is that the Android permissions are quite coarse grained and intertwined. I still get asked for some seemingly irrelevant permission but when I check then it turns out it's just Androids permissions being weird.
On Samsung it doesn't uninstall it, it just removes permissions and then finally disables it.
What OS are you using that it uninstalls things?
I think the converse of this is. What would the web would have looked like if a commercial corporation developed it? An app store, it would be an app store.
Do you really not know already given the many precedents of this kind of thing/
This kind of automatic intelligence based on very simple statistical methods is at best annoying and at most harmful.
If I had to run such a system and had access to this functionality, my first response would be to disable and remove it.
To avoid losing data you want to keep you can also mark directories or files to be stored in the permanent storage.
Take a look at the nixos-impermanence that automates this task to you.
You'd retain the nix package storage between boots (so as to avoid having to redownload/rebuild), and setting the system up just involves setting up some symlinks. - GrahamC's blogpost discusses this in a bit more detail.
"Fresh system each run" isn't too exotic compared to image-based approaches like launching a VM on AWS, or running a Docker image.
Zapping caches shouldn’t be a problem. Log files should be kept. Local configuration shouldn’t be mixed with system/default config.
Imo, this is attacking the problem from the wrong angle.
NanoBSD does this. It's a version of FreeBSD with an immutable (read-only) base.
I've always been surprised OpenBSD hasn't created similar capabilities, given that the use case for an immutable base is great for routers / firewalls - and OpenBSD is commonly used for that.