To read all comments associated with this story, please click here.
They are limited in XP and 2k so that you can't symlink a folder from a network drive, eg: \compmy folder -> C:my folder won't work.
I always though it was so people didn't use thin clients and presumably so MS gets more licenses by not allowing this, but they fixed it in Vista. At least for administrators, because users with regular privileges can't use symlinks.
Does NTFS-3G need regular defragging just like the original? And does it slowly grind to a halt as the disk fills up - like the original?
For resilience, NTFS is a great FS but it is slow and high maintenance.
I think I'd stick with native Linux file systems and share with Windows using Samba.
This has to be great for disaster recovery (for disasters such as "Oh my god! I've accidentally installed Windows")







Member since:
2005-07-06
The man pages of ntfs-3g say they support symbolic links (softlinks / symlinks). I guess that creating a symlink on a ntfs partition will work in linux, but not in windows? Windows softlink support is very limited.
I'm planning to move all my data to a new harddisk, and I'm still unsure about which filesystem to use. Both windows and linux must access the data. Ext2 drivers exists for windows, but matt's driver lacks networking support and stefan's driver has no unicode support. Both lack softlink support. (It would be great if symlinks would show up as .LNK files in windows, but such a feature would require another layer, and probably slow down the driver.)