>"(...) with some trepidation, we began investigating adding PulseAudio to Slackware. After several iterations here refining the foundation packages and recompiling and tweaking other packages to use PulseAudio, it's working well."
So Slackware is cucked now, given that PulseAudio will obviously depend on systemd in the near future, and Slackware will be forced to adopt it to sustain a working audio subsystem.
Yea right. So they now adopted PulseAudio so something else can work (instead of finding another way out), and you're implying that later someone will go all the way back and get rid of PulseAudio (which other stuff became dependent on in the meantime) to avoid systemd?
It's not for $RANDOM_ANON to "/thread" other people's threads.
Because apparently after some change somewhere Bluetooth audio stopped working, which could be resolved by a newer version of the Bluetooth component, which stopped supporting ALSA and requires PulseAudio now.
>people being surprised
slackware's MO is adding a ton upon another ton of software for full installations. no shit as Systemd becomes common place it'd work its way into slackware.
>I don't miss a distro that doesn't even check dependencies and rely on obsecure build scripts to install things.
sbopkg mitigates most of that. all you have to do is check the readme and add dependencies to queue to install all in order.
There's no way Pottery isn't an alphabet soup agent plant.
Making such vulnerable, botnet-ridden malicious code on purpose with no apparent reason other than muh baselevel coordination should be enough of a hint.
meh. slack aims for stability. if the vast majority of the programs it comes with become dependent on sysd, its going to eventually pick it up.
imo sysd is the future, for better or worse. too many users are indifferent, and its integration with Debian and Arch pretty much cemented that it'll stay
But Linux as such becoming fully and wholly dependent on a thing such as systemd (which, btw, keeps devouring more OS components as we speak) isn't really the Linux we once knew anymore, it's something different. It's a bit like comparing good old Windows 2000 with the mess we've arrived at that is Windows 10 (the analogy may be stretched and limited, but I guess you get it).
no, it has a package manager.
it has a decent guide on creating your own alpine packages as well if you need to. recently more daily driver type of programs have been added to the repository.
>Category: Firewall, Server, Security, Telephony
>Alpine Linux is a community developed operating system designed for x86 routers, firewalls, VPNs, VoIP boxes and servers. It was designed with security in mind; it has proactive security features like PaX and SSP that prevent security holes in the software to be exploited. The C library used is musl and the base tools are all in BusyBox. Those are normally found in embedded systems and are smaller than the tools found in GNU/Linux systems.
>"there's nothing wrong with either PulseAudio or systemd"
I wish this was true, and I guess hardly anyone would have their resevations if it indeed was the case. What you say is like arguing how Windows 10 supposedly is great just because it was released and is the way to go for every Windows user no matter the glaring problems with it.
No, I meant to quote you. You appear to have argued that changes which happen should be necessarily followed regardless of their possible (or even glaring) problems and deficiencies.
>all you have to do is check the readme and add dependencies to queue to install all in order
And why isn't this done automatically? If I wanted to do computations manually I would use an abacus.
Lots of "autistic faggots making up memes" it seems?
>complaining about pulseaudio when practically every audio API thats been developed for linux within the past 2 decades has ended up being a POS.
The problem at this point is less PulseAudio itself than the fact that once it becomes completely dependent on systemd it will most likely become impossible for Slackware to keep avoiding the latter.
I'm getting tired of poettering's shitty software. Today I issued usermod -l <newuser> <olduser> to rename my account, and then changed the home directory. I chown'ed -R name:group my home directory, and now pulseaudio keeps shitting the bed. Only ONE program can generate audio now, and unloading the module-something-cork does not fix the problem.
Simple solution to avoid pottering, we all move to *BSD. Pick one, any one.
>delete your pulseaudio dotfile?
Been there done that.
>Have your tried turning it off and on again?
Starting pulseaudio with pulseaudio -v is not consistent either. If more than one song has played, pulseaudio will be busy and mpv, for instance, won't be able to output any sound for a while.
SystemD is the result of forcing GNU devs to think for themselves since they can no longer clone good software frome ATT and Sun. You're better off learning OpenBSD and switching as soon as you can.
>because of my outdated UNIX philosophy
The UNIX philosophy follows the basis for engineering in general. It's much easier to debug, secure and maintain small, concise, clean pieces of software that WORK, as opposed to monolithic, overly complex ones.
Systemd IS a massive security vulnerability waiting to happen.
Once you pare down the problems, ignoring for a moment the bad blob design that tries to do everything, the buggy code, the antagonistic developers, there's the following:
tl;dr THE FUCKING THING DOESN'T EVEN DO INIT PROPERLY
Making it an obtuse, opaque and partially downright broken clusterfuck similar to modern Windows is not the solution.
>none of you can actually articulate why
Reasons or links to such were given many times (such as here >>52481482). It's you and your ilk who keep repeating how supposedly there's nothing wrong with it and nothing beyond that.