> > Actually the _best_ solution in the chmod/chown case is if the app
> > actually examines the error value. If it's ENOSYS or EOPNOTSUPP, then
> > presumably the operation failed, because it does not make sense on
> > that particular filesystem. So if it is trying to copy the file
> > attributes, it can safely ignore such an error.
> I agree. However, the amount of applications not currently handling this
> correctly is likely to mean that is an unrealistic solution,
I think the best solution is to make it optional. If it breaks your
app, turn on the workaround _and_ report it to the app's developers.
If for example this is breaking gedit, that should be fixed. Fending
off such bug reports refering to POSIX doesn't work. Some filesystem
just can't be made compliant.
But I don't think that anything much more complex than checking for an
error value should be needed to work around non-posixy filesystems.
Get latest updates about Open Source Projects, Conferences and News.