Jan Engelhardt <[EMAIL PROTECTED]> wrote:
> vfat does not know about ownership, hence the files are always owned by the
> vfat mounter (or whatever the uid= option specified). Which brings
> a problem to userspace programs trying to utime() but which do not
> run as the same user as the vfat mount
On 7/10/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
Linux does check for write permission, but _only_ for time=NULL.
Hence it would be helpful if someone knows the exact SUS text,
or whether this is not explicitly specified in SUS, leaving room
for interpretation.
I have already checked it str
On Jul 10 2007 12:18, Pawel Dziepak wrote:
>
> Single UNIX Specification says crealy that to do utimes on a file user
> have to had write permissions or be a file owner.
Linux does check for write permission, but _only_ for time=NULL.
Hence it would be helpful if someone knows the exact SUS text,
2007/7/10, Jan Engelhardt <[EMAIL PROTECTED]>:
I am not sure how this could be dealt with besides passing -o quiet to
mount.vfat. Any ideas?
The problem is in the function utimes. I have mounted vfat partition
as a root, then changed permissions to 777 for all files. However, I
wasn't be able t
Hi,
vfat does not know about ownership, hence the files are always owned by the
vfat mounter (or whatever the uid= option specified). Which brings
a problem to userspace programs trying to utime() but which do not
run as the same user as the vfat mounter, because:
fs/attr.c:53
ret =
5 matches
Mail list logo
