On Fri, 14 Mar 2008, Barry Kelly wrote:
>
> [1] http://ntfs-3g.org/
>
> There's a very important phrase in there, worth repeating: "users need
> to reliably interoperate with NTFS". Forget MS: think of the users.
For me it seems that for you the word "users" means those who have the same
problem as you. The world is a bit bigger. There were something like nine
NTFS drivers just for Linux. The project is not only about interoperability
with your personal preference.
The driver should handle all filenames created by the NT POSIX subsystem
or any other driver. Well, minus the real problems we currently have and
working on.
Your real problem is that, the NT POSIX subsystem can't handle all
filenames created by other softwares. Did you consider submitting a bug
report?
> Microsoft devs (or indeed devs from pretty much anywhere) don't have the
> authority to give "backing". What do you need? A patent cross-licensing
> deal with MS? I don't have the ability to get that, sorry. An internal
> design doc or spec from MS? I don't think you can legally get that
> without the cross-licensing deal at a minimum.
>
> So what do you need?
I expect the NTFS specification published here clearly stating what UTF-16
code units are not allowed to be stored in filenames:
http://www.microsoft.com/interop/
> > And here is our problem. Windows is massively plagued with all kind of
> > security problems by viruses, root kits etc which exploit Windows
> > shortcomings to hide themself. The open source NTFS-3G is widely used
> > in security softwares because it can access and remove them.
>
> > You're asking to drop the above highly important feature to become
> > compatible with the non-POSIX complaint NT "POSIX" subsystem. That
> > won't be easy but I'll think about it ...
>
> I don't have the detailed statistics, but I would venture that that is a
> niche use of NTFS-3G - an important niche, but a niche nonetheless.
>
> I believe it should be a mount option, a kind of "raw" mode, which
> defaults to off.
>
> I would hazard a guess that most users of NTFS-3G are using it because
> they are dual-booting Windows and Linux.
Yes, most dual booters think the same ;) This is the real picture:
1. embedded devices, dedicated appliances, emergency,
recovery, security and other LiveCDs
2. external storages
3. dual booters
> And please, think of the users!
That's why the driver works how it works. It doesn't restrict usage
but promotes better interoperability.
I'm sorry to say but you are in the minority demanding better
interoperability with a broken, niche system at the expense of
more users.
Regards,
Szaka
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
ntfs-3g-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
