cannedtuna@lemmy.world to linuxmemes@lemmy.worldEnglish · 2 months agoThis guy’s a real Upstart if you ask melemmy.worldimagemessage-square178linkfedilinkarrow-up1819arrow-down122
arrow-up1797arrow-down1imageThis guy’s a real Upstart if you ask melemmy.worldcannedtuna@lemmy.world to linuxmemes@lemmy.worldEnglish · 2 months agomessage-square178linkfedilink
minus-squaremabeledo@lemmy.worlddeleted by creatorlinkfedilinkarrow-up5arrow-down2·edit-27 hours agodeleted by creator
minus-squareViceversa@lemmy.worldlinkfedilinkarrow-up2arrow-down3·2 months agoThis field appeared in LDAP for different reasons, than age control.
minus-squaremabeledo@lemmy.worlddeleted by creatorlinkfedilinkarrow-up3arrow-down1·edit-27 hours agodeleted by creator
minus-squareViceversa@lemmy.worldlinkfedilinkarrow-up2arrow-down3·2 months ago systemd devs successfully rage baited you and a bunch of others Should that be their goal?
minus-squareanyhow2503@lemmy.worldlinkfedilinkarrow-up4arrow-down1·2 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.
minus-squareViceversa@lemmy.worldlinkfedilinkarrow-up2arrow-down4·2 months ago Neither does systemd. They are optional. Fields are optional, but developers of systemd consciously implemented those fields. And in a DB that’s not the case.
deleted by creator
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.
Fields are optional, but developers of systemd consciously implemented those fields.
And in a DB that’s not the case.