https://bugzilla.novell.com/show_bug.cgi?id=465502 User kasievers@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465502#c6 --- Comment #6 from Kay Sievers <kasievers@novell.com> 2009-01-15 11:06:41 MST --- (In reply to comment #5)
@sndirsch & @kasievers: For a machine with one user or maybe a family, groupwise permission management is fine. But we manage an instructional program with four computing labs and about 1000 students (different every 3 months); an enterprise deployment would have similar problems. student in group "video" would likely exceed a buffer limit
That sound like NIS, LDAP like setups, which should be fine with such a group assignment. :)
better to make /dev/nvidia0 mode 666.
That's what most people do with these drivers, yes. But a distro can not do that by default for security reasons.
Granting permission via an ACL would be nice, but I wanted to keep it simple, and in particular, if the machine crashed with the ACL row in place, > it takes a little brainpower to get rid of it next time around
Changes in /dev do no survive a reboot, /dev is a tmpfs, populated from scratch at every reboot. Is that what you mean?
Hell will freeze over before the vendors make their drivers' licenses FOSS compliant. Maybe a compromise: they would register with sysfs only the most basic device characteristics, bypassing legally troublesome proprietary features.
It's only one driver they load, and as long as the driver does not advertise itself in the kernel as GPL, they can not see the needed functions, can not resolve the GPL symbols in the kernel. So they would need to change the whole driver, and publish parts of it to be able to do that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.