On Tue, Aug 12, 2008 at 7:06 PM, Michael Sokolov <[email protected]> wrote: > Chris Louden <[email protected]> wrote: > >> Anyone ever had issues with permissions on folders that contain (#) >> (@) or( ,) in the name? > > Ahmm, Linux (just like UNIX) doesn't have folders, it has directories. > > As far as characters in file and directory names go: dunno about Linux, > but in UNIX the name of a file (any file, be it a regular file, a > directory, a symlink, a block or character device node or a socket) may > be up to 255 characters in length and may contain ANY 7-bit ASCII > characters except NUL and '/'. > > Permissions have absolutely nothing to do with it: the name and the > permission bits are completely orthogonal. Furthermore, the permission > bits are part of the i-node and there may be more than one filename (in > the same or in different directories) referring to the same i-node. > > MS
to clarify. I appear to be having issues with new files being created via SMB and not receiving the appropriate permissions and membership based on the sticky settings. The "directories" that this occurs in have complex names that _could_ potentially have issues with scripts due to the use of # , @ and other characters. Although troubleshooting is not complete. > _______________________________________________ > LinuxUsers mailing list > [email protected] > http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers > -- -Chris
