The reason for this is, that ntfs in 2.4 kernels only allows read access or write access if compiled in up to ntfs of nt4. 2.6 kernels have a more advanced ntfs module that can write ntfs, but not fully supported
That's not what i mean. How come that umask = 777 results in:
d--xr--r-- 1 root users
- that's a permission value of 144, as a result of setting umask to 633, not 777..
Other effects i saw (with other umask values) made me believe that they're accidently using some subtsraction operation instead of an arithmetic AND operation, so that the missing write-bit (which is always unset with ntfs) causes the wrong results. But eventually i can't understand the result above.. However, i'd still consider that thing as a bug.
-- [EMAIL PROTECTED] mailing list
