Thanks for the response.

On Sat, Sep 5, 2020 at 5:03 PM Jean-Pierre André <
jean-pierre.an...@wanadoo.fr> wrote:

> What was the purpose of wanting to have the same user
> recorded for two different users ? If you are double
> booting with Windows, how are the the Windows accounts ?
> When you do not have the same account sharing in Windows
> and Linux, you end up with this kind of problems.
>

Well it's not actually a problem. I understand that the behavior is
expected. And one-to-one user mapping between Linux and Windows can get
things straight. I'm asking for something extra, specific to FUSE only, I
think. And that is to make two (or more) Linux users think they own the
same file. Now I know that this isn't how DAC works on Linux and Windows.
But since it's possible to achieve with FUSE (and NTFS-3G is already using
FUSE), it'd be helpful if available.

You should probably have both users in the same primary
> group and use group permissions to facilitate file
> sharing by users.
>

Yeah I have the same setup. But write-access to primary GID or
supplementary groups isn't alway enough. As I quoted earlier, utime
<https://man7.org/linux/man-pages/man2/utime.2.html> won't work if the
calling user isn't the file owner. It's problematic when doing incremental
backups to NTFS drive. *rsync* will keep on complaining *"failed to set
times"* for every file.

So what I'm talking about can be something like: When NTFS-3G is mounted
with option, say, "mirror_users" and the calling Linux UID is mapped to the
SID file owner in the UserMapping file, the UID will see itself as the
owner of the file. In this way both Linux users (user1 and user2 in my
example) will see themselves as the owner of files owned by single Windows
SID (1001 in my example).

Regards,
Irfan
_______________________________________________
ntfs-3g-devel mailing list
ntfs-3g-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel

Reply via email to