cannedtuna@lemmy.world to linuxmemes@lemmy.worldEnglish · 3 months agoThis guy’s a real Upstart if you ask melemmy.worldimagemessage-square178fedilinkarrow-up1808
arrow-up1808imageThis guy’s a real Upstart if you ask melemmy.worldcannedtuna@lemmy.world to linuxmemes@lemmy.worldEnglish · 3 months agomessage-square178fedilink
minus-squareViceversa@lemmy.worldlinkfedilinkarrow-up3·3 months agoNo. A database doesn’t have these specific fields by default.
minus-squareViceversa@lemmy.worldlinkfedilinkarrow-up2·edit-23 months ago Neither does systemd. They are optional. Fields are optional, but developers of systemd consciously preimplemented those fields. And in a DB that’s not the case.
minus-squareViceversa@lemmy.worldlinkfedilinkarrow-up2·3 months agoThis field appeared in LDAP for different reasons, than age control.
minus-squareViceversa@lemmy.worldlinkfedilinkarrow-up2·3 months ago systemd devs successfully rage baited you and a bunch of others Should that be their goal?
minus-squareanyhow2503@lemmy.worldlinkfedilinkarrow-up4·3 months agoIt isn’t. I’m pretty sure the dev working on that userdb field didn’t plan on getting death threats on github and said as much afterwards.
deleted by creator
No. A database doesn’t have these specific fields by default.
deleted by creator
Fields are optional, but developers of systemd consciously preimplemented those fields.
And in a DB that’s not the case.
This field appeared in LDAP for different reasons, than age control.
deleted by creator
Should that be their goal?
It isn’t. I’m pretty sure the dev working on that userdb field didn’t plan on getting death threats on github and said as much afterwards.