xfs
[Top] [All Lists]

Re: Mounting XFS volumes with uid= or gid= or both

To: "Gonyou, Austin" <austin@xxxxxxxxxxxxxxx>
Subject: Re: Mounting XFS volumes with uid= or gid= or both
From: Steve Lord <lord@xxxxxxx>
Date: Fri, 13 Jul 2001 14:00:02 -0500
Cc: "'linux-xfs@xxxxxxxxxxx'" <linux-xfs@xxxxxxxxxxx>
Comments: In-reply-to "Gonyou, Austin" <austin@coremetrics.com> message dated "Fri, 13 Jul 2001 13:43:58 -0500."
References: <85063BBE668FD411944400D0B744267A6433E2@AUSMAIL>
Sender: owner-linux-xfs@xxxxxxxxxxx
> Could chacl possibly be used to force files to be written as a specific
> UID/GID?
> 

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.

Steve


<Prev in Thread] Current Thread [Next in Thread>