From owner-freebsd-questions@FreeBSD.ORG Fri Jun 20 05:20:22 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 78A1E96C for ; Fri, 20 Jun 2014 05:20:22 +0000 (UTC) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0203.outbound.protection.outlook.com [207.46.163.203]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 35C9E2515 for ; Fri, 20 Jun 2014 05:20:20 +0000 (UTC) Received: from [IPv6:2601:2:4780:2fd:993e:7d67:8ea2:66bb] (2601:2:4780:2fd:993e:7d67:8ea2:66bb) by BN1PR03MB024.namprd03.prod.outlook.com (10.255.224.42) with Microsoft SMTP Server (TLS) id 15.0.969.15; Fri, 20 Jun 2014 05:20:12 +0000 Message-ID: <53A3C486.0@my.hennepintech.edu> Date: Fri, 20 Jun 2014 00:20:06 -0500 From: Andrew Berg User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Subject: Re: samba, rsync --backup, and mangled instead of long filenames References: <489659738.13024627.1403216558777.JavaMail.root@cds005> <53A38A96.2000903@gmail.com> <20140620064405.07e6428b.freebsd@edvax.de> In-Reply-To: <20140620064405.07e6428b.freebsd@edvax.de> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [2601:2:4780:2fd:993e:7d67:8ea2:66bb] X-ClientProxiedBy: DM2PR03CA006.namprd03.prod.outlook.com (10.141.52.154) To BN1PR03MB024.namprd03.prod.outlook.com (10.255.224.42) X-Microsoft-Antispam: BCL:0;PCL:0;RULEID: X-Forefront-PRVS: 024847EE92 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(6009001)(428001)(199002)(51704005)(189002)(24454002)(77096002)(87976001)(81542001)(102836001)(85306003)(105586002)(99396002)(80022001)(65816999)(83322001)(33656002)(65806001)(95666004)(54356999)(88552001)(64706001)(76176999)(81342001)(50986999)(47776003)(21056001)(83506001)(4396001)(20776003)(77982001)(50466002)(75432001)(76482001)(31966008)(83072002)(101416001)(74662001)(23676002)(86362001)(85852003)(42186005)(74502001)(46102001)(92726001)(79102001)(92566001)(106356001)(3826002); DIR:OUT; SFP:; SCL:1; SRVR:BN1PR03MB024; H:[IPv6:2601:2:4780:2fd:993e:7d67:8ea2:66bb]; FPR:; MLV:sfv; PTR:InfoNoRecords; A:0; MX:1; LANG:en; Received-SPF: None (: my.HennepinTech.edu does not designate permitted sender hosts) Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=aberg010@my.HennepinTech.edu; X-OriginatorOrg: my.hennepintech.edu 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:20:22 -0000 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.