Hacker News Reader

Imo it was the right call. Linux filesystems, file attributes are different from Windows, and the two never would've been completely compatible. The two big ones, are the execute bit, and the very fact that windows files represent the data on disk, while Linux ones are just a hardlink to the inode.

It is what it is. My workflow is that I rsync the relevant files from Windows to Linux, do the work, and rsync them back. It's clunky but works well enough.

View on HN

> The two big ones, are the execute bit, and the very fact that windows files represent the data on disk, while Linux ones are just a hardlink to the inode.

This contrast is somewhat true of FAT but not NTFS.

Which is to say, in FAT, the direntry defines the first entry in the cluster chain, and the file size. But NTFS is not like this. There is a concept of inodes, which they call file IDs. Hardlinks are also a thing. You can also create a file, then delete its name, but leave the handle to the inode open. You can also open by file id.

This really isn't factually based. MFT entries are conceptually equivalent to i-node table entries. And the execute bit is what traversal checking bypass is all about.

Reply on news.ycombinator.com