It was a long time coming, but it now happened. SystemD managed to do something that might give people pause over convenience factor. I am saying might, because while I am now actively planning ( until now I treated it as ideologically impure aspect of linux, but sufficiently useful to offset that discomfort ). DOB merge ( and how it was done ) changes that calculus by a wide margin. It is not even about DOB now. It is the full blown slippery slope with MS doing round 2 of EEE.
I don't see the problem with the systemd DOB merger, the DOB will have to be stored somewhere and systemd already has a place where user information is securely stored so they added a new field to the user database.
The alternative is not that no DOB will be stored is that it will end up stored in 20 different locations on the filesystem.
The "DiRUG reform" link leads nowhere and I can't find that particular site neither on bmj.de nor the Wayback Machine. Is that an hallucinated artifact?
This just reads like a LLM trying to come up with a conspiracy theory around systemd.
It somehow got hyper-fixated on "three" for no particular reason and seems like it decided to harpen down that fact without explaining anything around it?
23 comments
The alternative is not that no DOB will be stored is that it will end up stored in 20 different locations on the filesystem.
https://web.archive.org/web/20260403141132/https://tboteproj...
[1] https://lwn.net/SubscriberLink/1064706/ba8e449d224f5067/
Debian’s forced accepting of Systemd is finally rearing it’s ugly head.
I am glad I switched to Devuan earlier this year.
It somehow got hyper-fixated on "three" for no particular reason and seems like it decided to harpen down that fact without explaining anything around it?