On Tue, 2003-12-09 at 23:29, Nick W wrote: > Assuming that NTFS implementation [captive] works hopefully that wont be > necessary. And it'll be r/w, from what I read it works pretty good with > lagged mount time the only drawback. > > /me still uses vfat for winblows. Until the kernel based NTFS is r/w anyway.
FTR, I still use vfat (FAT32) for all my multi-boot systems as well. FYI: The 2.6 kernel (using 2.6.0-test11 right now) has "safe" r/w support for NTFS, although it has some limitations. Here is the Help from 'make menuconfig' => File Systems => DOS/FAT/NT Filesystems => NTFS file system support => NTFS write support (NEW): CONFIG_NTFS_RW: This enables the partial, but safe, write support in the NTFS driver. The only supported operation is overwriting existing files, without changing the file length. No file or directory creation, deletion or renaming is possible. Note only non-resident files can be written to so you may find that some very small files (<500 bytes or so) cannot be written to. <snip> Note: While write support is safe in this version (a rewrite from scratch of the NTFS support), it should be noted that the old NTFS write support, included in Linux 2.5.10 and before (since 1997), is not safe. Curtis _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
