because whilst systemd-initd is the part that everyone is generally aware of, that’s linked to systemd-logind so that processes can be started as different users… process init, session management, and user management are intertwined
they don’t have to be for sure - sysv init proves that - but in modern linux, they are and that comes with a load of benefits
because theyre being pragmatic… laws are starting to be introduced around the globe for parental controls - whatever that means in each jurisdiction. given that, there needs to be options available to people wanting to, or required to comply with said laws… the best place to do that is in a user record, as an optional field… extensible user records, in modern linux, are stored in systemd
it needs it in a similar manner to how it needs location, email, real name, etc: it doesn’t functionally need it, but it’s a place to store the metadata associated with a user such that other applications can use it
Honestly idk why people are so mad at the wrong people. They are doing this for concern of following the laws that are being passed in many jurisdictions. Some of which required “operating systems” to store date of birth that apps can access. What that means and what even is an OS is heavily up to debate.
Either way people need to call their lawmakers and be mad at those passing these laws.
Enlighten us then. Why would an operating system management tool need to know the age of its user?
because whilst systemd-initd is the part that everyone is generally aware of, that’s linked to systemd-logind so that processes can be started as different users… process init, session management, and user management are intertwined
they don’t have to be for sure - sysv init proves that - but in modern linux, they are and that comes with a load of benefits
https://deepwiki.com/systemd/systemd/6-user-and-session-management
https://systemd.io/USER_RECORD/
I get that systemd also manages user data. I still fail to see how it needs that DoB.
because theyre being pragmatic… laws are starting to be introduced around the globe for parental controls - whatever that means in each jurisdiction. given that, there needs to be options available to people wanting to, or required to comply with said laws… the best place to do that is in a user record, as an optional field… extensible user records, in modern linux, are stored in systemd
it needs it in a similar manner to how it needs location, email, real name, etc: it doesn’t functionally need it, but it’s a place to store the metadata associated with a user such that other applications can use it
Honestly idk why people are so mad at the wrong people. They are doing this for concern of following the laws that are being passed in many jurisdictions. Some of which required “operating systems” to store date of birth that apps can access. What that means and what even is an OS is heavily up to debate.
Either way people need to call their lawmakers and be mad at those passing these laws.
Why would it need to know your real name?
It doesn’t. It just needs some name to display on the welcome screen and doesn’t know what else to call it.
Welcome screen? Systemd doesn’t have a welcome screen. And even if it did, why would it need anything other than username?
Why does it need a field for location and email?
Because back in the 60s and 70s, people wanted to know whose print jobs were running and where the printed documents should be delivered.
So over 40 years before systemd was initially released?
I’m hearing a whole lot of mental gymnastics from both of y’all to explain away the “okay” fields while demonizing the (optional) “evil” fields.
What are you getting at me for? You asked a question and I answered.
I don’t care about any new gecos fields because they’re optional.
<.< Your answer makes no sense.