systemd has been a complete, utter, unmitigated success
-
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.
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…
-
I'm in Guix Linux land right now and I miss
journald. I'm supposed to wade through all the log files in/var/logmyself?? -
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
wrote last edited by [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. -
This post did not contain any content.
I like systemd overall. The ease of use, uniform interface and nice documentation is awesome.
Though each time I try to run it on outdated hardware (say, my Thinkpad X100e, which is, well, a life choice xD) — it makes whole system much slower. IMO, openrc is not as bad, and in some ways it gives some capabiilties of systemd these days.
-
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.
There is no authority delegating responsibilities of writing tutorials for Linux. It is the responsibility of nobody and everybody. If you can't find one for your problem, write it yourself when you have figured it out.
-
This post did not contain any content.
I totally agree.
I hate to admit I didn't want anything to do with systemd because it took me forever to get somewhat familiar with some other mainstream init systems.
Then, I didn't care for a while until I developed software that had to keep running using some sort of init system. The obvious choice was whatever the default I had (systemd) and I fell in love with the convenience of systemd (templates, timers, ..). I started shipping sample systemd with the things I provide & yes, you are on your own if you use something else.
-
There is no authority delegating responsibilities of writing tutorials for Linux. It is the responsibility of nobody and everybody. If you can't find one for your problem, write it yourself when you have figured it out.
wrote last edited by [email protected]Sure, but I can't single-handedly create an entire knowledge base on doing everything with X, so it's a real and big limitation.
-
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.
In my opnion, systemd is like core-utils at this point.
It's so integrated into most things and the default so many places, that most guides assume you have it.
-
Sure, but I can't single-handedly create an entire knowledge base on doing everything with X, so it's a real and big limitation.
wrote last edited by [email protected]If you think so and that this is important, maybe you could be the one that makes it happen. Start a project and gather like-minded people. That is how Linux, FOSS and community driven efforts operate. It's useless to complain that nobody else makes the effort if you have the capabilities but can't be arsed making an attempt yourself.
-
I'm over here still using OpenRC. Mostly because I want to. Some servers I run have systemd on them. systemd is generally nice. OpenRC has finally gained the ability to run user services, which is also very nice.
dinit also has the ability to run user services, FWIW.
