Comment 2 for bug 124480

I've seen this on the ntfs-3g page, but I don't understand why ntfs
can be accessed in a POISIX way, since it is a filesystem designed for
windows. What are the advanteges? (since people have always used the
vfat filesystem to share files, which is non POSIX at least by
default?). This is an unexpected change! And finally what are the
disadvantages of using the filesystem in the WIN way?

On the other hand I'm glad to discover that there is a fix for
windows. BUT this should *really* be told to the user who uses
ntfs-3g, especially now that there is the spec to add it by default.

Doesn't using samba slow down the acces? I've seen lots of apps that,
before accessing the file, copy it to the local cache, which is a very
"expensive" operation for big files

Finally, I think that the user should have the possibility to choose
(maybe through ntfs-config ?) the first time he uses this driver.

He should be told that using it in the POSIX way, files will be case
sensitive, some characters such as : ? \ and others that previously
were not allowed on the filesystem now are allowed, and that they have
to download and install <B>Windows Services for Unix</B>
And he should be told that if he wants to access the filesystem in the
standard way, there are these restrictions in the filename, and the
case will be non sensitive