Re: kern/52724: ntfs driver doen't allow ':' in file names.

[trebol <trebol4444%gmx.com@localhost>]

The following reply was made to PR kern/52724; it has been noted by GNATS.

From: trebol <trebol4444%gmx.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/52724: ntfs driver doen't allow ':' in file names.
Date: Tue, 14 Nov 2017 12:28:42 +0000 (WET)

 On Tue, 14 Nov 2017, Dave Huang wrote:
 > Well using a non-printing character to access alternate data streams
 > certainly violates the principle of least astonishment, at least...
 
 As I've said in my problem report, the best solution for me is to write a 
 system utility to deal with ntfs attributes (and ads). You can use in 
 that utility the format that windows uses in its programs, with ':' as a 
 separator. You can use in the implementation of that program the idea of 
 J. Hannken to parse for colons from the end of the name, so you can keep 
 naming your files without restrictions.
 
 Using ^G is a dirty hack that allow me to read files without restrictions, 
 and the same time access the attributes without any problems.
 
 
 > Windows uses ":", and NTFS is primarily a Windows filesystem.
 
 Yes, and case insensitive file names. So NetBSD must use case insensitive 
 file names in ntfs? And use '\' for paths in ntfs because window uses 
 '\'?
 
 > If NetBSD wants to be different, I think there should be a good reason
 for it
 
 Because is UNIX, and the file system permits the use of unicode characters 
 except '\' and '\0' in posix sytems.
 
 If an OS has restrictions in its file names, is that OS who has to deal 
 with it. As long as the file system permits it (and doesn't matter who 
 develop the file system) other OSes don't have to be tied to others 
 limitations.
 
 There is other restrictions in windows names apart of the use of some 
 characters. A lot of them. Do you think is a good idea to put these 
 restrictions in the ntfs implementation?
 
 > personally, I don't consider accessing a file that would also be 
 > inaccessible on an actual Windows system to be a good reason.
 
 I hope you have tested that, because if not, you are just trolling 
 around.
 
 > I'm still curious as to which POSIX OS is creating files on NTFS with 
 > colons in their names.
 
 - Every OS that uses ntfs-3g, for example NetBSD?
 - Tuxera NTFS (a comercial version from the ntfs-3g developers)
 - Linux ntfs driver.
 - Someone with a Mac can test the internal (unstable) driver, I don't know.
 
 I said "Do whatever you want", but nevertheless, I'm now going around 
 things I already have said and looking for a stupid windows machine to 
 test file names with colons...
 
 trebol.