Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Can you get sound as root? If it's just users that can't hear sound, it's because of the file permissions of the audio devices in /dev. The "proper" way to set it up is adding a group called audio or sound etc.. and adding users to that group. Here is what you may want to try. First find out what the last gid(group id) is in /etc/group by doing this; cat group
Note the last number. Now do the following:
groupadd -g 102 (make this number the one AFTER the one you noted in the group file) audio <---Or whatever you want to call the group.
You'll want to add a user to that group. If you want joe to be in that group then you could modify his userstatus by doing this;
usermod -G audio joe <---Adds joe to audio
then cd /dev and change the ownership of the audio files to audio by doing this;
chown -v root.audio audio audio1 dsp dsp1 sequencer sequencer2
then change the permissions of said files like this;
chmod -v 464 audio audio1 dsp dsp1 sequencer sequencer2
That's it, now joe can hear sound properly. The 464 is debateable. That sets the permissions to r--rw-r-- thereby only users in the group will hear sound, you can mess with those. If I made any goofs yuh'all, please correct me.
Well, I should've thought about it sooner, but you are going to want to load the appropriate sound module in the /etc/rc.d/rc.modules file. I'm not in Slack at the moment but if you edit that file, scroll down to sound support and you should see the soundblaster support. Just uncomment the module by taking away the hash '#' reboot and then first see if root has sound. After that we can worry about getting the users sound if there is any problem.
i'm running slack8 on my thinkpad, and before i installed the 2.4.17 kernel on my system, i had to use alsa modules for my soundcard, so to load them at boot time i added the following lines to my /etc/rc.d/rc.local file:
yeah, in slackware only root has permissions to access your soundcard. you'll either wanna create a new group for your sound devices or change the permissions on the hardware itself. refer to this post for some more info: