From owner-freebsd-questions@freebsd.org Tue Jan 29 22:17:30 2019 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D401214AA189 for ; Tue, 29 Jan 2019 22:17:29 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from mx32.harte-lyne.ca (mx32.harte-lyne.ca [216.185.71.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx32.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 93BD96DEFA for ; Tue, 29 Jan 2019 22:17:28 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from mx32.harte-lyne.ca (unknown [127.0.32.1]) by mx32.harte-lyne.ca (Postfix) with ESMTP id 7CA32677E; Tue, 29 Jan 2019 17:17:27 -0500 (EST) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from mx32.harte-lyne.ca ([127.0.32.1]) by mx32.harte-lyne.ca (mx32.harte-lyne.ca [127.0.32.1]) (amavisd-new, port 10024) with ESMTP id DAkHms1pBwlX; Tue, 29 Jan 2019 17:17:25 -0500 (EST) Received: from webmail.harte-lyne.ca (mx32.harte-lyne.ca [216.185.71.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx32.harte-lyne.ca (Postfix) with ESMTPSA id D14F1676D; Tue, 29 Jan 2019 17:17:24 -0500 (EST) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Tue, 29 Jan 2019 17:17:25 -0500 Message-ID: <39252c5bcccb39bea6147117b029192c.squirrel@webmail.harte-lyne.ca> In-Reply-To: <20190129230018.a028f4fd.freebsd@edvax.de> References: <9aaa35912b122e88e667e7516ba6a865.squirrel@webmail.harte-lyne.ca> <20190129204033.7312742f.freebsd@edvax.de> <10a14c28507feee71572a2573d319fc3.squirrel@webmail.harte-lyne.ca> <20190129214351.2f32c04c.freebsd@edvax.de> <18bd6c1326e011634c5b548e5cfd94aa.squirrel@webmail.harte-lyne.ca> <20190129222126.d0449659.freebsd@edvax.de> <20190129230018.a028f4fd.freebsd@edvax.de> Date: Tue, 29 Jan 2019 17:17:25 -0500 Subject: Re: RSYNC changes file name From: "James B. Byrne" To: "Polytropon" Cc: freebsd-questions@freebsd.org Reply-To: byrnejb@harte-lyne.ca User-Agent: SquirrelMail/1.4.23 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Rspamd-Queue-Id: 93BD96DEFA X-Spamd-Bar: -------- X-Spamd-Result: default: False [-8.48 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[byrnejb@harte-lyne.ca]; RBL_COMPOSITE_RCVD_IN_DNSWL_MED_DWL_DNSWL_LOW(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:216.185.71.0/26]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; DKIM_TRACE(0.00)[harte-lyne.ca:+]; RCPT_COUNT_TWO(0.00)[2]; HAS_X_PRIO_THREE(0.00)[3]; RCVD_IN_DNSWL_MED(-0.20)[32.71.185.216.list.dnswl.org : 127.0.4.2]; DMARC_POLICY_ALLOW(-0.50)[harte-lyne.ca,quarantine]; MX_GOOD(-0.01)[cached: mx32.harte-lyne.ca]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:12021, ipnet:216.185.64.0/20, country:CA]; IP_SCORE(-3.78)[ip: (-9.91), ipnet: 216.185.64.0/20(-4.95), asn: 12021(-3.96), country: CA(-0.09)]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[harte-lyne.ca:s=dkim_hll]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.994,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DWL_DNSWL_LOW(0.00)[harte-lyne.ca.dwl.dnswl.org : 127.0.4.1]; TO_MATCH_ENVRCPT_SOME(0.00)[] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2019 22:17:30 -0000 On Tue, January 29, 2019 17:00, Polytropon wrote: >> >> The purpose of the USB key archives is to allow me to search for >> specific files, generally UFT8 encoded, using the native file system >> tools on whatever host I have access to. I do this on a regular >> basis. Encapsulating the data in a file format that depends upon >> access to a specific application defeats the purpose. > > Okay, this makes perfectly sense. > > So you do _not_ use those files to restore IMAP message content > on the server you've rsync'ed them from, you're just unhappy > with the fact that "12345." became "12345" on FAT due to > naming restrictions. In this case, you can convince yourself > that you didn't do anything wrong, it's just FAT that doesn't > allow a "." at the end of the filename. Maybe it is possible > to live with this fact, or try to change the source file naming > convention from "xxxxx." to "xxxxx" (where x = 0...9), if that > is possible. > I am considering modifying the transfer script so as to remove the trailing dot before hitting the FAT fs. That would prevent rsync from deleting all of the files on the target that do not have trailing dots before replacing them with files with the exact names as those it just deleted. Regards, -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3