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.
At work I have a small NIS domain, and everything works great, except I don't have any sound while in an X session. I fixed it so I have sound from the console (I can adjust settings with alsamixer and such), but when I log into any desktop environment, alsamixer gives me the "alsamixer: function snd_ctl_open failed for default: No such file or directory" error like there's no sound card installed.
At work I have a small NIS domain, and everything works great, except I don't have any sound while in an X session. I fixed it so I have sound from the console (I can adjust settings with alsamixer and such), but when I log into any desktop environment, alsamixer gives me the "alsamixer: function snd_ctl_open failed for default: No such file or directory" error like there's no sound card installed.
Does anyone know how I can make this work?
Are you sure that you are getting sound in the console? Even when using NIS, you still have to configure the soundcard on every box. So, make sure to run alsaconf as root on all your workstations. Also, make sure the accounts is included in the audio group just in case.
Yep. I know it works, because I have a local user that can access the sound card just fine. It's just the NIS user(s) that can't. And as far as I know, you can't simply add an NIS user to a group, since they're not technically a user on the local machine. usermod -G whatever_group username will complain about the user not existing.
Gotcha! Ok, so next question, are all these workstations Slackware, or are they a combination of different Operating Systems? If they are all Slackware, are they the same version? Also, did you make sure that you added your NIS users to the audio group on the NIS server? I'm quite familiar with NIS, so hopefully, I can get you on the right track.
Gotcha! Ok, so next question, are all these workstations Slackware, or are they a combination of different Operating Systems? If they are all Slackware, are they the same version? Also, did you make sure that you added your NIS users to the audio group on the NIS server? I'm quite familiar with NIS, so hopefully, I can get you on the right track.
The NIS server is a Slackware 11.0 server. The client(s) are a mixture of Fedora and Slackware-current machines. The Fedora machines are fine, since I think they do some PAM tricks to allow NIS users to access local devices, but since Slackware doesn't ship with PAM, there are device issues across NIS. Also, since the NIS server is an 11.0 machine running a 2,4 kernel (therefore, no power group, udev, etc.), there are obvious group issues. I did, however, add these groups (with the same GID even) to the NIS server, but it made no difference.
The NIS server is a Slackware 11.0 server. The client(s) are a mixture of Fedora and Slackware-current machines. The Fedora machines are fine, since I think they do some PAM tricks to allow NIS users to access local devices, but since Slackware doesn't ship with PAM, there are device issues across NIS. Also, since the NIS server is an 11.0 machine running a 2,4 kernel (therefore, no power group, udev, etc.), there are obvious group issues. I did, however, add these groups (with the same GID even) to the NIS server, but it made no difference.
I think using Slackware 11 as your NIS is the problem. The Slackware clients don't are probably getting confused on the group id (just a guess). In your Slackware-current box, look at the /etc/nsswitch.conf file and post what shows up after group:. It should be something like "files nis". I'm almost certain that Slackware 11 is causing the problems.
I changed nsswitch.conf to use "files nis" on passwd, shadow, and group. Also, I've made sure the GIDs are the same with the NIS server and it's clients.
Also, like I said, the NIS users can access local devices (sound card, CD-ROM, etc.) on the client machines when they're NOT in X, this only happens when I start an X session.
I changed nsswitch.conf to use "files nis" on passwd, shadow, and group. Also, I've made sure the GIDs are the same with the NIS server and it's clients.
Also, like I said, the NIS users can access local devices (sound card, CD-ROM, etc.) on the client machines when they're NOT in X, this only happens when I start an X session.
Ah, understand. I still stand on slackware 11 being the problem. In my experience, when deploying an NIS network, it is best practice to keep all servers and client with the same OS just to avoid those kinds of issues. Is the only having problems playing sound in X are your slackware-current box?
Yes. Like I said, the Fedora boxes use PAM I believe to set privileges for all users, so the NIS users have the same rights as the locals. It's just the Slackware boxes that have the permission issues.
I'm not really sure what the issue is. You can try and remove the nis option from the group section in the nsswitch.conf file. This should force Slackware current to use the local groups. Not sure if that would work though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.