Date: Thu, 06 May 2010 16:40:06 -0500 From: Tim Daneliuk <tundra@tundraware.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Accessing file from windows or to windows Message-ID: <4BE33736.3020307@tundraware.com> In-Reply-To: <m2n64c038661005061436l2b16b51aq4b6869fcc66dbbe1@mail.gmail.com> References: <AB2BC18AD166C948A0BC559E22CE9C9105DEC2CF@FCIEXCHANGE1.FCI> <4BE32DE4.20206@tundraware.com> <j2o64c038661005061430v68eb6394v5b4c5d5f9d37df24@mail.gmail.com> <m2n64c038661005061436l2b16b51aq4b6869fcc66dbbe1@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/6/2010 4:36 PM, Modulok wrote: >>> "writing to an NTFS partition may corrupt the partition" - I'm guessing this is not the case anymore. > > That's only when you have directly mounted an NTFS on the local > machine. Like if you jacked a hard drive out of a windows machine and > plugged it into your BSD machine. If you're accessing it across a > network you're never directly accessing the file system. There is > always an intermediary between you and it; the daemon which handles > file i/o requests. Notice: It handles your *requests*; you never > actually access the underlying file system. Yes, I know this. That was not my question. My question is that when you DO attach to a local NTFS partition, has the write corruption problem for the NTFS driver been fixed, and if so, as of what release of FreeBSD? I know this is now claimed to work in Linux as for ntfs3 support. 'Just wondering where FreeBSD is in that evolution, that's all. ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BE33736.3020307>