oiaohm wrote:F-full ownership
O-ability to change ownership
X-execute (run or open)
W-append and modify
Linux has most of these on all major filesystem or able to be created.
Linux filesystem have a lot longer attribs 3 layers of read write execute for user group and everyone. Ie X R and W. Extended attributes could be used to do full ownership ability to change ownership and delete even just append.
As far as I know, linux only has RWX where W also grants D permissions (where it does not in NTFS) and R translates as RX (where it does not in NTFS). So saying that they're the same, they're not. Also NTFS also supports permissions by owner, group and user just like Ext3 (under advanced).
I'm not saying "use NTFS", i am saying translating between the way Linux does permissions and the way Windows does permissions can cause problems. So what i was saying "have a filesystem that does it the way NTFS would [to minimize these problems]". Nor am i saying that ReactOS has to have 1 and only 1 filesystem. Indeed NT4 supported FAT, VFAT, HPFS and NTFS, 2000 supported FAT, FAT32 and NTFS (and read/wrote to VFAT but you couldn't install using it), XP supports FAT32 (read/writes FAT) and NTFS. For secure network access it wants to use NTFS and therefore, if ReactOS is ever going to work in a windows network or use programs that use NTFS permissions, you are either going to have to 1) translate or 2) offer a native system.
[edit: some grammar corrections]
And there are a few programs that do require NTFS, these are mostly programs that run on servers but they do exist.