From owner-freebsd-questions@FreeBSD.ORG Fri Jun 20 05:59:17 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DC97DEA8 for ; Fri, 20 Jun 2014 05:59:17 +0000 (UTC) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9F9A127AB for ; Fri, 20 Jun 2014 05:59:17 +0000 (UTC) Received: from r56.edvax.de (port-92-195-64-166.dynamic.qsc.de [92.195.64.166]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id B58083D6DC; Fri, 20 Jun 2014 07:51:16 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s5K5pFl8002286; Fri, 20 Jun 2014 07:51:15 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Fri, 20 Jun 2014 07:51:15 +0200 From: Polytropon To: Andrew Berg Subject: Re: samba, rsync --backup, and mangled instead of long filenames Message-Id: <20140620075115.a852559c.freebsd@edvax.de> In-Reply-To: <53A3C486.0@my.hennepintech.edu> References: <489659738.13024627.1403216558777.JavaMail.root@cds005> <53A38A96.2000903@gmail.com> <20140620064405.07e6428b.freebsd@edvax.de> <53A3C486.0@my.hennepintech.edu> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jun 2014 05:59:17 -0000 On Fri, 20 Jun 2014 00:20:06 -0500, Andrew Berg wrote: > On 2014.06.19 23:44, Polytropon wrote: > > On Thu, 19 Jun 2014 20:12:54 -0500, Noel wrote: > >> Yes, the colons will break windows compatibility. > > > > And make sure file names aren't too long, because long file names > > are also not accepted in the "Windows" land of non-compatibility > > and non-interoperability. ;-) > To be fair, this is more of an application issue than Windows itself > since Windows does provide an API for long file names, and > applications that use it can work with long file names just fine. It's _often_ an application problem when the native APIs aren't being used properly. As you usually don't get source code with "Windows" programs, you can't be fully sure, that's why it makes sense to avoid the expectation that things which work everywhere do also work on "Windows". If I remember correctly, the maximum length is 260 bytes (and in case of UTF-8 representation, this could mean less characters) for the _full_ path, whereas for example UFS restricts each _element_ of the path (and the file name) to 256 bytes. There are also "forbidden strings" like CON, PRN, CLOCK$, NUL (even with extensions), as well as for example $Boot, $Secure, or $Quota. If you expect those (in other places fully valid) file names to work, well, ... ;-) Not allowing damage to happen out of expectations is an important consideration when backing up files from FreeBSD to "Windows". Some careful precautions can help here, even though it might make the whole process "less convenient". But if you value your data, you usually don't care much for convenience. Avoiding obstacles before they can hit you seems to be helpful. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...