From owner-freebsd-questions@freebsd.org Tue Jan 29 22:10:48 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 6ED0C14A9D79 for ; Tue, 29 Jan 2019 22:10:48 +0000 (UTC) (envelope-from noeldude@gmail.com) Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 41BC46D98D for ; Tue, 29 Jan 2019 22:10:47 +0000 (UTC) (envelope-from noeldude@gmail.com) Received: by mail-qk1-x72c.google.com with SMTP id 68so12508280qke.9 for ; Tue, 29 Jan 2019 14:10:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:openpgp:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=FE2RKIAPUaNEdQDNKCIoLlhJhDajg8eqeYUM4O3kkCA=; b=S7VoY5+pVPoJLPrTu4Qrhu1ZBPvSjdb3euqRVXaUMVMCSKnx4K2vLGxAuexTnIa3kK GGJKnXvOZnQpy5l38BwCUPijDmAPDYxgWGQgl1Zsiwin7zq8zzdC6M39yxI8qTPnhaPG 4jvvMa+aQwi2me7/jJZV1p1WgKhexG+Aez3thPQYkMCroVetYs40omHxQ3vrtpiNZ3ml o6BaikQVRPIy7wpFYmc0GP9/lly8U7Q2pfNyN+BeIpZj18sPqCaC8KW6STQnDF0x1hur WaioSOh81iP+kjtikCk/rY43t6C2w1A4sVeAP/ZtbF4stEb6VbKHMhhZpdGugVnDELA3 7ELw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:openpgp:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=FE2RKIAPUaNEdQDNKCIoLlhJhDajg8eqeYUM4O3kkCA=; b=nkDSoLxrz2dJEbSO0WmzdgAYOorymg5kQ+uREB+Pk4vLFWnwDFJrgTlX4yWKtVWxmM of1cZboRRldddKC0VGIt8W/qLtJ2HTIv9ss/iRJ/zQBY23EC+Kupt6oQwIhPX4vD9HQu ySN8FNvgTW6aUzenCjtke++9e9HXKF/6S89EJD9dr1C6av6CebU+zRmcQm7N4yShsxFI S61RDE+xsp590LDBUUaJvy+gty4PWZXdZnAEq/nhzHSHyHJRvFo53L1wclCNFtRYseQU Ct/K8psNcPPZBHyply/A/2mgXbQ/Xx68vNcDUnvgHQkcIKEXm6eWe7yqFG/ucZR6qDWq VR8g== X-Gm-Message-State: AJcUukdzmNs9o9GAvQirOdte75aNM6CYR4iUvSvK6H7PHBm84YxM90q4 DHjabhgwK2qPZIL6to7lvxBAF3hp X-Google-Smtp-Source: ALg8bN56KMjxlejw3UuTDK/5RQg+Hb6bj8zi+L898ENk6qEkfI+PqjX/W67a9wWqjk9hyBmN8YAtDA== X-Received: by 2002:a37:57c5:: with SMTP id l188mr24435422qkb.54.1548799845558; Tue, 29 Jan 2019 14:10:45 -0800 (PST) Received: from [192.168.170.53] ([12.244.165.78]) by smtp.googlemail.com with ESMTPSA id q2sm56789255qkc.68.2019.01.29.14.10.44 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Jan 2019 14:10:44 -0800 (PST) Subject: Re: RSYNC changes file name To: freebsd-questions@freebsd.org 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> From: Noel Openpgp: preference=signencrypt Message-ID: Date: Tue, 29 Jan 2019 16:10:43 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 41BC46D98D X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=S7VoY5+p; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of noeldude@gmail.com designates 2607:f8b0:4864:20::72c as permitted sender) smtp.mailfrom=noeldude@gmail.com X-Spamd-Result: default: False [-6.80 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.97)[-0.967,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-2.82)[ip: (-9.55), ipnet: 2607:f8b0::/32(-2.52), asn: 15169(-1.95), country: US(-0.08)]; RCVD_IN_DNSWL_NONE(0.00)[c.2.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0] 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:10:48 -0000 On 1/29/2019 3:35 PM, James B. Byrne via freebsd-questions wrote: > On Tue, January 29, 2019 16:21, Polytropon wrote: >> On Tue, 29 Jan 2019 16:13:46 -0500, James B. Byrne wrote: >>> >>> On Tue, January 29, 2019 15:43, Polytropon wrote: >>>> On Tue, 29 Jan 2019 15:28:50 -0500, James B. Byrne wrote: >>>>> Gpart reports the file system is type 12 which I believe is some >>>>> variant of FAT. MS Windows does not permit file names ending in >>>>> either a dot or a space. The filesystem silently truncates the >>>>> offending character. >>>> Ha, just as I thought. :-) >>>> >>>> If you're going to use the target medium for FreeBSD >>>> only (i. e., you won't access it from "Windows"), why >>>> not initialize it with UFS? There are even tunefs >>>> options that can help optimizing access to specific >>>> media, like USB sticks or SD cards. In fact, there >>>> even isn't a need for a partition table, if you for >>>> example do "newfs /dev/da0" (where da0 corresponds >>>> to the medium in question), and then you can use it >>>> as "mount -t ufs /dev/da0 /mnt" without problems. >>>> Filenames will then correctly be stored. >>>> >>>> Suggestion: For backing up FreeBSD stuff, keep using >>>> FreeBSD stuff. :-) >>>> >>> The resulting archives must be readable on a windows OS. It is a >>> portable backup which may have to be used in situations where any >>> form >>> of *nix will not be available to me. >> You say, "the archives", but it seems you're copying >> bare files. A convenient to deal with this problem is >> to "encapsulate" the whole thing in a "| tar" pipe. >> There are versions of the tar program available even >> for "Windows". Inside a tar archive, a file "12345." >> can be stored, while the archive itself can have a >> name that does not violate FAT rules. >> >> Of course, this introduces another problem: Can you >> make sure that the system you'll be using will be >> able to use tar? It's not for the compression (which >> you _could_ use), just for the "encapsulation". >> But if you just need something to _store_ the file, >> not to _process_ it, it could be an option for you. >> I don't know about the specific scenarios you're >> preparing for, but as you talked about IMAP data >> in maildir format, I can imagine that you just could >> transfer a tar file from the "Windows" system to the >> actual IMAP server (for data restore), extract it >> _there_ - which will surely be some kind of UNIX >> system (FreeBSD, any BSD, Linux), and every UNIX >> system has a tar implementation. >> >> Just a thought. >> >> Summary: You cannot use FAT for backups when it will >> not allow the filenames to stay the same. >> > I am using the word archives in its ordinary sense, a collection of > records. I am using the word record in its ordinary sense as well, > something that is preserved, not as a entry in a data file. I am not > referring to any specific file format or application software. > > 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. > > That's perfectly fine, as long as you're aware of the limitations when moving between file systems that have different filename rules.  Also be aware that ms-dos type filesystems silently-internally case-fold names, so that "FOO" and "Foo" are the same file.  This can lead to data loss by unintentionally overwriting a file. rsync can't warn of you the name munging since rsync asks the filesystem to write file "foo." and the filesystem says, "ok, sure"...  so no error to report. If this is a regular thing, you would be well served to insure all the files you're saving conform to ms-dos name rules.