The fight for child safety has reached the core of free operating systems.
A new controversy has erupted around systemd , and the reason seems surprising even for the Linux world. A field for the user's date of birth was added to the project's code. The developers explained the decision as a result of legal requirements regarding age verification and future parental control mechanisms.
This is pull request #40954 for systemd . The change adds a new field, birthDate, touserdb JSON records , allowing for storing the date of birth. According to the description, the function is needed to verify age in accordance with recent laws passed in California, Colorado, and Brazil, among others. Only users with root privileges will be able to change the field's contents.
The new feature was introduced after the release of systemd 260, so unless the code is rolled back, the feature will be included in systemd 261. One argument in favor of adding it is related to the draft parental control system for Flatpak . In practice, the debate is no longer just about a new option in systemd, but about a broader shift: age checks are gradually beginning to reach the operating system level.
The Linux community reacted nervously. The GrapheneOS project , which develops Android without Google services and prioritizes privacy, publicly stated that it will maintain the system's availability without requiring personal data, documents, or an account. If local regulations block sales of GrapheneOS devices , the team is prepared to tolerate such a scenario. Android is not associated with systemd, but the tone of the statement is indicative of the mood surrounding the new requirements.
Tension is also palpable among Linux distributions. postmarketOS switched to systemd back in 2024, and given the current changes, this move no longer seems uncontroversial. In the Arch ecosystem, frustration has also become noticeable. One of the Garuda Linux maintainers explicitly wrote on the project's forum that the distribution will not implement age verification measures, as there are no laws in Garuda's jurisdictions requiring developers to implement such a mechanism.
The authors of the statement from Garuda added an even more blunt message: part of the community, they say, is shocked by the way the debate is unfolding in the Linux world, with distribution developers literally being pressured for their attempts to comply with local laws. The Garuda team believes that pressure should be directed not at package and build maintainers, but at politicians, lobbyists, and large companies that promote such regulations.
The controversy also raised the issue of Meta's possible influence . The article cites the findings of the TBOTE Project , which links the promotion of age verification laws and the App Store Accountability Act to the corporation's lobbying activities. The project's researchers claim to have directly traced over $25 million, and estimate Meta's total expenditure on similar pressure over the past year could have reached $2 billion. Multimillion-dollar lobbying expenditures in Europe are also specifically mentioned. The article does not provide an independent judicial review of these estimates, but the story itself has already begun to influence rhetoric within the Linux community.
In the US , the Digital Childhood Alliance plays a significant role in promoting age restrictions . According to sources, the coalition was assembled by over 50 conservative organizations, and in the summer of 2025, Bloomberg reported that Meta provided funding to the organization. For a young organization, the DCA's influence on the debate around child safety and age verification has been very noticeable.
Against this backdrop, distributions without systemd may emerge as winners. The article cites Artix Linux and other projects that deliberately forgo the most popular Linux service manager as potential beneficiaries. Adding a single field to userdb is no longer a minor technical tweak. For some in the community, the story has become a debate about privacy, developer authority, and the limits of government pressure on free operating systems.
A new controversy has erupted around systemd , and the reason seems surprising even for the Linux world. A field for the user's date of birth was added to the project's code. The developers explained the decision as a result of legal requirements regarding age verification and future parental control mechanisms.
This is pull request #40954 for systemd . The change adds a new field, birthDate, touserdb JSON records , allowing for storing the date of birth. According to the description, the function is needed to verify age in accordance with recent laws passed in California, Colorado, and Brazil, among others. Only users with root privileges will be able to change the field's contents.
The new feature was introduced after the release of systemd 260, so unless the code is rolled back, the feature will be included in systemd 261. One argument in favor of adding it is related to the draft parental control system for Flatpak . In practice, the debate is no longer just about a new option in systemd, but about a broader shift: age checks are gradually beginning to reach the operating system level.
The Linux community reacted nervously. The GrapheneOS project , which develops Android without Google services and prioritizes privacy, publicly stated that it will maintain the system's availability without requiring personal data, documents, or an account. If local regulations block sales of GrapheneOS devices , the team is prepared to tolerate such a scenario. Android is not associated with systemd, but the tone of the statement is indicative of the mood surrounding the new requirements.
Tension is also palpable among Linux distributions. postmarketOS switched to systemd back in 2024, and given the current changes, this move no longer seems uncontroversial. In the Arch ecosystem, frustration has also become noticeable. One of the Garuda Linux maintainers explicitly wrote on the project's forum that the distribution will not implement age verification measures, as there are no laws in Garuda's jurisdictions requiring developers to implement such a mechanism.
The authors of the statement from Garuda added an even more blunt message: part of the community, they say, is shocked by the way the debate is unfolding in the Linux world, with distribution developers literally being pressured for their attempts to comply with local laws. The Garuda team believes that pressure should be directed not at package and build maintainers, but at politicians, lobbyists, and large companies that promote such regulations.
The controversy also raised the issue of Meta's possible influence . The article cites the findings of the TBOTE Project , which links the promotion of age verification laws and the App Store Accountability Act to the corporation's lobbying activities. The project's researchers claim to have directly traced over $25 million, and estimate Meta's total expenditure on similar pressure over the past year could have reached $2 billion. Multimillion-dollar lobbying expenditures in Europe are also specifically mentioned. The article does not provide an independent judicial review of these estimates, but the story itself has already begun to influence rhetoric within the Linux community.
In the US , the Digital Childhood Alliance plays a significant role in promoting age restrictions . According to sources, the coalition was assembled by over 50 conservative organizations, and in the summer of 2025, Bloomberg reported that Meta provided funding to the organization. For a young organization, the DCA's influence on the debate around child safety and age verification has been very noticeable.
Against this backdrop, distributions without systemd may emerge as winners. The article cites Artix Linux and other projects that deliberately forgo the most popular Linux service manager as potential beneficiaries. Adding a single field to userdb is no longer a minor technical tweak. For some in the community, the story has become a debate about privacy, developer authority, and the limits of government pressure on free operating systems.
