On Wednesday, 21 September 2022 at 17:10:05 UTC+1, Greg Wooledge wrote: > On Wed, Sep 21, 2022 at 04:29:07PM +0100, jr wrote: > > $ locate /jr/ | > > > grep -v -e /.cache/ -e /tmp/ | > > > > that is (one way) how the "ACTUAL CONTENTS" are arrived at. > That listing almost certainly includes subdirectory names. Hence your > issues. > ... > That's why you're getting duplicates. > ... > As I told you several posts ago, if you're feeding "find" output -- or > in your case, "locate" output, which has the exact same characteristics -- > to tar, then you need to use GNU tar's "--no-recursion" option.
had some time last night to try stuff. and yes, the '--no-recursion' option appears to be the one I need. thank you. > Also, it boggles my mind that you don't have a SINGLE file with spaces > in its name in your entire home directory. Apparently, you don't run > Steam or Google Chrome. correct, I do not play computer games (prefer the newspaper puzzle pages), and only use a (Chrome) browser on a Chromebook. file names with spaces, like eg 'Screenshot 2022-09-22 07.39.14.png' would get renamed when they get copied/moved to the SAMBA share. > ... > Finally, your backup, being based on "locate" rather than "find", is going > to miss any files that were created after the most recent updatedb run. > I find this to be an incredibly strange choice. Maybe your files just > aren't that important to you. I can't guess why. simple really. on all but two machines, new files are created .. infrequently, so updating the locate db only once per day is no problem. one machine runs the same cron job, just more often, and the one I write on is for interweb access only, disposable if you will. # ----- On Wednesday, 21 September 2022 at 17:20:05 UTC+1, Markus Schönhaber wrote: > 21.09.22, 17:29 +0200, jr wrote: > > [a reply that isn't one] > > Could you please stop using a mail client that starts a new thread with > every message you send? > Please use something instead that really creates a reply when you are > replying to someone (i. e. something that sets the > In-Reply-To/References message headers accordingly). ouch. I read the digest, and in that it appears as a single thread. and I've just checked 'linux.debian.user' on Google Groups, there too I see a single thread only. cannot see "a new thread [started] with every message", sorry. # ----- On Wednesday, 21 September 2022 at 17:50:04 UTC+1, Michael Stone wrote: > ... The premise is false. There are actually multiple implementations of > "locate" available in debian (and more, historically) so just saying > "locate" doesn't describe the implementation very well. ... good point. (and thanks for also pointing out the '--no-recursion' solution)
