relan
relan
> Proposal: a method to request allocation some sectors without writing zeroes to new blocks. Well, looks like the infrastructure (kernel, FUSE and programs) just isn't ready for such feature....
> is it SMB version thing or truncate implementation in Windows? Can be both. A possible solution that comes to my mind: 1. On `truncate` set `size` to the desired...
Do you have a backtrace of the fuse-exfat crash?
> Searching through the exFAT code, however, I didn't find any mention of support for Windows attributes. Right, fuse-exfat does not support manipulations with those attributes. > Would it be...
@nemonein, this issue is about FAT's attributes system and hidden. Unix permissions are a different story. exFAT does not have any equivalent for them. But fuse-exfat supports `fmask` and `dmask`...
The last time I looked into automounting, default mount options were hardcoded into udisks. To override defaults you can create an fstab entry or udev rule.
@dionorgua, what do you expect fuse-exfat to do when it discovers a read-only file?
> Is it possible to add, somewhere in the filesystem, a special byte for each file, indicating the corresponding Unix permission? Yes, in exFAT each file entry can have optional...
No, I mean entries that have bit 5 in their type field set. In fact, entries of type 0xe0-0xff can store arbitrary data. But if we collide with another exFAT...
Yes. Currently it's in the `libfuse3` branch. Would be cool if you could test it.