> I'd like to have this same single checking function used for all the
> control-the-world permission checks. This includes all the "isroot"
> settings used in trivfs and term and so forth, and also the more detailed
> checks in things like chown. In keeping with fshelp_isowner, it might be
> natural to call this fshelp_isroot instead of cancontrol. The code in
> e.g. diskfs_S_file_chown would look like this:
Is that question really is the user root? It seems misleading to me.
> I don't think it much matters which of these criteria we use.
>
> If pfinet's style is preferable, then it should at least consistently track
> the st_uid/st_gid of the underlying node if it passes through changes (as
> trivfs filesystems usually do). Thus the interface in my example code
> above, where fshelp_isroot takes a struct stat containing the last stored
> state of the underlying node.
I think we should use both: if you have an id of the translator, you can
send it signals et al., therefore, you should be able to change its
options etc; if you own a file, you can control its ``contents''
therefore you should be able to control the translator.
If you agree to this usage, I think it eliminates the use of this function
helping with chown?
PGP signature
