Luca Olivetti wrote: > Christophe Combelles wrote: > > But why is it necessary to change the perms of the devices ?? > > This should be only a matter of groups. > It's not so simple, a group cannot tell if you are logging in at the > console or remotely (read below) > > For example /dev/mixer should always belong to root:audio with perms > > crw-rw----, and a user should be in the group audio. > > So even ater login, the /dev entry has not been changed, but only the > > users of the group audio could access /dev/mixer. > > And when a user is created, it should automatically belong to a series > > of standard groups like audio, etc. > Remember, Linux is a multiuser and networked system. Only a user logging > in at the console should access /dev/mixer (and /dev/dsp, and > /dev/video, etc.), a user logging in remotely (normally) has no use for > it. This pam module, while not ideal in every situation, is configured > to give access to some devices only to users phisically logging in at > the machine, and this should be ok for most situations. > If you need fixed permissions (for example, to record from the tv card > in a cron job or start a recording remotely) you can tweak > /etc/security/console.perms
The system I most often boot to Mandrake has no sound card, and takes more like a minute to complete a login if not root. There's no excuse for such behavior to have survived the 9.0 beta process, much less continue in 9.1. 7.1 has no such problem on the same machine. -- "There's nothing so absurd that if you repeat it often enough, people will believe it." William James Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
