> It's puzzling that chown-chmod would have any baleful effect. > With a plain > file, once you've opened it you can monkey with the inode all > you want and > the filehandle remains valid, and similarly with devfs the > various device > inodes (/dev/misc/psaux, modem TTY, etc.) can be chowned even > if, in the > case of the mouse, the X-server has it open.
At least the kernel module for an OpenGL accellerated card is opened multiple times. A few times when the xserver and the window manager initializes and a few more time for each application that (dynamically) links against the OpenGL lib. So changing file permissions at runtime does affect newly started programs. So you do have multiple clients where some of them must have only user permission. A group based access rights management system is a nice thing if your design is okay. E.g.: - user = group with no X11, no OpenGL - video = group with X11, but no OpenGL - opengl = group with no X11, but OpenGL (thats just my suggestion for the paranoid, typically its caps are included in video) - root = the systems wildcard group A normal user can be made capable of X11 and OpenGL usage by adminstration so that he further joins the respective groups. Alex. _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
