SEO

I've got slack8.1 installed on a 450mhz and all is well with the
exception of sound use by other any other user execept root.
I pecked around google and found a few things such as:
chmod a+r /dev/dsp
chmod a+r /dev/mixer
chmod a+r /dev/sequencer
chmod a+r /dev/audio

This didn't help at all.....as a user I still get permission denied when
trying to use the sound server. I opened up the X-server and using
kuser finally got everthing to work....but would have rather gotten it
fron the console.....what else should I have done to get this done fron
the console?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In article <3EF9B90D.A1CAA606@jomail.com>, Dennis R. wrote:
> I've got slack8.1 installed on a 450mhz and all is well with the
> exception of sound use by other any other user execept root.
> I pecked around google [snip]

Not very hard, I gather.

How come I can play sound as root, but not as a normal user?

http://wombat.san-francisco.ca.us/cgi-bin/fom?file=21

(FWIW, you need *write* access to some of the devices you
mentioned, which is why your original Google result didn't help.)

- --keith

- --
kkeller-mmmspam@wombat.san-francisco.ca.us
(try just my userid to email me)
alt.os.linux.slackware FAQ: http://wombat.san-francisco.ca.us/cgi-bin/fom

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj75zJcACgkQhVcNCxZ5ID8yPgCfVz3in0xC7u mBMTGMPxPqHpJA
GzQAnik32+Y7WvyXj6H3kE/6V943F/rX
=gYKK
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

?????? ? tempted the fates in alt.os.linux.slackware
by rushing in here and proclaiming the following to be true:

> so, you need "chmod a+w xxx" where xxx may be "/dev/dsp" or "/dev/dsp0" or
> "/dev/dsp1" ...

No, you don't.

It doesn't make much sense for you to warn the OP about giving
insecure, world readable access to the audio devices then advise him to
make them world-writeable as well, now does it?

This question is covered in the FAQ for the group, is covered in the mail
sent to 'root' when you install Slackware, as well as being archived on
Google.

RTFM, STFW, GAFC.

What the original poster (and you)_should_ do is read the FAQ that is
posted in here, every single day, that covers the (F)requently (A)sked
(Q)uestions that get posted in here.

The "correct" answer (for the majority) is to change the permissins
_basck_ to the more secure 0660. Verify that the ownership of /dev/dsp*
is to "root.sys" (changing it is necessary), then add the users
(including yourself) that you want to have access to the audio devices
to the 'sys' group in the /etc/groups file.

It's just thsat simple, and it's far more secure than chmod'ing everything
to 0770 (like a clueless newbie).

- --
Cibao Cu' Ali G. Colibri | San Francisco is my kind of city, Where the
GnuPG Pub Key EC9F1D51 -o) | women are strong and the men are pretty.
Linux Kernel 2.4.21 /\\ |
Slackenstein 9.0-ish _\_v |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.1 (GNU/Linux)

iD8DBQE++dQdJ+aEAOyfHVERAkUcAJ93fqguAaCaR7p9JyeiUS RYHB/2wwCfRBoL
zi9adgRKYdOZwRb7aNUVx+A=
=BOHr
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

+Cibao+ tempted the fates in alt.os.linux.slackware
by rushing in here and proclaiming the following to be true:

> This question is covered in the FAQ for the group, is covered in the mail
> sent to 'root' when you install Slackware, as well as being archived on
> Google.

O.K., so I'm apparently now smoking crack today.

FYI: Pat covers several things in that initial e-mail, such as setting up
an ide cdr/w, NFS, serial ports, checking the package databases, printers &
ppp/tcpip. However, what he does _not_ cover is setting up the sound
devices. That's covered in our (AOSLS) FAQ, instead.

Other than that, the rest of my post (hopefully) was still dead-on.

- --
Cibao Cu' Ali G. Colibri | I allow the world to live as it chooses,
GnuPG Pub Key EC9F1D51 -o) | and I allow myself to live as I choose.
Linux Kernel 2.4.21 /\\ |
Slackenstein 9.0-ish _\_v |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.1 (GNU/Linux)

iD8DBQE++ejWJ+aEAOyfHVERApWcAJ9PRBgbTfbv/wb4s2L4eLSzdOYMmQCeNf5w
vNMWALqEgXKxcCUjs7dWNpU=
=mCn2
-----END PGP SIGNATURE-----

In article <slrnbfjq7k.7v3.Cibao@raven.home>, +Cibao+ wrote:
> ppp/tcpip. However, what he does _not_ cover is setting up the sound
> devices. That's covered in our (AOSLS) FAQ, instead.

I was going to check my mail about that one.... did not remember it.

--
Perfection is reached, not when there is no longer anything to add, but
when there is no longer anything to take away.
-- Antoine de Saint-Exupery

Dennis R. wrote:

> I've got slack8.1 installed on a 450mhz and all is well with the
> exception of sound use by other any other user execept root.
> I pecked around google and found a few things such as:
> chmod a+r /dev/dsp
> chmod a+r /dev/mixer
> chmod a+r /dev/sequencer
> chmod a+r /dev/audio
>
> This didn't help at all.....as a user I still get permission denied when
> trying to use the sound server. I opened up the X-server and using
> kuser finally got everthing to work....but would have rather gotten it
> fron the console.....what else should I have done to get this done fron
> the console?

My experience from today: in kde control center, or otherwise, set artsd
sound system to auto-suspend if not in use on a 1 second timer. I had gaim
refuse to even load, but when i set that it worked immediately.

--
" ... and are endowed by their Creator
with certain unalienable rights ... "
NeoSadist