Does anyone know why I am having trouble with making a shared folder available that has a period in the name i.e. "10.006"?

Is this an OS issue?

I've been successful with spaces in folder names by using a "\" plus the space afterwards, but I don't know, and can't find, if there's a similar workaround for a period.

Many thanks for any direction here!

Sounds like a bug, we need to investigate.

I'm still in search of an answer for this question. All I can find is that a period at the beginning of a directory name renders it as hidden, but nothing that I can find has any issue with a period anywhere else (maybe other than at the end).

I'm trying to mount a share such as



After entering this, and the # shows up without an error, nothing is shared.

Also, a previous share was active (similar to above but without any glitches) and this new mount bumps off the first mount. Can only one mount be made?

Are you talking about Webshare shares or other Network shares?

The path (as per previous) is a network location (NAS) that I am trying to have available for a Webshare - so I guess it's both.

Pilot error.... I think!

I changed the link path from /1 to /2 (after making a new directory for /2) and it took.

mount -t cifs //192.168.3.29/h$/projects/2011\/11.001\ job/11.001\ share /2 -o user=admin,pass=password

Thanks anyway - check this one off the list!