'Twas brillig, and Lennart Poettering at 11/02/10 00:25 did gyre and gimble: > On Tue, 09.02.10 18:51, Colin Guthrie (gmane at colin.guthr.ie) wrote: > >>> By the way normally only the users who are in the audio group are >>> allowed to access audio (not entirely sure how this is handled with >>> osx though), so it's not like a random user is allowed to access the >>> audio device. >> >> The "audio" group is a legacy and is no longer needed. ACLs on the audio >> device are far more flexible. > > It's actually not legacy. In fact it was known on Debian for a long > time and only recently added to the other distros, too, pushed in via > udev. Ahh fair enough. Thanks for enlightening me (as usual!) > If people want to allow users unconditional access to audio devices, > regardless whether they are logged in on the console, then they can > add them to that group. That's fine. ACL certainly are more flexible, > but just adding someone to the "audio" group is certainly simpler. > > Most distros support both CK/ACL-based access and audio group based > access out-of-the-box. And that's fine that way and not going to go > away. But if a good proportion of the audio hardware out there does not support hardware mixing, should this mode of operation be encouraged? I'd have thought that by enabling this way of working it's just ultimately going to lead to problems when such hardware is attempted to be accessed concurrently? Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/]
