On Thu, Aug 18, 2005 at 04:02:37PM -0700, Matt Zimmerman wrote: > > Yes, as I said: > > > > > > What might be better for the default Debian permissions setup is to > > > > make the socket for public use by anyone in the audio group. > > I don't think that addresses all of the issues. If the first user logs out, > it shouldn't cause the second user's apps to have esd yanked out from under > them, they should be able to have independent audio preferences, etc.
Starting esd as daemon:audio would resolve the first part. Audio preferences (at least the ones esound offers) are hardware-specific settings, that wouldn't change per user. > > With your solution, if the first user leaves anything playing sound (game, > > music player, etc) running, additional users won't be able to get any sound. > > That isn't true with dmix. The supplied patch has a comment about how -as is used by default so that other users can actually use the device. If it's not true with dmix, then why the change? ALSA (and therefore dmix) aren't setup by default by d-i, anyways. I've also yet to see dmix do what it claims to. I'm guessing there's some sort of restriction on using OSS emulation. While that restriction is there, the user gets a better "don't need to think about low level sound details" experience by routing everything through a sound daemon. > > Also, even with your modified proposal on the socket name, only the first > > user to login can use third party applications. > > I'm willing to accept that tradeoff, given that it's more important to me > for free software to be robust than for commercial software to be robust. > It doesn't break it outright, and it still works in the cases where it works > today (with only one user running esd). The experience for the user in this case is horrible, however. Either the program refuses to start, or it just doesn't have sound without any sort of message. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
