From owner-freebsd-questions@FreeBSD.ORG Thu May 6 21:40:11 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5AC301065672 for ; Thu, 6 May 2010 21:40:11 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id F1BF08FC14 for ; Thu, 6 May 2010 21:40:10 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.4/8.14.4) with ESMTP id o46Le3PD065621 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 6 May 2010 16:40:03 -0500 (CDT) (envelope-from tundra@tundraware.com) Message-ID: <4BE33736.3020307@tundraware.com> Date: Thu, 06 May 2010 16:40:06 -0500 From: Tim Daneliuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: FreeBSD Mailing List References: <4BE32DE4.20206@tundraware.com> In-Reply-To: X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.5 (ozzie.tundraware.com [75.145.138.73]); Thu, 06 May 2010 16:40:03 -0500 (CDT) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: o46Le3PD065621 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: Re: Accessing file from windows or to windows X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 May 2010 21:40:11 -0000 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/