Any of you guys use Slackware?

I use slackware, basically the good part, aside from stability, is that most of the settings are in text files so it's easy to configure everything. The bad part is that you kind of have to configure everything. And I mean stuff that other distros would have by default, like making it run X by default instead of just the terminal

>>58574813
Would you say the community is still active?

>>58575156
I'm interested in this as well. I've always wanted to give Slackware a shot and I think it might just be the ideal distro for me, but I might not be that much interested if development/community is pretty much stale or dead.

Entire point of slackware is you don't have software, so it's like BSD, and you keep repeating "Everything you need is on the CD" and let the decades pass by

Slackware a shit

>>58574709
Pulseaudio.
You will end up compiling progeams you want that are not in the distro.

>>58575808
SlackBuilds is basically the equivalent of the AUR, and lots of packages are maintained and kept there.

>>58575808
You mean it has it by default?

>>58576317
yes, i believe for bluetooth audio which alsa doesnt support.

>>58576663
You can have bluetooth audio with ALSA and older bluez version (and that actually gives you better synchronization - pulseaudio a shit)
But bluez' recent version dropped ALSA support and requires pulseaudio now

>>58575988
yeah but slack has no package manager that does both slack repos an slackbuilds, so you end up having to use two and switch back and forth constantly. it gets old real fast when you're setting up the system

>>58576724
slackpkg and sbopkg
build scripts but useful nonetheless

>>58576724
op of >>58576724
sorry didnt read close enough

but most people use yaourt and pacman (pacaur is better but most use yaourt) on arch