From owner-freebsd-arch@FreeBSD.ORG Tue Feb 14 03:08:04 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A62416A433 for ; Tue, 14 Feb 2006 03:08:04 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from mail07.powweb.com (mail07.powweb.com [66.152.97.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 100C843D75 for ; Tue, 14 Feb 2006 03:07:56 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from vixen42.vulpes (24-119-205-114.cpe.cableone.net [24.119.205.114]) by mail07.powweb.com (Postfix) with ESMTP id C98B814DA18; Mon, 13 Feb 2006 19:07:51 -0800 (PST) Date: Mon, 13 Feb 2006 21:17:03 -0600 From: Vulpes Velox To: Roman Kurakin Message-ID: <20060213211703.6ec79399@vixen42.vulpes> In-Reply-To: <43F04891.5030208@inse.ru> References: <43EFD5A0.83BB82C4@verizon.net> <43F04891.5030208@inse.ru> X-Mailer: Sylpheed-Claws 2.0.0 (GTK+ 2.8.12; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: arch@freebsd.org, babkin@users.sf.net Subject: Re: NTFS write support X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Feb 2006 03:08:04 -0000 On Mon, 13 Feb 2006 11:51:29 +0300 Roman Kurakin wrote: > Sergey Babkin: > > >Hi, > > > >I've finally got Win XP as the second OS on my mahcine. The next > >thing I've found is that NTFS support still seems to be read-only, > >and it does not look like anybody is actively working on it. > >So adding the NTFS write support looks like an interesting > >project to undertake. > > > >Just in case, if anybody working on it already, please let me know. > >Any kinds of ready pointers to the good docs would be welcome. > >Or to the existing implementations too (Linux?). > > > IIRC Linux has write support but code marked as "NEW" and thus not > stable. As for me, I solved that problem by setting up FreeBSD and > Win on separate machines. I've done this after interference between > ntloader and sysinstall. I found a nice fix to be using partition magic, converting it to fat32, and then reinstalling the freebsd bootloader. It is also handy for shrinking installs as well.