M51 wrote:Also, claiming "works for me" doesn't help the guy with the printer problem, seeing as phenest doesn't even know if it is the same model, interface, etc.
What printer problem? That "guy" didn't specify. That "guy" just blamed systemd. How can someone give help when they don't specify what the problem is.
He wasn't really asking for help. Assuming everyone who has trouble with systemd must be wrong is stupid.
M51 wrote:That is simply 100% shitty-ass design. No reasonable developer can debate that and systemd is chock full of examples of exactly that kind of behavior. Reading the systemd changelog is some scary shit.
If systemd is that bad "100% shitty-ass design", should everyone be affected?
If you really think that, then you probably ought not to comment on technical issues. Systems are complex, and systemd depends on everything including the kitchen sink when it comes to system state so it is largely non-deterministic, like Windows.
phenest wrote: If some are affected and some are not, then perhaps it's the setup that's at fault.
The systemd developers are often guilty of thinking that there is a "right way" and a "wrong way" for a system to be set up. They are typically wrong.
phenest wrote: After all, if you not satisfied with keeping Debian as the Debian devs intended, then you're asking for trouble.
LOL, that's the stupidest and funniest thing I've heard all day. Thanks!