SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Pulse is a pain, but at least it's a user-land pain, but a kernel-land pain.
I don't like it, and it conflicts with TiMidity (which actually is a TiMidity's fault, but still), and it's the app that gets broken most often when updating -current.
But I have to admit, nowadays it is much better than before, and it does make configuring Bluetooth audio easier.
The only feasible option I see to get rid of Pulse is to write a thin translation layer from the most used pulse api to, say, JACK's. But even if "feasible", that's still hell of a lot of work.
Basically, what Lennart is doing is completely against UNIX-way, and it's also not as well tested as you'd want a Mac-way software to be, but it's not possible to resist his endeavours by just ignoring him. Either an alternative should be found, or he's gonna be the only Linux desktop guru out there.
As demonstrated by Debian BSD and Debian Hurd, a GNU operating system like the ones which we call usually "Linux" can run quite well with other kernels than Mr. Torvalds' Linux.
However, I see no one crying in this forum about Mr. Volkerding's choice to use the Linux Kernel for his operating system and how this choice limits their own freedom to run the Hurd Kernel instead.
Just like some believes JACK do the things better than PulseAudio, others believes that a FreeBSD Kernel is more stable and safe than a Linux Kernel.
How nobody asks about supporting the BSD kernels, let's do the same about PulseAudio and let's us to respect the Mr. Volkerding's choice. He chosen the PulseAudio over JACK, then that case is closed.
Last edited by ZhaoLin1457; 05-20-2019 at 12:53 PM.
Patrick just can't ship every software on earth in Slackware, and PA has a wider target, that's all. But jack1 and jack2 are available from SBo. They do not compete with PA, just address different use cases. And you can use both jack and PA, as you can use both PA and the ALSA userspace programs. That just needs a proper configuration.
Patrick just can't ship every software on earth in Slackware, and PA has a wider target, that's all. But jack1 and jack2 are available from SBo. They do not compete with PA, just address different use cases. And you can use both jack and PA, as you can use both PA and the ALSA userspace programs. That just needs a proper configuration.
However, if you listen to the pulse-haters, they swear that JACK do all that PulseAudio do, but better.
Could be a confusion from their part?
Last edited by LuckyCyborg; 05-21-2019 at 07:22 AM.
Rationale: wqy-zenhei is already included in -current, and these two fonts are very close in their origin, and essentially compliment each other. Their relationship is NOT like 'serif — sans-serif', but close to it. ZenHei looks blurry on big sizes, and but MicroHei is a bit too loose to be displayed where lots of text needs to be jammed into a small space.
while we're on the subject of mkinitrd: '-u' hasn't had a purpose for a while as UDEV is required and 'on' by default. Might as well remove it (or change it to "provided for backward compatibility") while you're in there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.