Re:Systemd needs official documentation on best practices
by tharne on Friday November 08, 2019 @03:26PM
(#21486347)
of course systemd is so bloated and monolithic that it's hard to find and identify bugs and flaws in the first place, so it's win-win for them.
Re:Systemd needs official documentation on best practices
by Xylakant on Friday November 08, 2019 @04:12PM
(#21486824)
Isn’t it shadow-utils that came up with that rule? And rhel/centos patching that out? https://gist.github.com/bloerwald/a482791395114fa82636e2ab20...
Re:Systemd needs official documentation on best practices
by catalogia on Friday November 08, 2019 @04:22PM
(#21486950)
It was never a rule, only a quirk a few other tools had. The kernel has always permitted these usernames; it is plainly systemd's responsibility to not shit the bed when it encounters such a username.
Re:Systemd needs official documentation on best practices
by kevin_b_er on Friday November 08, 2019 @04:30PM
(#21487023)
The example is because SystemD rejects POSIX as a standard. Whenever Pottering decides something is better, POSIX is tossed out the window.
Re:Systemd needs official documentation on best practices
by catalogia on Friday November 08, 2019 @04:48PM
(#21487195)
It's deeper than that. Rejection of POSIX is the reason SystemD is Linux only; Pottering rejects POSIX compatibility and gives the finger to anything other than Linux. But in this case SystemD failed to even adhere to the [non]spec of "what Linux supports."
Prime example: the "best practice" of not letting usernames start with numbers is invented on the spot by a SystemD dev to cover his ass: https://github.com/systemd/systemd/issues/6237#issuecomment-...