From owner-freebsd-questions@FreeBSD.ORG Mon Dec 12 17:10:09 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D94816A420 for ; Mon, 12 Dec 2005 17:10:09 +0000 (GMT) (envelope-from mailist@whoweb.com) Received: from whoweb.com (whoweb.com [66.180.172.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AF1743D6E for ; Mon, 12 Dec 2005 17:10:05 +0000 (GMT) (envelope-from mailist@whoweb.com) Received: from whoweb.com (localhost [127.0.0.1]) by whoweb.com (8.12.11/8.12.11) with ESMTP id jBCHA134068105 for ; Mon, 12 Dec 2005 12:10:01 -0500 (EST) Received: (from mailist@localhost) by whoweb.com (8.12.11/8.12.11/Submit) id jBCHA1Zj068104 for freebsd-questions@freebsd.org; Mon, 12 Dec 2005 12:10:01 -0500 (EST) Date: Mon, 12 Dec 2005 12:10:01 -0500 (EST) From: Incoming Mail List Message-Id: <200512121710.jBCHA1Zj068104@whoweb.com> To: freebsd-questions@freebsd.org Subject: mount_smbfs file name problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 17:10:09 -0000 I've got a problem with file names containing ":" and "?" characters when mounted via mount_smbfs. I have two FBSD machines running SAMBA. Machine-1 mounts a file system from Machine-2 using mount_smbfs(). The ls() command converts a file name such as XX:YY to something like X~Y. If I run tar() to backup XX:YY, it reports an error (tar: X~Y: no such file or directory). So it appears that when tar() recursively goes down a directory hierarchy and finds the file, it gets the name as X~Y. But when it trys to add the file to the archive, it fails because there is no file on the system with the name X~Y. Is this something that the charsets definition in nsmb.conf can fix? If so, what are the character sets I should use? If not, is there a solution for this issue? Thanks, Jon