From owner-freebsd-arch@FreeBSD.ORG Thu Feb 7 01:32:04 2008 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41AA616A41B; Thu, 7 Feb 2008 01:32:04 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id CEA1313C448; Thu, 7 Feb 2008 01:32:03 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (unknown [202.108.54.204]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTP id EA90D28448; Thu, 7 Feb 2008 09:32:02 +0800 (CST) Received: from localhost (unknown [202.108.54.204]) by tarsier.geekcn.org (Postfix) with ESMTP id 91757EC3651; Thu, 7 Feb 2008 09:32:02 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([202.108.54.204]) by localhost (mail.geekcn.org [202.108.54.204]) (amavisd-new, port 10024) with ESMTP id SW30hY5-j3HC; Thu, 7 Feb 2008 09:31:57 +0800 (CST) Received: from charlie.delphij.net (71.5.7.139.ptr.us.xo.net [71.5.7.139]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id AC641EC3609; Thu, 7 Feb 2008 09:31:55 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=mAbi3wCRgKz9I3tp9XRZvxY0jiy+k0MHkIpJmzS2vuSVN1qBgFXEzLxm3QiYGW7e4 YK+grpS8VWNDo4qYlRHOw== Message-ID: <47AA5F87.6040905@delphij.net> Date: Wed, 06 Feb 2008 17:31:51 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20080122) MIME-Version: 1.0 To: Attilio Rao References: <3bbf2fe10802061700p253e68b8s704deb3e5e4ad086@mail.gmail.com> In-Reply-To: <3bbf2fe10802061700p253e68b8s704deb3e5e4ad086@mail.gmail.com> X-Enigmail-Version: 0.95.5 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Yar Tikhiy , Doug Barton , Jeff Roberson , freebsd-fs@freebsd.org, Scot Hetzel , freebsd-arch@freebsd.org Subject: Re: [RFC] Remove NTFS kernel support X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2008 01:32:04 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Attilio Rao wrote: > As exposed by several users, NTFS seems to be broken even before first > VFS commits happeing around the end of December. Those commits exposed > some problems about NTFS which are currently under investigation. > Ultimately, This filesystem is also unmaintained at the moment. > > Speaking with jeff, we agreed on what can be a possible compromise: > remove the kernel support for NTFS and maybe take care of the FUSE > implementation. > What I now propose is a small survey which can shade a light on us > about what do you think about this idea and its implications: > - Do you use NTFS? I use it occasionally when I need to copy files from the Windows partition. > - Are you interested in maintaining it? No. > - Do you know a good reason to not use FUSE ntfs implementation? What > the kernel counter part adds? No, the only reason come to mind is that one don't need to install separately, and thus might be good if you run -CURRENT. > - Do you think axing the kernel support a good idea? If nobody would maintain it, as long as the FUSE NTFS implementation is usable I think it's a good idea to axe it in 8.0. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHql+Hi+vbBBjt66ARAg0bAJ4lsJRyQrRGayvskC41dMCwDuwCfACffhca BcYVAWhFBciKHIeEYWmDSi0= =YhRg -----END PGP SIGNATURE-----