Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Carlos E. R." Newsgroups: comp.os.linux.misc Subject: Re: Another interesting (?) scp/rsync problem. Date: Sun, 4 Oct 2026 19:31:25 +0200 Lines: 16 Message-ID: References: <119ql2q$2ee3l$1@news.xmission.com> <119tgru$2kbjn$2@news.xmission.com> <119tmoa$2kovh$1@news.xmission.com> <119u12s$3glq$1@dont-email.me> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: individual.net Ya9c208PaK+LE9J48MVzQQmpIREcHCCLMedFIGstWJUIbo1DUu Cancel-Lock: sha1:CZmnx+ipOqsKr6RWcf0OCusXcNw= sha256:Lg7IjZKNGHn9J/7QKAF8gFVoj6xmzR8vJoHqd7QBv2I= User-Agent: Mozilla Thunderbird Content-Language: en-GB In-Reply-To: <119u12s$3glq$1@dont-email.me> Xref: csiph.com comp.os.linux.misc:92849 On 2026-10-04 19:06, The Natural Philosopher wrote: > On 04/10/2026 15:10, Kenny McCormack wrote: >> Remember, this whole issue is simply one of there being a very well known >> bug in the old version(s) of scp/rsync, that is fixed in current >> versions. >> >> So, really, nothing to see here. > which is why I NFS crossmount my machines and used the GUI > sshfs and mc -- Cheers, Carlos E.R. ES🇪🇸, EU🇪🇺.