>On Fri, Apr 11, 2003 at 01:48:17PM -0700, David Lang wrote:
>
>
>>ant then you also have all the same problems as devfs about default
>>permissions, making permissions persistant across reboots, etc.
>>
>>
>
>You can store the default permissions in the database you use to store
>the naming data. This solves the reboot problem, as long as you can
>convince people to not modify the permissions on their own (well even if
>they do, at shutdown, you can always validate that they are the same
>before you clean up the node.)
>
>And provide an easy way for users to change the permissions so they show
>up in the database.
>
>devchmod and devchown anyone? :)
>
>
Greg,
I've been thinking of how to solve this particular problem, and believe
you could use dnotify in a daemon to track permission and ownership
changes and store them in a backing database. In fact, we do something
similiar to this today. This allows the user to use any type of
application for changing permissions/owners, even syscalls directly
without having to go "through" any sort of tracking database.
>thanks,
>
>greg k-h
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/