The primary problem here is to detect which driver gets used and which mount options should be used. Yes, a discussion with the kernel maintainers will be needed to get some guarantees before proceeding with any kind of workarounds in udisks. Would be nice to see this worked around in udisks for the time being as 5.15 is now released as it is, can't udisks be changed to only check for and apply the windows_names mount option for != ntfs3 filesystems / mount actions? I suppose if noone reports a bug upstream to clarify the situation, preferrably someone like you involved in the userspace and the internals and how to handle these edge cases and point out this change is a real issue then this will go nowhere. They all fail here since the detected ntfs signature doesn't match the required ntfs3 filesystem driver name. Same situation for existing /etc/fstab records and users or scripts calling the mount command. Problem is like this the new filesystem is pretty much useless, at least on the desktop for regular users not being able to mess with fstab and trying to make use of the convenient udisks usage of modern desktops.
0 Comments
Leave a Reply. |