171–180 of 191 posts
Earlier quoted context omitted.
When don't we just use jack without pulse audio, most programs support it (VLC,MPV).
Firefox doesn't. They dropped all other audio systems except for pulse! Highly annoying.
[1]: https://wiki.archlinux.org/index.php/Firefox#Multimedia_play...
Earlier quoted context omitted.
Yea, sysadmin is a shrinking job field. Dev ops is eating heavily with what they used to do with config driven management of servers be it kubernetes, docker, terraform, puppet, etc.
Some one is administering the system. Whatever its title. The grip I hear from those who _do_ (and I agree with them) administer SystemD servers (note I did not say desktop here) is that when it fails, it is often very hard to debug because of too much implicit and hardly documented.
Earlier quoted context omitted.
I think Poettering deserved his fair share of the blame for the problems in Pulse Audio. However, a guy writes an over ambitious project, has a lot of problems, has problems with interfacing with users, etc, etc, etc. This is the internet! Pick a random project an Github and you'll probably find similar issues. The real problem here was Red Hat -- and it was literally the same problem with systemd. They tied it so cl…
> The real problem here was Red Hat... Agreed. This is Red Hat's mentality with a lot of it's product base. Poettering and Dan Walsh come to mind with regard to the elitist attitude in their respective corners. But just wait, this is going to get worse. Now that IBM owns them they will push this agenda even harder. The new game is controlling a majority of devs in well-known or strategic projects so the overarching e…
Don't forget Drapper
Earlier quoted context omitted.
Aren't systemd units simple text files with no hidden magic? In fact, all systemd configuration is plain text files and symbolic links. The only binary format is the journal.
> Aren't systemd units simple text files with no hidden magic? Compared to something like a shell script, systemd unit files are magic because you have to know a lot about how systemd works to figure out how your config file translates into actual behavior.
Earlier quoted context omitted.
Firefox doesn't. They dropped all other audio systems except for pulse! Highly annoying.
This is just my own experience, but sound works fine for me with just Alsa (no pulseaudio or apulse). Although even the Arch Wiki [1] says differently. [1]: https://wiki.archlinux.org/index.php/Firefox#Multimedia_play...
Earlier quoted context omitted.
>if you're doing something Debian-based - make it Devuan-based, it's pretty straightforward. It's also pretty straightforward to switch Debian systems back to sysvinit.
No, actually it isn't straightforward. There a lot of artificial dependencies that you can't break. I mean, conceptually it's not difficult, but in practice it is. See also: https://unix.stackexchange.com/a/433346/34868
You still need libsystemd0 which is a compatibility library. It's actually unfortunately named, as it isn't part of systemd itself.
I've been using sysvinit on my Debian workstations since systemd became the default. It takes me about 5 minutes to switch a new system over (admittedly I don't use Gnome or KDE). The stackexchange thread you linked is out of date and switching is getting easier. I recommend following the debian-init-diversity mailing list for further info.
Earlier quoted context omitted.
> We know from the kernel command line debug debacle they rather see the world burn down than admit they did something wrong Can you expand? I've not heard of this.
Here is an overview: https://www.phoronix.com/scan.php?page=news_item&px=mty1mza
[1] Less blog spam, less click bait, better reporting.
Earlier quoted context omitted.
As an end user, meaning a web app developer, I actually like systemd a lot. I perceive the software quality to be good enough. I've used it in production since 2014 and encountered zero bugs. It does seem to me to be vastly simpler compared to the old way of doing things. I don't really feel strongly either way. I'll be pretty sad if Debian and redhat diverge.
Simpler for simple things, which is great when it works, but more complicated for more complicated work, which is simply unacceptable when it prevents you from controlling the system. Good old bad design that matters more as you scale up. It isn't the point of systemd that is the problem, it is this particular case of horrible design.
Earlier quoted context omitted.
> Why would I want to start working on software I don't use or need? Why do systemd advocates always insist that every implementation must include the features they think are important? If you don't care about multi-user session management, sure, but considering practically every window manager/DE relied on consolekit and now logind to provide that functionality, I find it hard to believe it's not desirable by a larg…
Not many users care about multi-user session management. An even tinier number of users care about multi-seat session management (which is when you have mutiple users on the same machine at the same time, with their own screen and input devices). Pretty much every desktop Linux user cares about being able to click options like "shutdown", "restart" and "suspend" in the user interface and have them work. As it current…
Everything I know about systemd is bad. When I want to write a script that runs on startup, I expect that I can just put (or link) it in some directory where the scripts are that get started on startup. Or that there is one main script that calls all scripts that are intended to be startet on startup. I do not want to write a "service" that has some "only run once and then discard" flag or whatever. When I want to lo…