| PLEX86 | ||
|
Do we need wine 48CAPSKOV There are quite many NTFS implementations for Linux with different degree of reliability and functionality: 1. Obsolete NTFS kernel driver. It's used upto kernel 2.4. Read is ok, write was disabled for Win2000 and up 4 years ago because write was implemented only for NT4. This basically read-only (today everybody use only XP, Win2000 and Win2003) driver is referred as "dangerous" by a few people who prefer still to live in the previous millenium. Do we need wine 49 Thank you, Dances With Crows. You understood perfectly. I do not mind any one. Everyone here is warmhearted. Thanks in advance. I am a... 2. Current NTFS kernel driver. Read is fully supported for 3-4 years, write is reliable but not everything is implemented. Do we need wine 50 I've just begun working with Wine myself to help adapt VB software to Linux, because I also want to leave Windows. I'm getting a big kick out... 3. User space NTFS library and utilities (ntfsprogs). Full read and almost full write support. Reliable. 4. ntfsmount. It's in ntfsprogs and uses FUSE to mount and read-write NTFS. Comment is as above. Full read and almost full write support. Reliable. Several Live CD uses it, e.g. Knoppix, Recovery Is Possible, Trinity RK, etc. 5. Captive NTFS. It uses the Windows NTFS driver. It has some limitations (e.g. very slow, 1 GB file size limit) but if you manage to get it work and can gracefully umount then it should be fine. Other NTFS implementations for Linux are done by Partimage (very limited, not reliable and plans to use ntfsprogs), Paragon, Acronis, Symantec (commercial and limited). Except for the obsolete 1., all the other implementations are still actively developed and maintained. For 2., 3. and 4. see
|
||||
Linux groups from Newsgroups The #1 Usenet Provider on the Internet
|
||||