by jiml8 » Jun 1st, '21, 22:23
Yeah. I could.
When I write something, I am always careful to retain backward compatibility. Should that prove unfeasible, I always build in a migration path and handle the migration.
Systemd has broken my system over, and over, and over. I am very reluctant to update these days because I may wind up with a broken system and be forced to retrace all my steps to see what got broken this time.
For instance, I was not aware that sysctl.conf was no longer being used, until I read it in this thread. Why is sysctl.conf now being ignored? No good reason. Just "we no longer want to do it this way".
Well, that change turns out to be at the root of a number of problems that have been annoying me lately...things I had fixed before with sysctl settings had become unfixed and I had not yet taken the time to chase them down. I had, in fact, not recognized that my sysctl settings had been removed. This includes my complaints about kcompactd. Once I reset my sysctl settings, THAT problem disappeared and my system swap behavior settled down.
Linux with systemd is actually now a lot worse than Windows with respect to updates. At least, Windows fixes the configuration of the system being updated when it changes how things are done. And, mostly, that works. But not linux.
Last edited by
doktor5000 on Jun 1st, '21, 23:04, edited 1 time in total.
Reason: removed fullquote