mount -t vfat has a "quiet" option now. See man(1). quiet: Turn on the quiet flag. Attempts to chown or chmod files do not return errors, although they fail. Use with caution!
It isn't enabled by default. However, a lot of things now don't return an error at all, even without quiet. e.g. pretty much any normal chmod operation will return "success", even if it didn't do anything. With quiet enabled, even chown will silently do nothing. To test this, cd /tmp dd if=/dev/zero of=fat.img bs=1024k count=1 # 1MB file mkfs.vfat fat.img mkdir fat.mnt sudo mount -o loop,uid=$USER -t vfat fat.img fat.mnt touch fat.mnt/foo chmod 700 fat.mnt/foo chown root fat.mnt/foo (run this as your regular user account, so the mount option is uid=peter, for example) If you look in the kernel sources (fs/fat/file.c), you can see that EPERM is still the only error code in evidence. However, it looks like it's mostly only returned when you actually don't have permission, e.g. you don't own the mount, and you're not root. I think ENOTSUP might be an improvement over silence, at least when you're using chmod directly. If some big GUI program is saving a file, the error messages it would print because of FAT are probably useless. -- misleading error message in terminal when trying to chmod on fat32 https://bugs.launchpad.net/bugs/164507 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
