MacOS file system changes between 7u10 and 7u40?

[Martin Buchholz]

Interesting.

ZFS apparently supports a wide variety of behavior.  Apparently for Windows
support ?!

http://docs.oracle.com/cd/E19253-01/816-5166/zfs-1m/index.html

casesensitivity=sensitive | insensitive | mixed
Indicates whether the file name matching algorithm used by the file system
should be case-sensitive, case-insensitive, or allow a combination of both
styles of matching. The default value for the casesensitivity property is
sensitive. Traditionally, UNIX and POSIX file systems have case-sensitive
file names.

The mixed value for the casesensitivity property indicates that the file
system can support requests for both case-sensitive and case-insensitive
matching behavior. Currently, case-insensitive matching behavior on a file
system that supports mixed behavior is limited to the Oracle Solaris SMB
server product, which is not supported in the Oracle Solaris 10 release.
For more information about the mixed value behavior, see the Oracle Solaris
ZFS Administration Guide.

This SMB related property is not fully functional in the Oracle Solaris 10
release because the Oracle Solaris SMB server is not supported in the
Oracle Solaris 10 release.

normalization = none | formC | formD | formKC | formKD
Indicates whether the file system should perform a unicode normalization of
file names whenever two file names are compared, and which normalization
algorithm should be used. File names are always stored unmodified, names
are normalized as part of any comparison process. If this property is set
to a legal value other than none, and the utf8only property was left
unspecified, the utf8only property is automatically set to on. The default
value of the normalization property is none. This property cannot be
changed after the file system is created.

This SMB related property is not fully functional in the Oracle Solaris 10
release because the Oracle Solaris SMB server is not supported in the
Oracle Solaris 10 release.

utf8only=on | off
Indicates whether the file system should reject file names that include
characters that are not present in the UTF-8 character code set. If this
property is explicitly set to off, the normalization property must either
not be explicitly set or be set to none. The default value for the utf8only
property is off. This property cannot be changed after the file system is
created.

This SMB related property is not fully functional in the Oracle Solaris 10
release because the Oracle Solaris SMB server is not supported in the
Oracle Solaris 10 release.



On Fri, Oct 4, 2013 at 9:32 AM, Philippe Marschall <
philippe.marschall at gmail.com> wrote:

> On Fri, Oct 4, 2013 at 6:29 PM, Philippe Marschall
> <philippe.marschall at gmail.com> wrote:
> > On Fri, Oct 4, 2013 at 5:30 PM, Martin Buchholz <martinrb at google.com>
> wrote:
> >> It is already the case that you cannot access all possible Unix file
> names
> >> from Java because by design, file names are represented by Java strings
> >> (UTF-16), but at the OS level filenames are actually arbitrary byte
> >> sequences with no concept of encoding.
> >
> > I don't think this is true on HFS+ and ZFS. As they do normalization
> > when a file is created, they need to have a concept of encoding.
>
> Well ZFS not when the file is created but on look up. And on creation
> ZFS still needs to check if a file name equal after normalization is
> present.
>
> Cheers
> Philippe
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/nio-dev/attachments/20131004/4174cd95/attachment.html