> So I would suggest the following: (with similar function signatures for
> the 'l' and 'f' variants):
>
> chflags(char *name, int attr_namespace, int *new_flags, int *curr_flags)
Oh, look - somebody has even worse l-k feed ;-) That's exactly what I
proposed one round downthread.
> If new_flags is non-NULL, then it is a pointer to the new flags which
> should be assigned to the file. If curr_flags is non-NULL, then it is a
> pointer to the flags *after* the chflags operation. This makes it easy
> for an application to check whether or not the filesystem refused to set
> a particular flag (for example, if it doesn't support that particular
> flag).
Makes sense.
-
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/