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.
every time i run the kde window system i recieve this message when it first starts up. i would like to have sound but have thusfar been running without it. i have looked everywhere on the net for solutions to this problem but none have been much assistance except for teaching me many things i did not know but did not need to know. i have slackware 8.1 installed and can provide any other information anyone needs to help me with this problem.
Originally posted by Strike This is half right and half evil. Never chmod 666 /dev/dsp. Its permissions should be 660, and it should be owned by root.audio. Then, anyone in the audio group has read/write access to it.
I'm no uber security nut, but would certainly like to know of any holes I too follow this scheme, but only because "I was told to" previously. But could you expand on the need to secure your dsp device from world reading/writing? Thanks for any info
Originally posted by MasterC I'm no uber security nut, but would certainly like to know of any holes I too follow this scheme, but only because "I was told to" previously. But could you expand on the need to secure your dsp device from world reading/writing? Thanks for any info
Well it's not as severe a security risk as many permissions problems can be, it's more of a "prevent a source of potential annoyances" than anything else. If you chmod 666 /dev/dsp and then go for years forgetting about that and then you start handing out shell accounts to people, you may find yourself listetning to someone cat'ing /dev/urandom into /dev/dsp in the middle of the night That and it's just the perfect thing to use the unix permissions model for that it makes no sense to pass up the perfect opportunity to acquaint yourself with it.