Toy distros are what I need as a home user.

1 members found this post helpful.

It's great that you Bluetooth users are happy, but as a non-Bluetooth user it's unthinkable to have PA on my system (surely I'm entitled to an opinion), so I will find another OS where programs like these will never be installed by default. Thanks for Slackware, it was the best Linux distribution while it lasted.

1 members found this post helpful.

I was hoping you were still rendered speechless.

"Cheers"

15 members found this post helpful.

So you are a 'trend maker' ? Because you are not interested anymore (which is respectable), you think the 'absolute value' have (will be) changed ?

Of course you are. You're not entitled to force that opinion onto others, though, least of all onto one of the people who voluntarily devotes a significant amount of his spare time to developing Slackware.

If it's unthinkable to you to install PulseAudio, don't install it. There have been countless threads about PulseAudio in this forum since it was added to -current, and most of them (this one in particular) have discussed how you can disable it if you don't want to use it.

Reading some posts here does miracles


Cheers

I still would like to know why you think PA is an unthinkable addition to Slackware. Yes it was created by our pal Lennart. It was a buggy piece of shit at the time. Now it is being developed by other people, and can be considered stable & useable.
The decision was made that adding it to Slackware and thus making the broken Bluetooth sound work again, was a better option than ditching BLuetooth support and leaving lots of people out in the cold.
This is about pragmatism as well as philosophy, and the line connecting the two is very thin. I really wish you could adopt the viewpoint that Slackware is and remains a solid stable and independent distro, making changes only when needed and not on a whim.
Using a distro inherently means trusting its developers to do the right thing. Please have a little bit more faith in Pat and the Slackware team.

If you are still hell-bent on your refusal of the addition of PulseAudio then I am sorry that you came to that decision but I respect you for it. I hope you find a distro that suits your needs and fits better with your viewpoint.

13 members found this post helpful.

This has become a rather heated discussion.
I'll add my two cents.
I chose slackware to create a personal audio studio for a few reasons.
http://sourceforge.net/projects/slac...?source=navbar
One of the first is the absence of pulseaudio. It doesn't coexist well with JACK.
I haven't delved into trying to connect bluetooth audio into JACK. That would be interesting.
Personally I would like to see/have a backend with gstreamer connected to JACK, but that's besides the point. I also did have to add PAM. It was necessary for some type of advanced POSIX memory locking/control (which I found very little to no information on) for an audio app (I believe it was ardour). The last was a desire to keep processes to a minimum that would interfere and cause JACK latencies. I like PAM. I don't believe it to be a security issue until third party addons/modules are used. I'm torn about PulseA. I do use BTaudio, but there has to be a better solution.

Why not just disable PA? It's trivial, and has already been described (quick edits to two config files). That seems like a better option than migrating to an inferior distribution (a lot less effort, too).

1 members found this post helpful.

Well, PulseAudio was fairly easy to add to Slackware (from SBO for example), and to use it only when needed, instead of shipping it by default. I did it when bluez got bumped. I don't need Bluetooth. I was just curious and didn't even think we would see it in Slackware. And because it emulates esound and virtually every player in Slackware has esound support there was no need to recompile any of them.

Lets hope that one day someone of the team gets a new toy, like a fingerprint scanner for example. That same day PAM will be shipped with Slackware because it will be a better option than leaving all those fingerprint scanner users out in the cold.


Cheers

4 members found this post helpful.

Wow, its like I'm in 4chan!

2 members found this post helpful.

I do hope you don't actually believe what you are saying there.
What rworkman said in an earlier post in this thread also strongly hints (at least in my opinion) that support for new stuff normally isn't just stuffed in because someone (even in the core team) think it's a novel idea at the time.
Alien Bob says the same thing.
My impression is that core team members do (as many, many other Slackware users) have some software on the side that they maintain packages of themselves. Packages stuff that sometimes (many times) will never go into Slackware proper. Even in the long run.
Also; I find that a fingerprint scanner is a somewhat bad example. It shouldn't be too big a stretch to imagine that there are quite a few more users of sound (and thus sound over bluetooth) than there are users that *need* fingerprint scanners to work.
That said, I do see the point you are trying to make, but it also seems your trust in the integrity of PatV and the core Slackware maintainers may be somewhat lacking.


--
KarlMag

5 members found this post helpful.

My laptop already has one. It's never worked and here's a list of all the times that's bothered me:





















...

9 members found this post helpful.

of course it does not work in Slackware, unsolved since nearly 10 years http://www.linuxquestions.org/questi...ut-pam-595124/

also http://www.slackwiki.com/ThinkPad_X6...erprint_Reader
and the central authentication scenarios ....

lets declare it to a feature that without changing big parts of the system by the user things like this are not possible.

consistency is a wonderful thing

When did you replace your T400?