Performance enhancing drugs. Athletes at most levels of competition are at least training on them, so let's be honest, eh?

I'm afraid it's become clear that Lennart has a lot of very serious personal and possibly mental issues that mean he just isn't suited to working with others. The progress of systemd will mean that eventually there will be a serious conflict with the kernel developers, amongst others.

Exactly. I'm getting tired of hearing that things will continue to work in the way they always have when this issue comes up. They won't.

It's exactly the kind of misdirection and smoke-and-mirrors you get from the systemd crew every time a serious shortcoming is brought up. It's a pretty serious mental issue. Oh, and yes, having to deal with a corrupted Windows Event Viewer is exactly like this is going to be. Something you should just not have to deal with.

Oh, and I can already search my text logs in a 'fine grained' and searchable manner thank you very fecking much. I know that might come as a big fricking shock, but a lot of people are.

No, it doesn't. Stop repeating this crap of how I am 'free' to use syslog every time this issue comes up.

It's a Lennart Poettering meltdown and accurately exemplifies the problems people have with him, those around him and why people are justifiably concerned about the software he is being allowed to write. This guy simply has 'issues'.

If he believes he's going to take on Linus and the kernel developers, stamp his feet and take over the Linux landscape he's going to lose badly.

Questioning someone's ability to write software or telling everyone to write a patch knowing full well they either can't, or it won't be accepted if they do, is right up Lennart's alley. Is that you Lennart?

You sound surprised. However, they all still have longstanding problems which their developers have a long history of passing off.

....and I'll qualify the Windows Event Viewer comparison by saying at least I'm reasonably confident Microsoft will fix an issue or I'll find a workaround.

This will be coming, and the Linux developers will have to chip in because systemd is already compromising their ability to actually do their work. I know you, and others like you, make that kind of comment because you believe it will never happen. It will, because it will have to.

I mean, some of us are legally required to keep logs. Look at that piece of meaningless crap Lennart posts as a final response to this.

Posted as AC? Check. Comment blames crazy user? Check. Is that you Lennart?

Considering that it's posted under AC I'd say that's affirmative.

It's the opinion of anyone who has ever interacted with him, and the crew he has around him. The kernel developers at the moment are just trying to avoid that lot. Soon they won't be able to. Passive aggressive, corrosive, unresponsive to any problem that looks serious and when they do respond it's a problem somewhere else or it's waved away with a completely non-sensical response.

Part of the same crew and culture I'm afraid.

Yer, Wait until we get bugs like that within systemd. "Nothing we need to fix". "This is something the kernel needs to fix". etc. etc. That's been the consistent pattern.