![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
I did a little further investigation into my troubles with the login process changes permissions on /dev/video, audio, mixer, etc... Originally I thought it was related to the KDE X11 login, but eventually figured out it the following statement in /etc/pam.d/login which enables this feature: session optional /lib/security/pam_console.so Now that I understand the process, I like it. However, I have uncovered one little problem. At some point, my machine was shutdown uncleanly, and when it restarted, pam_console.so could not recreate the lock file /var/lock/console/chris This prevented pam_console.so from completing its mission and left the ownerships of the various /dev/devices set incorrectly. Once I removed the existing locks in /var/lock/console, and logged in again, all was well. This behaviour may or may not be intentional on RedHat's behalf, but I think a simple /etc/rc.d/rc1.d init script could easily cleanup the locks on system boot up... comments? +------------------------ | christoph | linuxguy at ici.net | http://home.ici.net/~linuxguy - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |