14 сентября 2014 г. 15:42:25 CEST, "Edward Ned Harvey (openindiana)" <openindi...@nedharvey.com> пишет: >> From: Edward Ned Harvey (openindiana) >> [mailto:openindi...@nedharvey.com] >> >> Is ZFS using Unicode or ASCII? Or something else? >> >> Are there disallowed characters? '\0' or @ or '/' or anything else? >I know >> these characters generally would be *difficult* to use just because >of >> limitations of your application environment (for example, bash will >always >> parse the '/' as a directory delimiter, but at least in hfs+, that >character isn't >> actually forbidden by the filesystem.) So I'm not asking which >characters >> would be *practically* difficult to use, I'm asking which characters >are *valid* >> according to the filesystem itself. > >Are the valid characters the same for filesystem names, and filenames? >(e.g. mountpoints & zvol's, versus directories and files) > >_______________________________________________ >openindiana-discuss mailing list >openindiana-discuss@openindiana.org >http://openindiana.org/mailman/listinfo/openindiana-discuss
while i don't have a precise answer, i think that the set of valid characters in dataset names is different from those in the POSIX filesystems - i.e. '@' and '%' are reserved dataset separators (real and receiving-in-progress snapshots) while valid in filenames. We were taught in school that only '\0' and '/' are invalid in posix fs object names, being the end of string and directory separator accordingly. I am not sure if this holds in the utf era as well, though. Jim -- Typos courtesy of K-9 Mail on my Samsung Android _______________________________________________ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
