systemd has been a complete, utter, unmitigated success

[email protected]

This post did not contain any content.

[email protected]

I'm in Guix Linux land right now and I miss journald. I'm supposed to wade through all the log files in /var/log myself??

[email protected]

I totally agree. I used to hate systemd for breaking the traditional Unix philosophy, but the reality is that a tight init and service-tracking integration tool really was required. I work with and appreciate systemd every day now. It certainly didn't make things simplier and easier to debug, but it goes a long way towards making a Linux system predictable and consistent.

Poettering can go fuck himself though - and for PulseAudio too. I suspect half of the hate systemd attracted over the years was really because of this idiot.

[email protected]

I still have no idea how to find the right record to read but at least I can run a journalctl --follow till my crash happens

[email protected]

predictable and consistent.

Or none of those.

Oh. My NIC didn't 'start' because systemd and network manager are fighting again? Neet.

[email protected]

I’m supposed to wade through all the log files in /var/log myself??

You configured your logging. You could have made them all one file.

[email protected]

Uh, sorry. I don't follow. Is there a way to tell all programs to write to one file in Guix?

[email protected]

systemd is easy to work with, other init systems introduce kinks, I rather break philosophy than deal with that shit

[email protected]

Is it really breaking it? As far as I'm aware, it's more like gnu. It has components and you can select what you use (here meaning distros and packagers).

People mistake this for a monolith because it's all named systemd-thing. Integration, like you said, was and is needed. But what if all those separate utilities and services are actually disconnected and speak some protocol different to pipe? Does it make it less unixy?

And poettering is an absolute good guy here. Pulseaudio wasn't perfect, but did it improve things compared to what was there before? Sure it did. Even now, pulesaudio protocol is used within pipewire and it works just fine.

Perfect is the enemy of good. And while all these tools might not be perfect, they are the best in the Linux world.

[email protected]

poettering is an absolute good guy here

Agreed. But he's also an abrasive know-it-all. A modicum of social skills and respect goes a long way towards making others accept your pet projects.

pulesaudio protocol is used within pipewire and it works just fine.

I wasn't talking about the protocol, I was talking about the implementation: PulseAudio is a crashy, unstable POS. I can't count the number of hours this turd made me waste, until PipeWire came along.

[email protected]

I always assumed that Poettering is an arse to people because of the hate he got for systemd. I imagine it's hard to see the best in people when there's a crowd of haters everywhere you go. Though I have no idea what he was like beforehand.

[email protected]

People are idiots.

Poettering got death threats for systemd.

[email protected]

Pulseaudio was introduced in 2004. How come it took almost 20y for it to be replaced if it was that bad?

Implementation, being what it is, improved the situation compared to alsa and other things before it. Again, while not perfect it made things better for everyone.

It's funny that this is a thing attributed to poettering as bad since things before were way worse... why not throw Sticks and stones at those people?

I really don't get it.

And all of these things are optional. The fact that distro people and companies select them is because they solve real world problems.

[email protected]

Yea, symlink all the files to the same master log file. ... /s

[email protected]

I don't know why they are downvoting you, it's true. I'm dealing with this kind of problem currently.. sometimes the boot lasts forever to the point that I have to use AltGr+SysRq commands to force kill everything.. other times it simply boots as normal. It's not consistent at all.

At least before with the old init it was relatively simple to dig into the scripts and make changes to them.. I feel now with systemd it's a lot more opaque and harder to deal with. I wouldn't even know how to approach the problem, systemd-analyze blame does not help, since the times I actually get to boot look normal. But I do believe it must have to do with the mountpoints because often they are what takes the longest.
Any advice on what should I do would be welcome.

Also, I have a separate Bazzite install in my living room TV, and while that one does not get locked, sometimes NetworkManager simply is not running after boot... I got fed up to the point that I wrote a workaround by creating a rc.local script to have it run, so I can have it available reliably when the system starts (that fixed it.. though some cifs mountpoints often do not get mounted.. so I'm considering adding the mount command to the same rc.local script too....).

[email protected]

I feel that generally, when the issue is that the person is an arse, then the complaints are often not about the software. You might see people campaigning to boicot the software out of spite, but they won't give you a technical reason, other than them not wanting the creator to get any credit for it.

When the complaints are about discrepancies in the way the software is designed (like it was with systemd), there's no reason to expect the person to be an arse. Though him not being an arse does not make the criticism about his software invalid... in the same way as him being an arse would not have made the software technically worthless. Don't fall for the ad-hominem.

[email protected]

I'd say the main bad part of systemd is how it's used and now expected everywhere.

If you search for some Linux guides or install something complicated or whatnot, they always expect you to have systemd. Otherwise, you're on your own figuring how things work on your system.

This shouldn't really happen. Otherwise, yes, it's great, it integrates neatly, and is least pain to use.

[email protected]

Agreed. But he’s also an abrasive know-it-all. A modicum of social skills and respect goes a long way towards making others accept your pet projects.

This isn't what I get when reading bug reports he interacts in. Yeah, sometimes he asks if something can't be done another way – but he seems also very open to new ideas. I rather think that this opinion of him is very selective, there are cases where he comes off as smug, but I never got the impression this is the majority of cases.

I wasn’t talking about the protocol, I was talking about the implementation: PulseAudio is a crashy, unstable POS. I can’t count the number of hours this turd made me waste, until PipeWire came along.

PipeWire for audio couldn't exist nowadays without PulseAudio though, in fact it was originally created as "PulseAudio for Video"; Pulse exposed a lot of bugs in the lower levels of the Linux audio stack. And I do agree that PipeWire is better than PulseAudio. But it's important to see it in the context of the time it was created in, and Linux audio back then was certainly different. OSS was actually something a significant amount of people used…

[email protected]

Try https://lnav.org/

[email protected]

If that approach is enough then tail -f /var/log/* could work too with multiple files, it'll "follow" all the files and display only new lines.

agnos.is Forums

systemd has been a complete, utter, unmitigated success