Messages in this thread | | | Date | Fri, 18 Feb 2000 07:26:10 +1100 | From | Richard Gooch <> | Subject | Re: [patch-2.3.46-p3] /proc/driver/microcode P6 ucode support |
| |
Hi, Alexey.
> BTW can I ask one silly question (I apologize, if it is RTFM)?
There is a manual: Documentation/filesystems/devfs/README and it should say this.
> How does devfs control access to devices? Who does set > permissions?
Drivers which create device entries specify a default permission. You can override that with devfsd (the daemon). You can also use devfsd to capture inode change events (chmod/chown), so you can build your own persistence mechanism. In the future, devfs will tunnel through to the mounted-over FS and save permissions there.
Note that if you want to set permissions on a group of devices (i.e. /dev/vc/*) then using the existing devfsd-based mechanism is more efficient in space usage.
Regards,
Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |