> From: Edward Ned Harvey (lopser) > > But I'm running OSX. ;-) All unicode characters are allowed, including > NUL. > (Although many applications will impose their own restrictions.)
As mentioned, this belief was based I thought on several sources, but apparently it distills down to a single unbacked wikipedia page. So it could be true, or could be bunk, as mentioned. > And in btrfs, '/' is disallowed (in addition to \0). And in extfs, \0, '/', > "." and > ".." are disallowed... I'm choosing not to try supporting "'/' and '\0' are disallowed" as they don't seem to be under challenge. So the only point in question is whether or not "." and ".." are permitted filenames in extfs. I think we all know the answer to this question. They are reserved, so if we want to get semantic, we could say they are technically permitted, but disallowed for any purposes in user space other than read. _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
