|
From: Anton A. <ai...@ca...> - 2003-07-22 10:30:41
|
Feel free to send me patches for all of the below... If you are doing it please rephrase the DANGEROUS and "guaranteed to be broken" to EXPERIMENTAL and "while we cannot guarentee that it will not damage any data we have so far not received a single report where the driver would have damaged someones data so we assume it is perfectly safe to use". Feel free to rephrase any way you like... Cheers, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/ On Sun, 20 Jul 2003, Leonard Norrgard wrote: > Some more or less humble suggestions for 2.6: > > Documentation/filesystems/ntfs.txt > -- overview says "works only in read-only mode" rather than also > mentioning > the partial rw support available > -- overview needs a reference to the project website, > http://linux-ntfs.sourceforge.net, > with a description of all the material available there, (FAQ, NTFS > on-disk format docs, ...) > -- overview needs to mention ntfsprogs (!) > -- reorder sections: "Features" before "Supported mount options" > -- Section "Limitiations when using the MD driver": > Implement a test in code for the dangerous case that the > documentation warns > for (hoping this is possible ;) and refuse to mount such MDs (or > mount ro?). > -- Add section saying "we" know the NTFS format well enough to have > write support, > if we only would have time or someone would step in to sponsor > (thus magically creating time) > > fs/Kconfig > -- CONFIG_NTFS_FS > -- needs direct mention of project website, > http://linux-ntfs.sourceforge.net > -- mention ntfsprogs (!) > -- CONFIG_NTFS_RW > -- described as (DANGEROUS) and: > | This enables the experimental write support in the NTFS driver. > | > | WARNING: Do not use this option unless you are actively developing > | NTFS as it is currently guaranteed to be broken and you > | may lose all your data! > | > | It is strongly recommended and perfectly safe to say N here. > > This warning seems outdated ("guaranteed to be broken"?) > > -- Leonard |
