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.
Not everyone has a $100 sound card or even a dedicated sound card, there are a lot of people who use the onboard audio on their motherboard.
Excuse me? I have said repeatedly that I understand what value PA has to some and even recommended in this thread and others that they use, or at least try it. I don't hate PA or at least what it tries to accomplish. I just hate that it is a hard dependency forcing those of us who find it a major penalty to be stuck with it and jumping through hoops to work with it or without it. I've chosen and been using Slackware just shy of 20 years exactly because Pat V has stated and lived by the directive of not assuming use case. I completely understand why he had to submit when Bluetooth required it and I applaud him for providing a way out when that dependency ceased.
I'm completely comfortable with those who prefer PA. Why are some apparently uncomfortable with those like me who are not? It's all about Freedom and Liberty for ALL, right?
I've seen lots of discussion about fixing the sound on hazel's computer. Granted, the fix that worked was to remove /etc/asound.conf.
That advice was the wrong way to think about system administration.
The system is up and running, but parts of it aren't working right (or at least, the way you want). As you go poking around, bear in mind that you might poke something the wrong way, and everything comes crashing down.
The #1 priority of a sysadmin is "don't do anything you can't undo". I didn't see where anyone suggested hazel keep a copy of /etc/asound.conf.
The simplest, safest approach is to move said file into a user-home directory, e.g.
Code:
# mv /etc/asound.conf ~hazel/
Followed by testing, testing, and testing again, maybe even with a system reboot mixed in for good measure. If any stage of testing shows that this action was not a good idea, at least hazel still has the file! It's a simple matter of returning the file to its original location (and reboot, if needed), to get the system back to a semi-working state.
Don't delete anything until you're absolutely sure you don't need it.
Some here know hazel is a keyboard veteran from the dawn of computing and surely knows how to eliminate a file's action without painting herself into any corners. Your advice is excellent but I'm betting she knows that well. Also, a simple "upgradepkg --install-new" fpr PA should reinstall "/etc/asound.conf" since AFAIK the reason eliminating it's action works is because PA replaces it with one directing action to PA instead of ALSA.
Additionally, since Current and apparently the next full release will have both options, PA or Pure-ALSA, including scripts to enable either, the point will become a non-issue and provides at the very least a guide if not an actual example and script to switch from one to the other.
Excuse me? I have said repeatedly that I understand what value PA has to some and even recommended in this thread and others that they use, or at least try it. I don't hate PA or at least what it tries to accomplish. I just hate that it is a hard dependency forcing those of us who find it a major penalty to be stuck with it and jumping through hoops to work with it or without it. I've chosen and been using Slackware just shy of 20 years exactly because Pat V has stated and lived by the directive of not assuming use case. I completely understand why he had to submit when Bluetooth required it and I applaud him for providing a way out when that dependency ceased.
I'm completely comfortable with those who prefer PA. Why are some apparently uncomfortable with those like me who are not? It's all about Freedom and Liberty for ALL, right?
I have no idea what you are talking about, I removed pulseaudio from my system the day it was added to current.
I've seen lots of discussion about fixing the sound on hazel's computer. Granted, the fix that worked was to remove /etc/asound.conf.
That advice was the wrong way to think about system administration.
I didn't see where anyone suggested hazel keep a copy of /etc/asound.conf.
The simplest, safest approach is to move said file into a user-home directory, e.g.
Code:
# mv /etc/asound.conf ~hazel/
You'll laugh! That's precisely what I did, except that I stored the backup in /root. Storing a thing like that in $HOME isn't safe, because after a few weeks, you think "what's that doing there?" and delete it. Remember I'm old and my memory isn't what it once was. Anything stored in root's home is clearly important and worth keeping.
In fact I never just delete system config files. I always copy them to root first. And if I edit a system file, I make a copy of the original with a .orig suffix. Belt and braces.
Excuse me? I have said repeatedly that I understand what value PA has to some and even recommended in this thread and others that they use, or at least try it.
Some?
Probably is better to say "almost all" Slackware users.
I do not believe that in the wild are more than few music creators who uses Slackware, like you do.
And I believe that even you do not believe on those stories, otherwise you haven't feel the need to abuse the word "audiophile" which by excellence describe the educated listeners, but not also the music creators.
An audiophile is a person who is enthusiastic about high-fidelity sound reproduction.
Please note the words "sound reproduction" which are on exactly other side of the chain starting with "music production"
And please, please do not argument with whatever present or past poll from this forum, because I believe that those who use Slackware are in a substantially much higher number than those around 100 who usually vote here polls.
Only myself I know personally over 30 Slackware users of various knowledge levels, and no one of them posted here, at least until now.
Please take no offense, I have all respect for the music creators, as I have broken The Great Firewall firstly to grab new Eminem songs, but you are really few, we we are really many.
Last edited by ZhaoLin1457; 05-28-2019 at 02:13 PM.
Okay, point taken re: hazel, but I'm also concerned that someone might come here from a web search, a neophyte who might not grasp the implications of a command.
I expect soon I will need to bite the bullet and go to something from RME similar to what is shown in the following linked video.
Just so you know: RME USB interfaces, in class compliant mode, do not have full input monitoring capabilities. If you need real time monitoring for recording, it works in a way, but hard panned to either the left or the right channel.
I have no idea what you are talking about, I removed pulseaudio from my system the day it was added to current.
Although I have a few test partitions and one of them has Slackware Current on it (for which I totally agree) my main is a mildly modified 14.2 Multilib. I can't use Current as a Work platform, or at least don't choose to. That requires a fixed full release.
ZhaoLin1457. Regarding your post #66 about the percentage of Slackware users who for whatever reason prefer to not run PA (and there are quite a few posts of those here) I have to ask, "So what? Why rule out anyone if it is not required to do so?"
I think my point still stands that PA unnecessarily tried to coerce it's use and preyed on convenience to make it so, somewhat in opposition to the philosophy of Slackware. A bit of evidence supporting that concept is Pat Vs decision to produce an alternative as soon as the Bluetooth stranglehold was removed.
Just for fun.....
Quote:
Originally Posted by Eminem
They say music can alter moods and talk to you
Well can it load a gun up for you, and cock it too?
Well if it can, then the next time you assault a dude
Just tell the judge it was my fault and I'll get sued
Just a precision: asound.conf is shipped in the alsa-lib package in Slackware version 14.2.
Thanks. I wasn't certain since all I know is default install of 14.2 has PA replacing lines in asound.conf and didn't know if it overwrote with it's own version or just "sed" it
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
