On Mon, 2003-07-14 at 09:07, RICOTTA, FEDERICO [AG-Contractor/5000] wrote: > It worked for me too....... At least for reading... > in kernel 2.4.20-8smp with Konqueror I saw that in the > page above (which Callan talks about) that there is a > new version of the ntfs.o module that was developed > for 2.5.### kernels that supports writing!!!!!! > Check it out.....!!!! First off, the existing NTFS drivers in 2.x support writing. But it is disabled by default for _good_ reasons. Understand that the NTFS filesystem itself is _tied_ to the registry. That means even if you have another NT/2000 system, you should _never_ _write_ to the NTFS filesystem _except_ with the system that created it! Microsoft really did _not_ think things through when it forked HPFS into NTFS. The only "workaround" before NT 5.x (2000/2003) was to make sure you _always_ wrote files you cared about on a NTFS filesystem with _domain_ ownership/ACLs. Otherwise things could get nasty -- especially if you have _any_ files on the disk that are "owned" or granted ACLs to local accounts of the machine. Not just "I can't read it" but someone on the order, "crap, I Windows just toasted Windows ... again." The "new way" in NT 5.x (2000/2003) is to use "dynamic disks." "Dynamic disks" are a _replacement_ partition table, so you'll need a Linux kernel that supports it (I assume that is what 2.5 does, maybe already in 2.4?). Dynamic disks store some "registry-independent" maps and other details so the NT-machine other than the one that created the NTFS with all the NT-machine specific meta-data can read them, or at least not _corrupt_ the filesystem. ;-ppp -- Bryan -- Bryan J. Smith, E.I. b.j.smith@xxxxxxxx MCSE/MCSA, RHCE/LPIC-2, SCSecA/SCNA and dozens more http://thebs.org http://thebs.org/certs.pdf -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
