> Could chacl possibly be used to force files to be written as a specific
I do not think so, access control lists merely control who has
access to files, not who owns them.
I presume what you are attempting to do is create a filesystem where
no matter who creates a file, it ends up with the specified uid
instead of that of the user. A sort of msdos style of user id - i.e. none.
I think the filesystems which support the uid and gid options are those
which do not directly support storing uids and gids themselves. So the
options are there to help non-unix filesystems function in a unix environment,
not to dumb down a unix based filesystem.
It would be possible to implement this, there are probably only a couple
of key places in xfs which would need changing to place a uid/gid
from the mount structure into an inode rather than that supplied
by the caller. These would be create a new inode and setting the
attributes of an existing one.
However, I do not see this as something which should be folded back
into the main xfs code base.