this post was submitted on 25 Mar 2026
168 points (87.2% liked)
Technology
83098 readers
2743 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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
If they're pragmatic, they'd wait to confirm the requirement. Currently, they're more on the proactively bootlicking side than pragmatic.
Location is needed to set timezone. As for real name and email, they're both tied to history.
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.
https://en.wikipedia.org/wiki/Gecos_field#Format
https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/4/html/introduction_to_system_administration/s2-acctsgrps-files#ftn.idm140081194521120
My point was that adding another optional field asking for DOB is just as “scary” as the optional fields asking for real name and location. It doesn’t need them, which was what the other user was alluding to.