So, the manpage seems to have a bug in it. The valid values for the
normalization property are:
none | formC | formD | formKC | formKD
Nico
--
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinf
On Thu, Aug 13, 2009 at 05:57:57PM -0500, Haudy Kazemi wrote:
> >Therefore, if you need to interoperate with MacOS X then you should
> >enable the normalization feature.
> >
> Thank you for the reply. My goal is to configure the filesystem for the
> lowest common denominator without knowing up f
Nicolas Williams wrote:
On Wed, Aug 12, 2009 at 06:17:44PM -0500, Haudy Kazemi wrote:
I'm wondering what are some use cases for ZFS's utf8only and
normalization properties. They are off/none by default, and can only be
set when the filesystem is created. When should they specifically be
e
On Wed, Aug 12, 2009 at 06:17:44PM -0500, Haudy Kazemi wrote:
> I'm wondering what are some use cases for ZFS's utf8only and
> normalization properties. They are off/none by default, and can only be
> set when the filesystem is created. When should they specifically be
> enabled and/or disable
Hello,
I'm wondering what are some use cases for ZFS's utf8only and
normalization properties. They are off/none by default, and can only be
set when the filesystem is created. When should they specifically be
enabled and/or disabled? (i.e. Where is using them a really good idea?
Where is
